Spans and Layers Analysis for Organisation Design

A structure can look efficient on an organisation chart while creating slow decisions, overloaded leaders and avoidable management cost. The issue is rarely the number of boxes alone. Spans and layers analysis tests how work, accountability and managerial capacity are distributed through those boxes – and whether the design supports the operating model the organisation needs.

For senior HR, finance and transformation leaders, this is not a simple exercise in removing management roles. Done properly, it provides an evidence base for decisions about organisation design, workforce cost, job architecture, reward and leadership effectiveness. It identifies where management is genuinely required, where it has accumulated without clear purpose, and where a nominally lean structure has stretched managers beyond a sustainable level.

What spans and layers analysis measures

A span of control is the number of direct reports accountable to a manager. A layer is a level of management between the chief executive and the frontline, operational or specialist roles that deliver work. The analysis maps both measures across the organisation, usually by business area, geography, function, grade and employee population.

Neither measure is meaningful in isolation. A manager with four direct reports may be appropriately deployed when each person leads a major market, carries regulated accountability or manages a technically complex function. The same span may indicate unnecessary hierarchy where the work is standardised, co-located and supported by clear processes. Equally, a manager with 14 direct reports may perform well in a stable, transactional environment but struggle in a business facing rapid change, capability gaps or high employee-relations risk.

The purpose is therefore to understand the relationship between structure and work. A useful analysis considers management population and cost, the number of reporting layers, reporting-line patterns, management workload, decision rights, role clarity and business performance. It should also show how these factors vary rather than hiding them in a single organisation-wide average.

Why organisation-wide averages mislead

A headline average span can create false comfort. A business may report an average of seven direct reports per manager while combining a sales operation with spans of 12, a corporate function with spans of three and several isolated managerial roles with one or two reports. The average does not reveal whether any of those patterns is justified.

The same applies to layers. Some additional layers are necessary to manage scale, risk or geographical complexity. In multinational groups, country leadership, legal-entity responsibilities and local regulatory requirements may be legitimate features of the design. In other cases, layers persist because job titles, legacy structures or promotion practices have not kept pace with changes in technology, processes or customer demand.

The practical question is not, ‘How many layers should we have?’ It is, ‘Where does management add value, and where does the structure make accountability less clear?’ That distinction prevents a cost exercise from damaging operational control or employee experience.

Diagnose the structure before designing solutions

A credible review starts with clean workforce and reporting-line data. This typically includes employee identifiers, job titles, grades, cost, function, location, legal entity, manager relationships, vacancies and contingent labour where relevant. Data needs to be reconciled before conclusions are drawn. Duplicate records, acting arrangements, matrix reporting and inconsistent job titles can otherwise distort the picture.

The next step is to establish a consistent management definition. This may include people managers, senior individual contributors with formal leadership accountability, project leaders and executive roles, but the treatment should be explicit. A role title containing ‘manager’ is not sufficient evidence of a genuine managerial job.

Quantitative mapping then identifies patterns requiring investigation: very narrow spans, unusually broad spans, long chains of command, manager-to-manager reporting, isolated roles and concentrations of leadership cost. It is useful to test these patterns against grade and job architecture. A global grading framework can reveal whether apparent layers reflect meaningful differences in role size or simply inconsistent levelling.

Data alone cannot establish whether a structure works. Interviews with leaders and managers should test how decisions are made, how priorities are set, whether managers coach and develop their teams, and where work is delayed or duplicated. Employee listening, attrition, absence, engagement and customer measures can add useful context. The aim is to connect structural symptoms with operational evidence.

Assess the work managers actually do

Management capacity depends on more than direct-report numbers. A manager’s available time can be consumed by operational problem-solving, regulatory controls, technical approvals, stakeholder management, client delivery, hiring, performance management and change activity. Team maturity also matters. Experienced specialists working to clear standards usually require less day-to-day oversight than a newly formed team undertaking unfamiliar work.

This is why a target span should be a range, not a universal rule. The organisation can define principles for different environments – for example, a broader range for stable operations and a narrower range where work is complex, dispersed or safety-critical. These principles should inform judgement rather than replace it.

Turning findings into organisation design choices

Once the evidence is clear, options can be modelled. Some roles may be consolidated to create broader, more viable managerial spans. In other areas, removing a layer may bring decision-makers closer to customers and frontline teams. A few functions may require investment in management capacity because leaders have too many direct reports to set expectations, develop capability or manage performance properly.

The best option is rarely the one with the lowest immediate payroll cost. Removing a managerial layer can reduce cost and shorten decision paths, but may transfer workload to senior leaders, weaken control or create excessively large teams. Conversely, retaining a layer may be commercially sound when it protects delivery, manages risk or enables growth.

Each option should be tested against a clear set of criteria: affordability, accountabilities, delivery risk, talent impact, employee relations, governance and implementation feasibility. Scenario modelling should quantify role changes, one-off restructuring costs, recurring savings, pay implications and the likely effect on management ratios. Where roles are redesigned, job evaluation should establish whether the revised accountabilities warrant different grades or pay ranges.

This is also where reward considerations become material. Narrow spans can be reinforced by pay and career structures that equate progression with acquiring a team. A stronger job architecture creates credible expert and project leadership pathways alongside people management. It enables employees to develop and be rewarded for broader contribution without creating managerial roles that the operating model does not need.

Implement with discipline, not just a revised chart

An organisation chart is an output, not an implementation plan. Reporting-line changes need defined decision rights, revised role profiles, leadership communication and a practical approach to consultation where applicable. Managers taking on larger teams may require support in delegation, performance management and prioritisation. Newly broadened roles need clarity about what stops as well as what is added.

Governance should continue after the change goes live. A small set of structural measures can be monitored through workforce planning and people reporting: span distributions, layers by function, management cost, vacancy patterns, internal progression, regretted attrition and engagement. The measures should be reviewed alongside business outcomes, not treated as a stand-alone HR scorecard.

For complex organisations, a pilot can be more informative than a large-scale redesign. Testing the principles in one business unit exposes data issues, local constraints and unintended consequences early. It also gives leaders practical evidence on whether new spans and accountabilities improve decision-making and execution.

Reward Associates approaches this work as a connected organisation, workforce and reward question. The analysis must be sufficiently rigorous for board scrutiny, but practical enough to guide role-level decisions and implementation.

A well-designed structure should make it easier for people to know who decides, who leads and where to take action. When spans and layers are reviewed with that outcome in mind, the result is not simply fewer boxes on a chart. It is clearer accountability, better use of leadership capacity and a workforce model that can support the next business decision rather than slow it down.