Span of Control Analysis

Definition

The problem it addresses

Districts are routinely handed a benchmark ratio and told their spans are too wide or too narrow. The ratio travels well and explains nothing.

Two leaders with identical headcounts can face entirely different jobs. One supervises a team doing standardized, measurable, related work, with experienced staff and documented processes. The other supervises unrelated project work with no performance measures, carries a caseload of her own, and is still learning half of what her people do. The second job is harder at half the headcount.

A review that reports span ratios alone has stopped short of the analysis. Worse, it gives a cabinet a number to argue about instead of a condition to fix.

How it works

Each supervisory relationship is scored against seven indicators. The more indicators present, the wider the span a leader can reasonably carry.

• Similar experience, knowledge, and skills. Supervising one kind of professional is a narrower job than supervising six kinds, because the supervisor can hold one body of practice in mind.
• Mastery employees. Staff who have mastered their work need direction less often. A team of new hires consumes supervision at several times the rate.
• Related activities. Work that connects is supervised together. Work that only shares a reporting line is supervised one item at a time.
• Results identifiable by metrics. Where output is measured, the supervisor can manage by exception. Where it is not, the only way to know is to watch.
• Work is routine. Routine work generates fewer decisions that have to travel up.
• Standardized processes. A documented process answers questions the supervisor would otherwise answer personally, one person at a time.
• The majority of the leadership role is managing. A director who carries her own caseload, runs a program, and supervises nine people is doing three jobs. The span is the smallest of her problems.

The analysis is run position by position across the district, and the pattern matters more than any single result. Spans that are all wide suggest a structure sized for a smaller organization. Spans that are all narrow suggest layers that were added to solve something other than workload.

Evidence required

• Organizational charts by department, and the employee list they were built from
• Job descriptions, including the supervisory responsibilities each one assigns
• Job analysis questionnaires completed by position, reporting actual direct reports
• Position control records, to confirm who is filled, vacant, and held
• Whatever performance measures each department currently reports
• Interviews, to establish which parts of a role are managing and which are producing

The four documentary sources disagree more often than districts expect. Reconciling them is part of the analysis and is frequently its first useful product.

Indicators and measures

• Direct reports by position, reconciled across chart, job description, questionnaire, and employee list
• Indicators present, scored one to seven per supervisory relationship
• Levels of hierarchy established between the superintendent and the front line
• Positions supervising positions of the same or higher classification
• Functions with no supervisor of record
• Share of a leadership role spent managing, from questionnaire and interview
• Peer comparison of executive-level direct reports for districts of similar size

Appropriate uses

• Inside an organizational review, to explain why a structure strains where it does
• When designing structure options, to test whether a proposed chart is supervisable
• During a superintendent transition, to understand the inherited structure quickly
• Alongside a maturity assessment, because standardized processes and measured results are maturity conditions and they widen the defensible span
• To decide whether a department needs a layer or needs process documentation

Inappropriate uses

• As a staffing reduction formula. Span analysis describes supervisory load, and it carries no opinion about how many people the district needs.
• As an evaluation of the supervisor. A wide span is a design condition.
• As a stand-alone benchmark. Peer ratios frame a finding and rarely settle one.
• Against schools without adjustment. A principal's span is structured differently from a central office director's, and the indicators apply differently.

Limitations

The indicators are qualitative. Two analysts can score the same relationship one indicator apart, which is why LEAN Frog scores against documented evidence and interview record rather than impression.

The method also says nothing about whether the work itself should exist. A perfectly supervisable structure can be organized around functions the district no longer needs. Span analysis belongs next to a work and ownership map, not in place of one.

Finally, the analysis measures a moment. A district with heavy retirement exposure in its leadership ranks will lose its mastery employees on a known schedule, and spans that work today will not work then.

An example

One school system's review counted twenty-three positions reporting directly to the superintendent, with no established levels of hierarchy across the central office. A coordinator could supervise a coordinator. Job descriptions for supervisory titles assigned no supervision, while questionnaire returns from the same positions reported anywhere from zero to more than two hundred direct reports.

The headcount was the least interesting finding. Of the seven indicators, the superintendent's span carried almost none: the reports did unrelated work, few of their functions were measured, and several were the only person in the district doing what they did. That combination is what made the number unworkable.

Three months after the report, the district's own revised structure reduced the superintendent's direct reports from twenty-three to six plus the principal group, using two assistant superintendents. The district reached the span math its own way, which is the outcome the analysis is built to support.