How To Use Anti-Patterns
Treat each anti-pattern as a signal, not a verdict. A wide span may be fine in a repeatable operations team. A deep chain may be necessary in regulated work. The point is to notice the pattern, name the risk, and decide what evidence to gather next.
In the embedded examples, red nodes mark the likely structural issue, amber nodes show adjacent pressure, and green nodes provide a healthier comparison. The descriptions on the nodes explain what to inspect.
Diagnostic rule: if the chart shape makes it hard to explain who owns the work, who coaches the people, or who makes the decision, the structure deserves a closer look.
The Overloaded Mixed-Function Span
A wide span is not automatically a problem. The risk rises when one manager owns many unrelated functions. The manager cannot coach every discipline well, context-switching increases, and every small decision can become a bottleneck.
Questions to ask
- Are these reports doing similar work, or is the manager supervising unrelated disciplines?
- Which decisions wait for this manager because nobody else has clear authority?
- Would grouping the work differently improve coaching, escalation, or service quality?
For benchmarks and a more detailed audit, use the Span Of Control guide.
The Deep Chain With Thin Layers
A deep chain appears when each manager has only one or two direct reports and each layer mostly relays information. It can slow decisions, distort context, and create management titles that do not carry distinct authority.
Questions to ask
- Which layers make distinct decisions, and which mostly approve or forward work?
- How many hops does front-line information travel before it reaches someone who can act?
- Could a layer be compressed without making the remaining manager's span unsustainable?
See Layers And Organizational Depth for a fuller process for counting layers and deciding when to compress them.
The Orphan Role
An orphan role is placed far from the work it serves. It often happens because a team needed help quickly and the role was assigned to the nearest available manager. Over time, the placement becomes normal even if it weakens coaching and handoffs.
Questions to ask
- Does the manager have enough context to coach the person and judge tradeoffs?
- Where do most handoffs, escalations, and quality issues happen?
- Is the role placed for today's work, or because of a historical compromise?
Chart Habits That Create Bad Decisions
Some anti-patterns are not visible as a shape. They come from how the chart is maintained and presented.
The stale chart
The chart was accurate months ago, but hires, exits, and informal reporting changes were never reflected. Decisions based on it are now based on old structure.
The executive-only chart
The chart shows the CEO's direct reports and maybe one layer below. It may work for a board update, but it cannot support span, layer, or role clarity analysis.
The aspirational chart
The chart shows the future state as if it already exists. Planned but unfilled roles appear operational, which makes current-state diagnosis unreliable.
The contractor-blind chart
Contractors, fractional leaders, and outsourced teams are omitted even when they own critical work. That hides real dependencies and escalation paths.
What To Do Next
| Anti-pattern | First fix | Better follow-up |
|---|---|---|
| Overloaded span | List the decisions and support needs flowing through the manager. | Split by discipline, workflow, geography, or customer segment only if the work truly differs. |
| Deep chain | Identify which layer makes distinct decisions. | Compress pass-through layers and move decision rights explicitly. |
| Orphan role | Map the role's main handoffs and escalations. | Move the role closer to the work, or document why the unusual placement is intentional. |
| Stale or aspirational chart | Separate current-state structure from planned future-state structure. | Make one owner responsible for chart updates after hiring, exits, and reorg changes. |
Model the current structure, then inspect spans, layers, orphan roles, and planned changes before you redesign the organization.
Create org chartSources And Further Reading
- Jay R. Galbraith, Designing Organizations.
- Henry Mintzberg, Structure in Fives: Designing Effective Organizations.
- David A. Nadler and Michael L. Tushman, Competing by Design.
Continue Reading
The most common visual anti-patterns usually point back to spans and layers.
Next guideSpan Of Control
Learn when a manager's span is too wide, too narrow, or mismatched for the work.