The board approved a new direction last quarter. Leadership is aligned. The roadmap is clear. Meanwhile, the assets executing that strategy were designed a decade ago, procured around a different set of priorities, and will still be running - or failing - a decade from now.
That gap does not announce itself. It accumulates.
In most asset-intensive organisations, the people sitting between strategy and execution are doing their best to serve two masters moving at completely different speeds. Strategy responds to markets, boards, and leadership cycles - sometimes overnight. Physical assets respond to physics, procurement lead times, and maintenance histories measured in years. The processes, systems, and people in the middle are being asked to connect across boundaries that they were never designed to connect.
What makes this genuinely difficult is that the consequences are not immediate.
A strategic decision made today - a shift in operating model, a change in production target, a cost reduction - doesn't produce an immediate feedback loop, and it can take months for the operational reality to catch up. By then, the connection back to the original decision has been lost. The operations team is managing a symptom, and there may not be the people, time, or money to look at the underlying cause.
The downstream impact is where it becomes visible. A customer starts seeing delivery inconsistency. Service levels drift. Penalty clauses get triggered. The commercial team is fielding conversations they cannot explain, because the explanation is buried somewhere in the relationship between a strategic call made two quarters ago and a set of assets that were never going to respond in time. The upstream cause and the downstream consequence exist in completely different conversations - and this is the hardest link to bring together.
This is not a failure of intent. The strategy team did their job. The operations team is doing theirs. The problem is structural. Between strategy and execution sits the hard reality of asset-intensive operations - operations, maintenance, assets, people, processes, inventory, finance, compliance. The difficulty is not finding the people willing to make the call. It is working out the right path when all of those things are pulling in different directions at once. When something goes wrong downstream, it's even harder to trace back what the root cause is to be sure it doesn't happen again.
What good looks like is not a perfectly integrated organisation with a bespoke ERP / EAM full of AI dashboards.
That is not realistic in asset-intensive industries, and anyone who tells you otherwise has not spent much time in them. What good looks like is deliberate visibility of both the decisions being made and their impact - covering implementation, delay, and no action. Knowing where the tension points are before they become failures, and having the capability to translate a strategic decision into operational consequence before it surfaces at the customer end.
Good organisations can see where each one leads.
Every person in the organisation should be able to draw a line from their daily work to the strategy above them. They should also be able to see - at least in outline - what their work means for the person before and after them in the value chain. That is not a cultural aspiration. It is a practical requirement for understanding the impact of your decisions and what potential issues they could cause.
The path forward starts with acknowledging that the gap is structural, not personal. Better communication and dashboards will help, but they may not fix it all. It is fixed by deliberately building the connection - through a value chain process that reflects how work actually gets done, people who understand where their role sits in the broader chain, and a clear line of sight from strategic intent to operational consequence. The organisations that get this right do not eliminate the speed difference between strategy and assets. They build the capability to manage decisions across a system of people, assets, processes, funds, and the technology that supports them.
If you got this far, we should probably talk. No pitch, no obligation - just an honest discussion about whether there's a problem worth solving together. Request a meeting.