I have seen a pattern repeat in growing companies: the leadership team believes the strategy is clear, the teams are working hard, and yet the connection between the two becomes surprisingly difficult to prove.
That is not because people are careless. It happens because strategic intent has to travel. It moves from the board or leadership team into business units, functions, roadmaps, initiatives, metrics, budgets, and daily trade-offs. Every handoff can preserve the intent, weaken it, or reshape it a little.
This is where the first signal gap appears: the gap between strategy as communicated and strategy as it is connected to actual work.
A simple test often reveals it. Ask five initiative owners to trace their current work to a current board-level objective in under sixty seconds. Not the annual theme. Not a general priority. A specific current objective. Then notice three things: how long it takes, how confident the answer is, and whether different people use the same logic.
When this is hard, the issue is rarely lack of commitment. More often, the organization has relied on communication where it needed connection.
Broadcasting is not the same as connection
Many organizations treat strategic alignment as a communication task. Leadership publishes the annual plan, runs the all-hands, shares the deck, and expects the message to cascade through the company.
Communication matters. I would never argue against clarity. But broadcasting and connection are different capabilities.
Broadcasting means people have heard the strategy. Connection means people can see how their current work contributes to it, and the line of logic is visible enough for others to inspect.
This distinction matters because strategy and work are usually organized in different languages. Strategy is expressed as outcomes, choices, and priorities. Work is organized as projects, backlogs, owners, budgets, deliverables, and local constraints. If the two languages are not deliberately connected, people have to translate from memory.
That translation is where drift begins. A team may know the strategic priority and still be executing work shaped by last quarter’s assumptions. A function may be doing valuable work and still be loosely connected to the current direction. A project may look sensible locally while its strategic rationale has quietly expired.
The second strategy
Henry Mintzberg and James Waters made a useful distinction between intended and emergent strategy. Organizations do not execute only what they planned. A second strategy also emerges from the daily decisions people make while trying to get work done.
This is not a problem by itself. Emergence is often how organizations learn. A sales team follows demand from an unexpected segment. A product team changes sequence because a technical constraint becomes visible. A business unit shifts capacity because customer needs are changing faster than the annual plan.
The risk is not adaptation. The risk is invisible adaptation.
If leadership cannot see how the portfolio is changing, it may continue to believe that the intended strategy is being executed while a different pattern of work is taking shape. Sometimes that emergent pattern is smarter than the original plan. Sometimes it is a collection of local compromises. Either way, it is information leadership needs.
Connected by design
In small companies, connection often lives in people’s heads. The founder knows which projects matter. A senior manager knows the informal priorities. A few well-networked people can translate between board intent and team-level work.
That can work for a while. It becomes fragile when the company reaches the point where the leadership team can no longer hold the whole operating system in memory.
By complexity, I do not mean bureaucracy. I mean the normal accumulation of teams, initiatives, dependencies, customer segments, markets, products, and metrics. At a certain point, no single leader can reliably know which work connects to which strategic intent without a visible system.
Connected by Design means the link between team-level work and strategic intent becomes a property of the system, not a property of a few experienced people. The organization can answer “what connects to what?” without convening a meeting or rebuilding the map in a spreadsheet.
When connection is structural, leadership can see which initiatives support current priorities, which priorities lack real work behind them, and which work may have become orphaned after either an intentional strategy change or an emergent shift in the portfolio.
What to notice
I would not ask a leadership team to run a full diagnostic from a blog post. That is what my Health Check is for. But one observation is worth taking into the next strategy review: notice how much of your strategy connection depends on people remembering, interpreting, and translating correctly under pressure.
If a top-three objective changed tomorrow, the real question is not how fast leadership could announce the change. The question is how fast the normal management system would reveal which initiatives, metrics, owners, and dependencies should change with it.
That is where strategy often loses signal. Not in the quality of the message, but in the distance between the message and the work.