What it means

When strategy is truly working, you would never know it was there.

That sounds wrong. Strategy is supposed to be visible - the big document, the annual offsite, the carefully cascaded objectives. Organisations invest enormous effort in making strategy seen.

But think about what it looks like when it has gone deeper than that. Nobody stops mid-decision to check the strategy - and yet, across different teams, different levels, different contexts, people keep making choices that pull in the same direction. Not because they have been told to. Because something about what matters here and where we are heading has become part of how they think.

Then Monday morning comes. And Tuesday. And all the Wednesdays after that. Gradually, without anyone deciding to ignore the strategy, the distance between it and the daily work starts to grow. Not because the strategy was wrong, but because it exists in a different place from where the work actually happens.

This shows up time and again with organisations whose strategic thinking is genuinely strong. The problem is not the quality of the strategy - it is the distance between where it lives and where it is needed. Strategy lives in documents, in quarterly reviews, in leadership conversations. Work lives in team meetings, in email threads, in the moment someone has to choose between two competing priorities with no one senior in the room.

The organisations where strategy has gone deeper feel different. Not because they have better strategies - though they might. But because strategy has somehow become part of how people think. It is not something they reference. It is something they use. When a new opportunity appears, people can assess it without escalating. When priorities compete, people know what matters most without needing to check. The strategy has moved from a document into the operating system.

That is what we mean by Embedded Strategy. Not strategy that has been communicated. Strategy that has been absorbed so deeply into how the organisation works that it is inseparable from the work itself. Like a language you have become fluent in - you stop translating and just think in it. Strategy becomes the way people reason, not something they consult before reasoning.

And this is an emergent property. You cannot embed strategy by communicating it harder - by cascading it through more levels, by putting it on more slides, by repeating it in more town halls. Embedding happens when the conditions are right: when purpose gives strategy something meaningful to translate, when trust exists for people to interpret strategy locally rather than just follow instructions, when the structures of daily work make strategic priorities visible rather than invisible. When those conditions align, strategy embeds itself. When they do not, it stays on the surface no matter how much effort goes into pushing it down.

The golden thread is the test. Can you trace a continuous line from the organisation's biggest ambition, through its strategic priorities, through team objectives, all the way down to what someone chose to work on this morning? In organisations where strategy is truly embedded, that thread holds. It may flex and adapt at each level, but it never breaks. Where it is not embedded, the thread snaps somewhere - often at the point where leadership's clarity meets the complexity of daily work.

The lens question: If you removed every strategy document and presentation, would people still know what to prioritise - and would they prioritise the same things?