When a business grows, coordination can start to grow faster than output.

More customers create more exceptions. More managers create more interfaces. New functions bring expertise, but they also bring reviews, reports and handoffs. Decisions that once took an afternoon begin to require a meeting, a paper and three approvals.

The cost is rarely visible in one budget line. It sits across calendars, delayed work, repeated analysis and senior people resolving issues that should never have reached them.

This is management load: the time and attention consumed by coordinating, checking, escalating and reconciling work beyond what the business genuinely needs to operate well.

Some management load is essential. A regulated decision should be reviewed. A major investment deserves challenge. A complex client commitment needs cross-functional input. The problem is accumulated load that adds motion without improving the decision, reducing risk or creating customer value.

Before changing the organisation chart, cutting management roles or buying another productivity tool, leadership teams should establish where that load actually sits. A 30-day Management Load Audit provides a practical way to do it.

Management load is not the same as being busy

A full diary is a weak diagnostic. A senior manager may spend most of the week in meetings and still be doing necessary, high-value work. Another may have fewer meetings but act as a permanent workaround for unclear accountability.

The better question is whether management activity improves an outcome that matters.

Useful management work does at least one of four things:

  • Sets direction or makes a consequential choice
  • Allocates scarce people, capital or capacity
  • Improves performance through challenge, coaching or problem-solving
  • Manages a material risk, dependency or exception

Management load is the residual: activity that persists because roles are unclear, information is unreliable, decisions are repeatedly reopened, routine work is escalated or processes cannot handle normal variation.

That distinction matters. An indiscriminate meeting reduction can remove valuable coordination while leaving the underlying ambiguity intact. A delayering exercise can widen spans without simplifying the work. Automation can make low-value output arrive faster and in greater volume.

The objective is not to minimise management. It is to improve management leverage.

Six signs that coordination is constraining growth

Management load tends to become visible through recurring symptoms.

1. Routine decisions rise to the leadership team

Pricing exceptions, recruitment choices, customer remedies and operating priorities reach senior forums because the boundary of authority is unclear or because previous decisions are routinely second-guessed.

The founder or CEO becomes the safest route to closure. This may feel efficient while the business is small. At scale, it creates a queue around one person's judgement and teaches managers to escalate rather than decide.

2. Meetings are used to manufacture ownership

When no individual has clear authority, more people are invited. The meeting becomes a substitute for accountability.

The visible cost is the time in the room. The larger cost is preparation, follow-up, rescheduling and the delay between identifying an issue and resolving it.

3. Managers reconcile the business by hand

Forecasts, customer data, delivery plans and financial views do not align, so managers spend time comparing spreadsheets, translating definitions and chasing updates.

They become a human integration layer between systems and functions. The work can look indispensable because the business relies on it, but that does not mean it should exist.

4. Normal variation is treated as an exception

Every growing business needs to accommodate some variation. Problems arise when common customer requests, delivery changes or supplier issues sit outside the standard operating model.

Managers then approve the same type of exception repeatedly. The organisation pays a coordination tax because it has not converted a recurring pattern into a policy, offer or process rule.

5. Reporting expands after every surprise

A missed target or operational failure often triggers a new report, checkpoint or control. These additions are rarely retired after the immediate concern has passed.

Over time, teams maintain layers of reporting for different audiences. Managers debate whose number is right instead of deciding what to do.

6. Technology increases output but does not remove work

AI can produce reports, analysis, content and code more quickly. If every output still passes through the same reviews, meetings and approval chain, total management load may increase.

More material is created, circulated and checked. The apparent productivity gain is absorbed by the operating model.

Run the audit across six lenses

The audit should be narrow enough to complete in 30 days. Select two or three business outcomes where management drag appears to be material, such as quote-to-order speed, project delivery, customer onboarding, monthly forecasting or product decisions.

Do not attempt to map the whole company. Use real work to expose patterns.

Lens 1: Leadership time

Review four representative weeks of diaries for the CEO and a small sample of senior and middle managers. Classify time into five categories:

  1. Direction and decisions
  2. Performance and problem-solving
  3. People leadership and capability building
  4. Coordination, reporting and review
  5. Administration and avoidable rework

The classification will require judgement. The purpose is not surveillance or precise time accounting. It is to identify where capable managers are spending substantial time without a corresponding business outcome.

Ask:

  • Which recurring activities could only be done by this role?
  • Which meetings exist because information is not trusted or ownership is unclear?
  • Which issues return without being resolved at source?
  • How much time is spent preparing material that does not change a decision?

An internal ratio can help the leadership team track progress:

Management load ratio = time spent on coordination, repeated review, avoidable escalation and rework divided by total sampled management time

This is not an external benchmark. Use it to compare roles, processes and progress within the business.

Lens 2: Decision flow

Select ten recurring decisions that materially affect customers, cash, capacity or risk. Examples include approving a non-standard price, prioritising product work, hiring into an unbudgeted role or resolving a delivery exception.

For each decision, record:

  • The trigger
  • The person expected to decide
  • The required inputs
  • Everyone who reviews or approves it
  • Elapsed time from trigger to decision
  • The number of times it is discussed
  • Whether it is later reopened
  • The consequence of delay

Look for decisions with no single owner, multiple effective vetoes, evidence requirements disproportionate to the risk or routine escalation to a more senior level.

A useful test is simple: could the named decision owner make the choice within clear limits without seeking informal permission? If not, authority exists on paper rather than in practice.

Lens 3: Management cadence

Build an inventory of recurring management meetings connected to the selected outcomes.

Record purpose, frequency, participants, preparation time, decisions expected and actions completed. Then examine overlap. A weekly trading meeting, monthly performance review and leadership meeting may all inspect the same numbers with slightly different packs.

Rate each forum:

  • Keep: it makes necessary decisions or resolves material dependencies
  • Redesign: the purpose matters, but membership, inputs or frequency are wrong
  • Merge: another forum covers substantially the same ground
  • Remove: it distributes information or repeats discussion without changing action

Do not judge a meeting only by whether participants enjoy it. Judge whether it produces a decision, intervention or shared understanding worth the collective time invested.

Lens 4: Handoffs and interfaces

Map how one piece of work moves across teams. Start with a customer or commercial outcome rather than a departmental process.

For a quote-to-order process, for example, trace the work from qualified opportunity to an accepted and deliverable commitment. Count:

  • Functional handoffs
  • System changes
  • Re-entry of the same data
  • Review loops
  • Queues and waiting time
  • Clarifications caused by missing information
  • Points where accountability changes

The greatest friction often sits at interfaces: sales to operations, operations to finance, product to commercial or central function to business unit. Each team may be locally efficient while the end-to-end outcome remains slow.

Lens 5: Exceptions and escalations

Review the last 20 material exceptions in the selected processes. Group them by cause rather than by incident.

Typical categories include:

  • Customer proposition does not fit the standard offer
  • Policy boundary is unclear
  • Data is missing or disputed
  • Decision authority is too low
  • Delivery capacity is not visible
  • Commercial promise conflicts with operational reality
  • Process cannot accommodate predictable variation

Then separate genuine exceptions from repeated patterns. If the same issue appears every week, it is part of the operating model whether or not the process documentation admits it.

The leadership decision is not merely how to handle the next case. It is whether to change the policy, product, process, capability or authority that creates the case.

Lens 6: Role clarity and management leverage

For roles most involved in the selected outcomes, compare the job as designed with the job as performed.

Ask each role holder:

  • Which outcomes are you personally accountable for?
  • Which decisions can you make without approval?
  • Where do you spend time compensating for gaps elsewhere?
  • What work reaches you that should be resolved one level lower?
  • What important work receives too little attention?

Look beyond job-title duplication. Two roles can have different titles but overlap in practice. One role can also contain several incompatible jobs, such as operational control, technical problem-solving and team leadership.

Span of control is relevant, but it is not a standalone answer. A wide span can work when work is standardised and teams are experienced. A narrow span may be justified when judgement, risk or coaching needs are high. The question is whether the management role adds leverage to the work beneath it.

Score the evidence, not the organisational politics

Score each lens from one to five for every selected business outcome:

Add two evidence fields beside the score:

  • Capacity consumed: approximate management hours per month
  • Outcome affected: revenue, margin, cash, customer, delivery, people or risk

This prevents the audit becoming a collection of complaints. A frustrating process is not automatically the highest priority. Focus on the issues that consume meaningful capacity and damage a material outcome.

Choose the right intervention

Different symptoms require different responses. Reorganisation is only one option.

If the work does not add value, stop it

Retire duplicate reports, inactive controls, standing meetings with no decision purpose and approvals introduced for risks that no longer exist.

Give each recurring management activity an owner and a review date. Work without an owner tends to survive because no one is authorised to remove it.

If ownership is unclear, redesign the decision

Name one decision owner. Define the input required, the boundaries of authority, the escalation triggers and the deadline.

Keep consultation proportionate. Input is not a collective veto. Once the decision is made, record it and prevent routine reopening unless new evidence meets an agreed threshold.

If exceptions are recurring, redesign the offer or process

Repeated commercial exceptions may indicate that the standard proposition no longer fits the market. Repeated operational escalations may reveal missing capacity rules or unclear service levels.

Turn frequent exceptions into explicit choices. Standardise what should be standard, price the variation that customers value and decline complexity that does not earn an adequate return.

If information is unreliable, repair the source

Do not solve a data-definition problem through additional reconciliation meetings. Establish the source, owner, definition and update frequency for the measures that drive recurring decisions.

A smaller set of trusted indicators is usually more useful than an expansive dashboard that requires manual explanation.

If a manager is acting as middleware, fix the interface

When a role exists mainly to chase, translate and reconcile, examine the process and system boundary beneath it.

The right answer may be a clearer handoff, shared workflow, common data definition, role redesign or selective automation. Removing the role without repairing the interface transfers the work to someone else.

If technology is involved, simplify before automating

Use AI or workflow automation after the business has decided what work should exist, where judgement is required and who owns the outcome.

An illustrative example is proposal approval. AI may help extract terms, compare them with policy and flag material deviations. It should not preserve six approval stages that arose historically and no longer reflect the level of risk.

The better sequence is:

  1. Remove unnecessary inputs and reviews
  2. Define decision authority and exception thresholds
  3. Standardise the information required
  4. Automate repeatable analysis and routing
  5. Measure elapsed time, quality and exceptions after implementation

A practical 30-day sequence

The audit should create visible decisions within a month.

Days 1 to 5: Define the outcomes

  • Select two or three outcomes where management drag appears material
  • Name an executive sponsor and a working owner
  • Agree the evidence to collect
  • State what will not be included

Days 6 to 15: Gather real work

  • Sample leadership and management calendars
  • Trace ten recurring decisions
  • Inventory the relevant management forums
  • Map one or two end-to-end workflows
  • Review 20 recent exceptions or escalations
  • Interview the roles carrying the greatest coordination burden

Days 16 to 22: Quantify and diagnose

  • Score the six audit lenses
  • Estimate management capacity consumed
  • Connect each issue to an affected business outcome
  • Identify root causes rather than visible symptoms
  • Test findings with the people who perform the work

Days 23 to 30: Decide and launch

  • Select no more than five interventions
  • Assign a named owner and 90-day outcome to each
  • Remove at least one low-value activity immediately
  • Pilot redesigned decision rights or workflow in one area
  • Establish a small baseline of speed, capacity and outcome measures

The audit is complete when the leadership team has made choices, not when it has produced a detailed presentation.

What the leadership team should review after 90 days

Measure whether the operating system has changed:

  • Has elapsed decision time fallen?
  • Are fewer routine issues reaching senior leaders?
  • Has recurring meeting and preparation time reduced?
  • Have handoffs or review loops been removed?
  • Are repeated exceptions declining?
  • Has management capacity moved into customers, people, growth or performance improvement?
  • Have customer, financial or risk outcomes improved or remained protected?

Some interventions will release cash or reduce overhead. Others will create capacity for growth without requiring equivalent additions to management. Both are valuable, but the intended benefit should be explicit.

The real test is management leverage

Scaling businesses do not become stronger simply by adding management. They become stronger when management makes the rest of the organisation clearer, faster and more capable.

That requires occasional subtraction. A report must stop. An approval must move closer to the work. A recurring exception must become a designed choice. A senior leader must release a decision they have outgrown.

A Management Load Audit gives the leadership team evidence to make those changes without relying on anecdotes or launching an indiscriminate restructure.

Allington Advisors helps founders, CEOs and leadership teams diagnose operating-model friction, clarify decision rights and release capacity for growth and performance. A focused diagnostic can provide a practical starting point where coordination has begun to constrain the business.