In many organizations, the first people to sense strategic drift are not in the boardroom. They are the managers translating strategy into work.
They see the capacity constraint before it becomes a missed deadline. They notice when a dependency is becoming fragile. They hear when teams are quietly reprioritizing because the stated objective no longer fits operational reality.
The difficulty is that these signals are often early, partial, and hard to express. They do not yet look like a red status. They may not even look like a formal risk. They are weak signals, and weak signals need a route before they become evidence.
Drift is continuous. Formal channels are periodic.
Strategy execution changes every week. Customers respond differently than expected. Resources tighten. Dependencies shift. Assumptions age. Teams adapt.
Most strategy processes, however, listen in cycles: quarterly reviews, monthly status meetings, annual planning, steering groups. These forums matter. But their cadence changes what people choose to raise.
When leaders are busy and forums are periodic, the threshold for speaking goes up. People learn to bring “real issues,” not early discomfort. A small concern waits until it has become a pattern. A pattern waits until it has become a risk. A risk waits until it has become visible enough to defend.
By then, the organization may have lost the cheapest moment to act.
Middle managers are not just messengers
Middle managers sit at the intersection of strategic intent and operational reality. Research by Steven Floyd and Bill Wooldridge has shown the important roles middle managers play in strategy formation, including synthesizing information, championing alternatives, facilitating adaptability, and implementing deliberate strategy.
That matches what I have seen in practice. Middle managers are often the first layer that can see both the official strategy and the friction created when it meets capacity, dependencies, customers, systems, and team energy.
The practical implication is simple: if the organization does not have a reliable way to hear from this layer, it is missing a strategic input.
One voice is easy to treat as local
Even when one manager raises a concern, the signal may be difficult to interpret. One team is overloaded. One dependency is delayed. One customer segment is not responding. Leadership may reasonably treat this as a local issue.
The meaning changes when similar signals appear across many teams. Ten managers in different parts of the organization may be describing variations of the same strategic constraint. That pattern is more useful than any single escalation.
The challenge is aggregation. Most organizations collect status, but they do not always collect operational interpretation. They know whether work is green, amber, or red. They know less about the assumptions behind those colors.
The green-to-red pattern
A familiar pattern follows. A project is green for several reporting cycles. Then it turns red suddenly. In hindsight, the warning signs were present earlier. They lived in resourcing conversations, informal concerns, delayed handoffs, or quiet changes in team priorities.
This is not necessarily dishonesty. Bent Flyvbjerg’s work on project bias points to a broader pattern: organizations often produce optimistic views of projects because incentives, confidence norms, and reporting structures shape what gets surfaced.
The result is a compressed version of reality. By the time the dashboard turns red, the system has often been absorbing weak signals for weeks or months.
Hearing honestly is an architecture question
The question is not whether leaders are approachable. Many are. The question is whether the organization is designed to let weak signals travel without relying on individual courage, timing, or personal relationships.
A useful signal architecture has three properties. It is continuous, so signals can appear between planning cycles. It is structured, so concerns can be compared and aggregated. And it is visible enough that patterns cannot disappear inside one reporting line.
When those properties are missing, middle managers adapt rationally. They choose what to raise, when to raise it, and how much to soften it. Over time, the organization hears less than it needs.
What to notice
The next time a project turns red, do not only ask what happened. Ask where the earlier signal lived. Was it in a formal system, an informal conversation, a capacity discussion, a dependency that had no owner, or a manager’s private judgment?
That question often reveals whether the organization has a reporting system, or a sensing system. Reporting describes the work. Sensing helps leadership understand whether the work is still connected to the strategy under real conditions.