A VP sends a note asking why a project is slipping. The manager forwards it to the team with “can someone give me the latest?” The team replies with blockers, partial explanations, and two questions about scope. The manager forwards the questions back up. The VP answers one, ignores the other, and adds a new request for a summary by Friday.
By the end of the day, the manager has sent twelve messages, created a status document, and scheduled a follow-up meeting because the thread is now too hard to follow.
No decision has been made. No priority has changed. No blocker has been removed.
The manager has been busy, visibly so. They have also functioned as a routing layer between people with context and people with authority. That is what happens when management is designed around visibility without matching decision rights.
How the Relay Role Forms
Managers rarely become message relays because they lack initiative. The role forms when the organization gives them responsibility for outcomes and withholds the authority required to shape those outcomes.
A manager is accountable for delivery while scope changes sit with product. Team health is theirs, while headcount and budget sit elsewhere. Execution is theirs, while technical decisions require architecture review, security approval, and executive sign-off. Stakeholder confidence is theirs, so every uncertainty has to be communicated upward before it becomes a surprise.
The manager still has work to do. They collect updates. They translate leadership requests into team questions. They turn team concerns into executive summaries. They route approvals through the right channels. They keep everyone informed enough that no one can claim they were left out.
Decision-making and information movement get separated. The people closest to the work have context. The people with authority sit elsewhere. The manager becomes the conduit between them.
Once that pattern stabilizes, relaying starts to look like management. The manager is in meetings all day. Their inbox is full. They produce reports, summaries, trackers, and alignment notes. The organization sees motion and calls it coordination.
Visibility Consumes the Job
Visibility requirements scale faster than teams expect.
A manager with one VP and a handful of stakeholders can keep updates lightweight. A manager with two VPs, a program office, three partner teams, a customer-facing deadline, and a weekly leadership review can spend most of the week preparing versions of the same information for different audiences.
The work changes under that load. Ambiguous problems are harder to report, so they get softened. Risks become watch items. Disagreements become open questions. A blocker becomes a dependency waiting for alignment. The manager learns to preserve accuracy while removing the sharp edges that would force a decision.
Reporting also rewards neutrality. If the manager adds interpretation, they can be accused of misrepresenting the team, alarming leadership, or taking a position before all stakeholders have weighed in. Repeating what others said is safer. Summarizing without judgment becomes the professional posture.
The organization receives detailed visibility into activity and weak visibility into consequence. Leadership knows what people are doing. It knows less about whether the work matters, whether the plan is still credible, or which trade-off needs to be made before Friday.
Consensus Turns Managers Into Schedulers
In some organizations, unilateral calls are treated as cultural failures. A good manager is expected to bring people along, gather input, create alignment, and avoid surprising stakeholders.
Those norms are useful until every contested decision requires consensus.
A team needs to decide whether to delay a feature or cut scope. The manager cannot make the call because product, design, sales, support, and engineering all have stakes in the answer. They schedule a meeting. The meeting surfaces more questions. Someone asks for customer impact. Someone else wants engineering options. A follow-up is scheduled. By the time consensus forms, the decision window has narrowed enough that the team has fewer options than it started with.
The manager has facilitated well. They have also avoided the managerial act the situation required: naming the trade-off and making, or escalating, a clear recommendation.
Consensus culture produces a specific kind of relay manager. They are careful, inclusive, and process-oriented. They document conversations. They make sure no one is skipped. When interests conflict, they do not resolve the conflict because the culture has made resolution indistinguishable from overreach.
Escalation Becomes the Safe Move
Managers learn quickly which mistakes are punished.
A bad decision can be traced. Someone approved the scope change. Someone chose the vendor. Someone told the team to ship with the known limitation. A slow escalation is harder to discipline. The manager was being careful. They were ensuring visibility. They were waiting for alignment.
The incentive is plain enough. When a decision is ambiguous, escalate. When direction is unclear, ask for clarification. When two stakeholders conflict, schedule a meeting. When risk appears, route it upward before touching it.
Over time this becomes muscle memory. The manager no longer asks, “What decision should I make inside my scope?” They ask, “Who needs to be aware before I move?”
The organization may complain that managers are passive, but it often designed passivity into the role. It punishes visible judgment errors and tolerates invisible delay.
What Relay Work Looks Like
Relay management has recognizable artifacts.
The inbox becomes the primary workstream. Messages arrive as requests, questions, risks, and updates. The manager forwards them with a short prompt: “thoughts?”, “FYI”, “can we align?”, “please review.” Each forward is reasonable. Together they create branching threads where the same decision travels through several people who cannot make it.
Meetings multiply around those threads. A status sync is scheduled because the email chain lost context. A priority meeting is scheduled because two managers interpreted the same update differently. A decision meeting is scheduled with everyone who might object, then turns into information gathering because the decision was never framed clearly enough to make.
Summaries become another layer of motion. The manager turns team detail into executive language and executive direction into team language. That work can be valuable when it adds judgment: what matters, what changed, what needs a decision, what can be ignored. Relay summaries mostly compress. They make information shorter without making it more actionable.
Escalations activate before resolution attempts. A dependency is blocked by another team, so the manager emails that team’s manager, who emails a director, who asks for a meeting. The original problem may have needed two individual contributors and a priority call. Instead it enters the management transport system.
The delay does not feel dramatic while it is happening. Everyone is responding. Everyone is keeping people informed. The decision is simply always one layer away.
Where the Pattern Fails
Relay management can look functional when conditions are stable. It breaks when the organization needs judgment under pressure.
A production issue does not wait for a reporting chain. Someone has to decide whether to roll back, disable a feature, notify customers, or accept degraded service while engineers investigate. A relay manager escalates the situation, schedules the emergency call, and documents the current state. Those actions may be necessary. They are insufficient if no one with ground-level context is empowered to act.
Cross-functional projects expose the same weakness more slowly. Each manager relays status inside their own vertical. Integration decisions require horizontal coordination, but the managers involved cannot resolve trade-offs across reporting lines. The issue moves up to the lowest common executive, who lacks operational detail and asks for options. The managers relay the request downward, summarize the responses upward, and wait.
Strategic changes create another failure mode. Leadership announces a new priority. Relay managers forward the message to their teams. They do not stop old work, reorder commitments, or interpret what the strategy means locally. Teams keep moving on old assumptions while asking whether the new direction applies to them. Questions travel upward. Clarifications travel downward. The strategy arrives everywhere and changes little.
High performers eventually route around the system. They coordinate directly with peers, make small decisions without waiting, and involve managers only when process requires it. Relay managers often respond by inserting themselves back into the flow: more CCs, more required meetings, more visibility. The bypass threatens the only function the structure has left them.
Why Organizations Keep Relay Managers
Relay management persists because it serves leadership needs that are easier to feel than to admit.
It preserves centralized control. Managers who mainly relay do not make many independent calls. Ambiguity travels upward. Direction travels downward. Executives retain decision authority while management layers handle the operational burden of moving information.
It diffuses failure. When a project misses, leadership can point to execution. Managers can point to unclear direction, changing requirements, or delayed approvals. Everyone can show the messages they sent. The paper trail is thick enough to obscure where authority actually sat.
It produces visible activity. Relay managers attend many meetings, maintain dashboards, send updates, and keep stakeholders informed. A manager who makes crisp decisions may generate less visible exhaust. They decide, communicate the call, and move on. In organizations that reward busyness and stakeholder comfort, the relay manager looks safer.
It avoids real delegation. Giving managers authority means trusting judgment, accepting variation across teams, and tolerating some wrong calls. Relay management lets executives keep control while believing they have delegated management. The cost arrives later as delay, weak ownership, and teams trained to wait.
The Structures That Create Relays
Several common design choices produce relay behavior even when the people in the roles are capable.
Large spans of control reduce a manager’s ability to understand work deeply enough to make good decisions. A manager with too many direct reports and too many projects can still forward messages, gather updates, and schedule group discussions. They cannot make informed calls at the same rate. Relaying scales better than judgment.
Approval-heavy governance teaches managers to route decisions instead of making them. Architecture review, budget approval, security sign-off, legal review, and executive escalation may all be necessary for certain decisions. When ordinary work has to pass through the same machinery, the manager becomes a process coordinator.
Matrix structures blur authority. An employee may have a functional manager for development and a product manager for priorities. If those managers disagree, the decision travels up both chains until someone with authority over both sides can resolve it. The managers in the middle are not coordinating the decision so much as transporting it.
Reporting tools can reinforce the pattern. Dashboards and status systems show what is happening, but they rarely say what should be done. Managers spend time keeping the system accurate because leadership wants visibility. When a choice is required, the tool offers evidence, not authority.
What Management Requires
Management needs more than information movement. It needs bounded authority.
Managers need a defined scope where they can make binding decisions without approval. That scope can be narrow, but it has to be real. If every meaningful choice escalates, the manager is a messenger with a title.
They need resource authority proportional to their accountability. A manager responsible for delivery needs some ability to move time, attention, people, or budget. Otherwise every resource trade-off becomes a request to someone else.
They need the authority to set local priorities and say no. Stakeholders will always generate more demand than the team can absorb. A manager who cannot reject low-value work becomes a relay for every request that arrives with enough seniority attached.
They also need outcome-based accountability. If managers are measured on communication, visibility, process compliance, and stakeholder satisfaction, they will optimize for relay work. If they are measured on decisions, delivery, team effectiveness, and judgment under ambiguity, the job changes.
None of this removes the need for communication. Good managers still summarize, escalate, align, and report. The difference is that those actions support decisions rather than replace them.
The Cost
Relay management turns organizational layers into information transport.
Decisions that should take hours take weeks because they move through people who can explain the problem but cannot resolve it. Projects stall while managers seek alignment. Teams wait for calls from executives who have less context than the managers below them. Crises route upward until someone senior enough feels allowed to act.
The human cost is quieter. People who want agency leave or learn to work around management. People comfortable with low authority remain. The organization gradually selects for compliance, patience, and political navigation over initiative.
The central loss is judgment. Management exists because some decisions require both local context and organizational understanding. When managers become message relays, that judgment disappears from the middle of the system. Information still moves. Reports still arrive. Meetings still happen.
The organization can describe what is happening in detail and still fail to decide what to do next.
