What it means
At its simplest a hierarchy is a chart of reporting lines, but the useful version also records what each level may decide. A team leader might approve spending up to a set amount, a divisional director rather more, and anything above that goes to the board, so authority narrows as the value rises.
Without those limits the chart is only a seating plan. Two numbers describe most hierarchies.
Span of control is the average number of people reporting to each manager, and the number of layers is how many management levels separate the top from the front line. Widening spans reduces layers and cost but demands more capable, better-supported managers, while narrow spans give closer supervision at the price of more management salaries and slower decisions.
The structure has a direct financial consequence, because every layer is paid for. Tall organisations with narrow spans carry a higher ratio of managers to producers, and each additional layer also adds delay and distortion as information is summarised on its way up.
Flatter structures are cheaper but can overwhelm managers and leave junior staff without development. Hierarchies are rarely as simple as a single tree in practice.
Matrix structures give people a functional manager and a project or regional manager at the same time, which suits businesses that need both deep expertise and local responsiveness but creates ambiguity about who decides. Some firms deliberately keep a flat formal structure while relying on informal seniority, which can be fast but makes accountability harder to trace.
The nuance worth remembering is that hierarchy describes authority, not value. A skilled specialist several layers down may matter far more to results than a manager above them, and structures that confuse rank with contribution tend to lose their best technical people.
Well-run firms often build separate progression routes so that experts can advance without having to manage anyone.
In practice
Real-world examples.
Example
A contact centre with 600 agents reviews its structure and finds an average span of 5. Moving to a span of 10, supported by better scheduling software and clearer escalation rules, removes a whole management layer and cuts supervisory costs by nearly half.
Example
A hospital trust runs a matrix in which nurses report to a ward manager for daily work and to a professional lead for standards and training. The arrangement works because the two roles have written boundaries, with the ward manager owning rotas and the professional lead owning competence.
Example
A 40-person startup keeps a deliberately flat structure with everyone reporting to two founders. At around 70 staff the founders are approving holiday requests at midnight, and the company introduces four team leads with defined approval limits.
Formula
Calculation
Managers required at a level = employees at the level below / span of control
Consider a services company with 1,296 front-line staff and an average span of control of 6. It needs 1,296 / 6 = 216 team leaders, then 216 / 6 = 36 managers, then 36 / 6 = 6 directors, and those 6 report to 1 chief executive. Total management is 216 + 36 + 6 + 1 = 259 people, total headcount is 1,296 + 259 = 1,555, and managers are 259 / 1,555 = 16.7% of the workforce across five levels.
Now widen the average span to 12. The company needs 1,296 / 12 = 108 team leaders, then 108 / 12 = 9 managers, and those 9 report to the chief executive, so management totals 108 + 9 + 1 = 118 people. Headcount falls to 1,296 + 118 = 1,414, managers are 118 / 1,414 = 8.3% of the workforce, and the structure has four levels instead of five.
The difference is 259 - 118 = 141 management roles. At an average fully loaded cost of $95,000, that is 141 x $95,000 = $13,395,000 a year, which is why span of control is one of the first things reviewed in a cost programme, and why the practical question is how many people a manager can genuinely support.Case study
Seen in the real world.
This is an illustrative, fictional example. Ravenscar Systems, an invented engineering software firm, grew to 900 staff and eight management layers, with several managers supervising only two or three people. Engineers complained that a decision to change a product specification took eleven weeks to travel up and back down.
A structural review found that four of the eight layers added no decision rights at all; they simply reviewed and forwarded. The company removed two layers, widened the average span from 4 to 9, and published a one-page table of what each remaining level could approve without escalation.
In this fictional account the annual saving was around $8,000,000, but the change managers valued more was that specification decisions moved to a fortnight. The hard part, as usual, was finding new roles for capable people whose jobs had consisted mostly of passing information upwards.
Watch out
Common mistakes.
- Drawing an organisation chart without setting decision rights, which leaves everyone clear on who reports to whom and unclear on who can actually approve anything.
- Removing management layers without widening spans deliberately, so the same work lands on fewer managers and quality of supervision collapses.
- Treating a place in the hierarchy as the only measure of seniority, which pushes strong specialists into management roles they neither want nor suit.
Questions
People also ask.
What is a normal span of control?
It varies hugely with the work, from around 4 or 5 where tasks are complex and bespoke to 15 or more in standardised operations.
Does a flat structure always mean faster decisions?
Not necessarily, because when formal authority is vague the decision simply waits for an informal consensus instead.
How does a matrix structure differ from a hierarchy?
A matrix is a hierarchy with two reporting lines rather than one, which helps balance functional depth against project or regional needs but requires explicit rules on who decides what.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related