Consider the scale of strategic investment that flows through middle management every year. Globally, organizations commit trillions of dollars to initiatives that depend on middle managers for execution. These managers hold operationally grounded knowledge about what is working, what is drifting, and what is about to break. Yet in most organizations, that knowledge has no structured, continuous channel to reach the people making strategic decisions.
The result is an enormous waste of organizational intelligence, repeated across industries and economies. The problem is not that middle managers lack insight. The problem is that the architecture around them was never designed to capture what they see, aggregate it meaningfully, or make it visible to the organization as a whole.
Drift is continuous. The channels are not.
A common framing of this issue focuses on a single moment: the strategy offsite or planning cycle where middle managers are brought in too late, or not at all. In my experience, that framing misses the deeper challenge.
The real problem is not about one meeting. Drift between strategy and execution happens continuously, for many reasons — shifting market conditions, resource constraints, evolving customer needs, dependencies that behave differently than planned. Middle managers are the people closest to this drift. They see the early, often ambiguous signals: a team that is quietly reprioritizing because the original objective no longer makes sense, a dependency that is becoming fragile, a capability gap that was not visible during planning.
But these signals are frequently unclear, unstructured, and difficult to articulate in the language of a status report. They are weak signals, the kind that do not fit neatly into a RAG indicator or a quarterly review template. And middle managers, often overwhelmed by operational work, tend to lack the time and the forum to surface what they are observing in a way that reaches decision-makers while the information is still actionable.
Research by Steven Floyd and Bill Wooldridge, spanning multiple studies in the Strategic Management Journal, found that organizations with greater middle management involvement in strategy formation consistently outperformed those without it. Floyd and Wooldridge identified four distinct strategic roles that middle managers play — from synthesizing information and championing alternatives to facilitating adaptability. When these roles are structurally blocked, not by intention but by the absence of continuous channels, the organization loses a strategic input that the research suggests is directly linked to performance.
One voice is not enough
There is a second dimension to this challenge that is easy to overlook. Even when an individual middle manager does surface a concern, that single perspective is inherently incomplete. One manager sees their part of the organization. They understand their team's constraints, their dependencies, their operational reality. What they cannot see is the pattern that emerges when dozens or hundreds of managers are experiencing similar pressures simultaneously.
The true picture of strategic drift surfaces only when the voices of all middle managers are aggregated in a meaningful way. Not as an annual engagement survey. Not as an eNPS snapshot that captures sentiment but not substance. A continuous aggregation that reveals where operational reality has diverged from strategic intent, across the entire organization, in something closer to real time.
Without that aggregation, each manager's signal remains isolated. Leadership may hear one concern and reasonably conclude it is a local issue. But when thirty managers across different business units are independently flagging variations of the same problem, that is no longer a local issue. That is a strategic signal. The challenge is that most organizations have no mechanism to make that pattern visible.
Green until it is red
This gap between individual signals and organizational visibility helps explain what might be called the green-to-red phenomenon.
A project is green on the dashboard. It has been green for three quarters. Then, in a single reporting cycle, the project turns red. Not amber. Not a gradual deterioration. Green, and then suddenly red.
In the cases I have observed, the warning signs were present long before the red appeared. They lived in weekly team calls, in resourcing conversations that were deferred, in dependencies that several managers flagged informally but where no formal mechanism existed to aggregate those flags into a visible pattern.
Leading indicators of this phenomenon are often available, though rarely captured systematically: the number of deferred escalations accumulating in a quarter, the frequency with which teams quietly reprioritize away from stated objectives, the ratio of informal concerns raised in hallway conversations versus formal concerns recorded in the reporting system. These are the data points that, if tracked continuously, could provide early warning well before the dashboard turns red.
Bent Flyvbjerg's research on behavioral biases in project management, drawing on data from over 2,000 projects, identified optimism bias as one of the most pervasive forces in organizational reporting. The pattern Flyvbjerg documented is structural: incentive systems and reporting cultures systematically inflate the picture that reaches decision-makers. When you combine that structural optimism with the absence of aggregated middle management intelligence, the green-to-red pattern becomes almost predictable.
The dismissal problem
There is another vantage point worth considering. In some organizations, middle managers do voice concerns, and leadership chooses not to act on them.
This is not always malicious. Leadership may have hired middle managers precisely to solve operational problems, and so they interpret upward signals as evidence that managers should handle the issue themselves rather than escalate it. Or the concern arrives as one voice among many priorities, and without aggregated data showing its significance, it is easy to deprioritize.
In the organizations I have observed, concerns raised by individual managers without a formal escalation mechanism tend to dissipate without action. Managers learn, rationally, to calibrate what they raise and when. This is an adaptation to an architecture that does not reliably reward candor.
The structural response to this dynamic is to make the bottom-up voice part of the organizational process itself, visible not just to a single leader who may choose to dismiss it, but to the entire organization. When aggregated middle management intelligence is transparent across the organization, it becomes much harder for any individual leader to ignore a pattern that everyone can see. The signal shifts from a private complaint to a shared organizational reality.
The economy-wide cost
Scale this pattern across industries and the implications become significant. Every organization that fails to capture middle management intelligence systematically is making strategic decisions with an incomplete picture. Multiply that across the thousands of organizations running major strategic initiatives at any given time, and the global waste — in misallocated resources, in initiatives that drift undetected, in corrections that come too late — is substantial.
This is not a niche management problem. It is a structural inefficiency embedded in how most organizations operate, and the cumulative cost to the global economy is worth taking seriously.
What to ask
If you want to understand whether your organization has this dynamic, three diagnostic questions are worth exploring.
First: when was the last time an official project status changed from green to red within the same quarter? If green-to-red transitions happen with some regularity, it is worth examining whether early warning signals exist somewhere in the organization that are not reaching the surface in time.
Second: do your middle managers have a continuous, structured channel to surface concerns about strategic drift — not just in planning cycles, but throughout execution? If the answer is only during quarterly reviews, or only when someone specifically asks, the architecture may be filtering out the signals that matter most.
Third: is there a mechanism that aggregates what middle managers are seeing across the organization, making the pattern visible to everyone — not just to the individual leader who happens to receive a specific concern? If each manager's signal stays isolated, the organization is collecting intelligence it cannot use.
The cost of not hearing from middle managers, continuously and in aggregate, tends to show up eventually. Often in the same quarter a project turns red.