Hierarchy becomes expensive when information travels upward so that a decision can travel back down. But removing levels without redesigning authority can leave managers overloaded and employees uncertain.
A useful hierarchy provides direction, resolves tradeoffs and supports people doing the work. Its effectiveness depends on what each level contributes, rather than how flat the chart appears.
Give every level a distinct contribution
- Frontline leadership often needs to maintain daily conditions, develop capability and respond to abnormalities.
- A broader management level may coordinate capacity across teams and remove recurring constraints.
- Executives allocate resources and make strategic tradeoffs.
These are examples, not universal job boundaries. Define the actual contribution of each level in your context.
If two adjacent levels make the same decisions and review identical information, investigate duplication. If important cross-team decisions have no clear home, removing a layer may worsen the gap.
Delegate within clear boundaries
Delegation requires an outcome, authority, resources and a review mechanism. It does not mean assigning a task while keeping every meaningful choice at the top.
Specify acceptable cost, risk, timing and policy boundaries. Agree what evidence should trigger escalation and what the employee should do while waiting.
For a hypothetical assembly operation, a team leader can reallocate trained people within the shift and stop work for an abnormal condition. Changing a validated technical method requires the relevant approval. These boundaries allow speed without pretending that every decision is equivalent.
Distinguish communication from authorization
Employees should be able to exchange relevant information across functions without routing every message through their managers.
Direct communication does not automatically transfer authority. Two specialists can resolve a technical question within an agreed scope; they should not silently change the commercial commitment or an approved design baseline.
Use horizontal relationships to accelerate understanding, with clear rules for recording consequential decisions. This preserves accountability while avoiding unnecessary chains of correspondence.
Set spans around management work
There is no universally correct number of direct reports. Consider task variety, employee experience, geographic distribution, risk, standardization and the support available to the manager.
A stable team doing similar work may need less individual coordination than a dispersed group handling unique, uncertain assignments. A wider span can reduce layers while making coaching and exception handling impractical.
Evaluate the manager’s actual workload. Include performance conversations, capability development, recruitment, change work and urgent decisions. Reporting volume alone does not describe the role.
Use escalation as a designed service
Define which issues need immediate escalation, which can wait for a review and what information must accompany them.
An effective escalation states the condition, its impact, options and the decision required. Set a response expectation and identify a substitute when the decision owner is unavailable.
Review recurring escalations. If the same decision repeatedly reaches an executive, the organization may need a clearer rule, stronger local capability or a different allocation of authority.
Evaluate the design through outcomes
Track decision lead time, management overload, unresolved exceptions and the quality of coaching. Listen to employees who cannot get timely decisions or whose decisions are repeatedly reversed.
Before announcing a flatter organization, redesign one decision pathway. Move the decision to the lowest level with the competence, information and authority to manage its consequences. Provide support and verify the result.
Hierarchy should make the organization more capable of acting. Fewer boxes matter only when the work and the decisions improve.