A manager leaves an executive meeting with a message: the company needs to move faster on enterprise readiness.
Their team asks what that means. Should they pause the self-serve work? Should they rewrite the permissions model? Should they prioritize security controls over onboarding experiments? Which customer commitments change? Which dates move?
The manager cannot answer with a decision. They translate.
They explain the executive intent, summarize the likely implications, identify open questions, and promise to clarify the trade-offs. Then they take the team’s concerns back upward, turn operational constraints into leadership language, and wait for another round of interpretation.
Nothing about this is lazy. It is work. It is also a sign that the organization has given the manager responsibility for outcomes without enough authority to commit the team to a direction.
The Manager Becomes the Interface
Managers translate when decision authority and execution context live in different places.
Leadership owns strategy, budget, headcount, and cross-functional trade-offs. Teams own the operational detail: the code, customer reality, delivery constraints, technical risk, and the actual sequence of work. The manager sits between them.
If the manager can decide, they use both contexts to make a call. If they cannot, they become an interface layer. They convert executive direction into team language and team reality into executive language. They keep the packets moving.
The translation is necessary because the system is split. It becomes expensive when translation replaces judgment.
The same information travels repeatedly. Leadership asks for status. The manager gathers detail, compresses it, and presents. Leadership asks a question that only the team can answer. The manager goes back down, gathers more, compresses again, and returns. Each loop adds latency. Each summary loses detail. Each audience receives a version optimized for its own altitude.
Meetings Produce Alignment Without Commitment
Translation work concentrates in alignment meetings.
A feature request needs a decision. Engineering explains complexity. Product explains strategic value. Design explains user risk. Customer success explains account pressure. The manager synthesizes the perspectives and asks where the group can align.
The group cannot align because the issue is a trade-off, not a misunderstanding. Someone has to decide whether speed, quality, customer pressure, security, or roadmap coherence wins this time.
The manager lacks authority over all the functions involved. They can clarify positions, restate concerns, and document options. They cannot make the losing side accept the decision.
The meeting ends with more analysis, a smaller follow-up group, or another stakeholder review. Everyone participated. No one committed.
Organizations often read this as healthy collaboration. Sometimes it is. Often it is distributed decision deferral with good manners.
Translation Degrades Context
Every translation optimizes for an audience.
A customer problem is simplified for customer success. Customer success summarizes it for a manager. The manager reframes it for product. Product abstracts it into a requirement. Engineering implements the abstraction. By the time the solution returns to the customer, the original contour of the problem may be gone.
No one deliberately corrupted the signal. Each person made the message more usable for the next person. The accumulation changed it.
The same thing happens upward. Engineers describe a risk with technical detail. The manager turns it into a delivery risk. The director turns it into a timeline risk. Leadership hears that the team needs more time, not that a specific architectural assumption is breaking.
Direct channels can repair some of this. Engineers join customer calls. Executives hear from frontline teams. Product sits with support. Those bypasses preserve context, but they also reveal the weakness of the translation stack. The organization is paying for a layer and then bypassing it when accuracy matters.
Repackaging Is Safer Than Filtering
A manager with authority can filter. They can decide which details matter, what should be escalated, what can be resolved locally, and which stakeholder concerns are advisory.
A manager without authority repackages.
They forward more context than the executive needs because excluding a detail might be interpreted as hiding risk. They bring more stakeholder concerns to the team because dismissing a concern might exceed their scope. They write longer documents because clarity has to compensate for the absence of commitment.
Information overload follows. Executives receive too much operational detail. Teams receive too much strategic ambiguity. The manager becomes busy keeping both sides informed enough to avoid blame.
Filtering requires trust in the manager’s judgment. Organizations that withhold decision authority usually withhold that trust too.
Consensus Becomes the Substitute
Managers who cannot decide often become excellent consensus builders.
They learn stakeholder preferences. They pre-negotiate objections. They adjust language until each function can live with the proposal. They produce decisions that are acceptable to everyone with enough influence to block them.
Acceptable is not the same as good.
Consensus tends to favor the intersection of comfort zones. It avoids bold trade-offs because bold trade-offs make someone uncomfortable. It produces decisions that are defensible and slow, with risk distributed across the group.
The manager is rewarded for facilitation. Stakeholders feel heard. The process looks mature. The organization quietly stops developing managerial judgment because managers are practicing alignment more than decision-making.
Status Work Fills the Calendar
When managers translate instead of decide, status becomes their main product.
They collect updates from the team, aggregate them for leadership, receive leadership updates, decompose them for the team, compare notes with peer managers, and keep stakeholders synchronized. The calendar fills with syncs because the system depends on humans moving context between layers.
This is why adding managers often fails to increase speed. If managers are deciders, one decision can unblock many people. If managers are translators, each additional manager creates another interface to keep synchronized.
Narrow spans of control can then look necessary because translation work scales with every relationship. The organization says managers are overloaded. The deeper issue is that the role has been defined as communication bandwidth instead of decision leverage.
Clarity Work Expands Into the Decision Vacuum
Managers in translation mode write a lot.
Strategy notes. Priority summaries. Alignment memos. Decision logs that contain no decisions. Documents explaining what leadership likely means, what teams should probably emphasize, and which questions remain open.
This clarity work has value when it communicates a decision. It becomes circular when the decision has not been made.
The document helps teams interpret ambiguity. Teams act on their interpretation. Misalignment appears. The manager writes a clearer document. More edge cases are covered. The next ambiguity appears somewhere else because the document is still explaining around a choice that nobody has made.
Managers who can decide need fewer words. Commitment does much of the clarifying.
Talent Learns the Wrong Skill
Developing managers requires giving them decisions, consequences, and feedback.
Translation-mode organizations delegate coordination instead. Junior leaders attend meetings, take notes, write summaries, manage stakeholders, and learn how to keep information moving. They learn useful skills. They do not learn how to make trade-offs, say no, commit resources, or own a wrong call.
Later, they are promoted because they are good at coordination. They manage the way they were trained. More translation layers appear.
Decision-making training cannot fix this alone. Frameworks do not grant authority. Delegation workshops do not help a manager who still has to seek approval for every meaningful resource, priority, or technical choice.
Judgment develops when the structure allows judgment to be exercised.
What Translation Signals
Translation management signals a trust gap.
The organization distrusts both directions of travel. Executive guidance is assumed to need operational translation. Team interpretation is assumed to need mediation. Managers are trusted to stand between the two, while the actual decision authority stays elsewhere.
That compromise can reduce immediate miscommunication. It also prevents learning. Executives do not see where their guidance is unclear because managers smooth it. Teams do not learn to work directly with strategic context because managers buffer it. The manager absorbs distortion that should have become feedback.
Moving from translation to decision requires bounded authority: budget discretion, priority rights, hiring influence, technical scope, and permission to say no inside a defined area. The authority need not be unlimited. It has to be sufficient for the manager’s actual responsibilities.
Without that, middle management becomes bidirectional organizational debt: people bridging a gap the structure keeps recreating.
