Organisation Design for Scaling Companies: When the Structure That Got You Here Stops Working

TL;DR: Organisation design is the deliberate choice of how work, authority and people are arranged so a company can execute its strategy. In a scaling company it usually breaks in three places at once: spans and layers drift (too many managers with too few reports, too many levels between the top and the front line), decision rights blur (decisions escalate past the people who should own them), and the workforce plan stops matching the business plan (headcount follows budget requests rather than the operating model). Bain’s spans-and-layers database puts the average company at six to seven direct reports per manager and eight to nine layers, against 10 to 15 reports and no more than seven layers for the best performers. Fix the three together, not one at a time, and review them on a fixed cadence rather than waiting for a crisis.

Most companies do not decide to become complicated. They add a manager when a team gets busy, a new function when a customer asks for something, a layer when a founder can no longer see everything, and an approval step after every mistake. Each choice is sensible on the day it is made. Three years later, the same company finds that decisions take weeks, two people believe they own the same outcome, and nobody can explain why headcount grew faster than revenue.

That is the moment organisation design stops being an HR topic and becomes a business one. People strategy is business strategy, and the structure is where that principle either holds or fails.

This article is about what to change when the structure that got a company here stops working: the arithmetic of spans and layers, the allocation of decision rights, and a workforce plan built from the business plan rather than the budget cycle.

What Is Organisation Design?

Organisation design is the process of shaping a company’s structure, roles, reporting lines, decision rights and ways of working so that the organisation can deliver its strategy. It answers four questions: what work needs to be done, who does it, who decides, and how the pieces connect.

It is broader than restructuring. A restructure changes boxes and reporting lines. Organisation design also covers who holds authority, how many people each manager can lead well, how teams hand work to each other, and how the shape of the workforce should change as the business plan changes.

For a scaling company, the useful definition is practical: organisation design is the discipline of keeping the structure in step with the strategy as both change. The Astravise perspective on why the org chart was designed for a world that no longer exists makes the case that a chart is a snapshot, not a design. This article picks up from there and deals with what to change underneath the chart.

The pressure to get it right has increased. McKinsey’s State of Organizations 2023, a survey of more than 2,500 leaders in organisations with at least 1,000 employees across countries including India, found that around 40% of respondents point to complex organisational structure as a cause of inefficiency, and a similar proportion cite unclear roles and responsibilities. Only 14% said their organisation had adopted a fully agile operating model.

The Signs Your Organisation’s Structure Has Stopped Working

Structural problems show up as operational symptoms long before anyone calls them structural. The signs below are mechanical, which makes them measurable:

Decisions escalate past the people who should own them. Routine approvals reach the founder, the CEO or the parent company because nobody below is sure they have the authority.

• Two people believe they own the same outcome. Duplicated roles appear after acquisitions, new market entries or a GCC build, and each role holder defends a different version of the answer.

• Spans are wildly uneven. One manager has 15 direct reports and no time to coach any of them; the manager next door has two and spends the day in meetings.

• Layers have multiplied. A frontline issue passes through four or five levels before it reaches someone who can act.

• Handoffs have no owner. Work stalls between teams because each team’s process ends at its own boundary.

• Headcount grows faster than output. New hires are approved one requisition at a time, and nobody can connect them to a line in the business plan.

• Forums multiply. More steering committees, more review meetings and more reporting packs, with no corresponding improvement in decisions.

The leadership-level version of these symptoms, including decision fatigue at the top and the pull of promoter-led companies to keep decisions central, is covered in the Astravise analysis of CXO blind spots that appear only after scaling. The sections that follow set out the structural fixes.

Spans and Layers: The Arithmetic of a Lean Organisation

Span of control is the number of direct reports a manager has. Layers are the number of management levels between the top of the organisation and the frontline employee. Together they determine how fast information and decisions move, and how much of the payroll goes on management rather than delivery.

Bain & Company’s spans-and-layers database, covering more than 125 global companies, gives the standing benchmark:

The companies in Bain’s database improved spans by 24% and reduced layers by 14% on average. The benchmark was published in 2010 and is still widely cited; the direction of travel it describes has not changed.

The right span depends on the work. Bain notes that skills-based roles, such as engineers or brand managers, are usually well served by a span of six to eight, while task-based roles, such as call-centre or shop-floor supervisors, can run at 15 or more. A single company-wide target is rarely right. Set targets by function.

A quick self-diagnostic:

1. Pull the reporting lines from the HR system and count direct reports for every manager.

2. Flag every manager with fewer than four direct reports, and ask whether the role is a management role or a senior individual contributor role with a management title.

3. Count the layers from the CEO to the most junior person in each function. Any function deeper than the company average needs a reason.

4. Check for dual reporting lines. These are common in GCCs, where a team reports locally for administration and to the parent for work, and they distort both counts.

Narrow spans are rarely a deliberate choice. They usually come from promotions used as retention tools, or from a new manager hired for every new team. Fixing them is less about removing people than about redefining which roles manage and which roles do the work.

Decision Rights: Who Actually Owns the Call

Decision rights define who has the authority to make a specific decision, who must be consulted before it is made, and who is informed afterwards. A decision rights framework lists the decisions that matter, assigns a single owner to each, and sets the thresholds above which a decision moves up.

Most scaling companies have decision rights by habit rather than by design. The founder approved hires when there were 20 people, so the founder still approves hires at 400. The parent company signed off vendor contracts when the India entity was a pilot, so it still signs them off when the entity runs a full function.

A practical decision rights framework has four parts:

1. A decision inventory. List the 30 to 50 recurring decisions that drive the business: pricing, hiring above a grade, capital spend, vendor selection, product release, customer exceptions.

2. One owner per decision. Not a committee and not two names. A committee can advise; one person decides.

3. Thresholds. Value, risk or strategic thresholds above which the decision moves to the next level. Below the threshold, the owner decides without escalation.

4. Escalation rules. What happens when the owner and a stakeholder disagree, who breaks the tie, and how quickly.

For companies with a GCC or shared services centre, the hardest decision rights question is how much authority sits in India and how much stays with headquarters. The Astravise piece on the trade-offs management must make at scale sets out that autonomy-versus-centralisation choice from the board’s side.

For promoter-led and family businesses, decision rights also means separating the owner’s role from the board’s role and the management team’s role. The Astravise view on clarity, structure and succession in family businesses covers that separation from the finance side.

RACI vs Decision Rights: Why Most RACI Charts Fail at Scale

A RACI matrix assigns four roles to each task in a process: Responsible (does the work), Accountable (owns the outcome), Consulted (gives input before) and Informed (told after). It is a useful tool for documenting a process. It is often the wrong tool for allocating authority.

The difference matters:

RACI charts fail at scale for three recurring reasons. First, several people are marked Accountable, so nobody is. Second, the Consulted column grows until every decision needs six sign-offs. Third, the chart is built once, filed, and never updated as roles change.

The fix is to separate the two. Use a decision rights framework to decide who owns the call, then use a RACI for the processes that sit underneath each decision. Once decision rights are clear, they cascade into people systems. The Astravise guide to performance management that works at scale shows how that plays out when an employee in a dual-reporting GCC has two managers with a view on the same rating.

Workforce Planning: Tying Headcount to the Business Plan, Not the Budget Cycle

Strategic workforce planning is the process of working out the number, type, location and cost of people the business will need to deliver its plan, and then closing the gap between that and the current workforce. It is different from a headcount budget. A headcount budget says how many people each department may hire. A workforce plan says which capabilities the business needs, when, and in what shape.

In a scaling company, the headcount budget usually wins by default. Each function submits requests, finance trims them to fit the cost envelope, and the result is a list of approved roles that reflects last year’s structure plus growth. The operating model the business actually needs never enters the conversation.

A workforce plan tied to the business plan works in the other direction:

1. Start from the business plan. Revenue, markets, products, delivery model and the operating model changes planned for the next two to three years.

2. Translate into capabilities. What work will the business need done, and at what volume? Which of it is core, which can sit in a shared services centre, and which can be bought in?

3. Model the structure. Apply span and layer targets to the capability model, so the plan shows managers and individual contributors separately.

4. Compare to the current workforce. Identify roles to build, roles to redeploy and roles that will shrink.

5. Sequence the gap. Decide what to hire, what to develop and what to move, and in which order.

The plan also has to account for technology. Gartner’s December 2025 survey of 110 CHROs found that just over half of organisations had redesigned or redefined roles because of AI in the past year, and 78% agreed that workflows and roles will need to change to get the most from their AI investments. A workforce plan written without a view on which work will be automated will be out of date before it is approved.

Once the plan exists, execution becomes a hiring question. For a GCC building its first teams, the Astravise GCC talent playbook covers the hiring sequence and compensation design.

When to Restructure vs When to Patch

Not every structural problem needs a restructure. A restructure is expensive, disruptive and slow; a patch is cheap and fast but can bury a deeper problem. The test is whether the problem sits in one part of the organisation or in the design itself.

Three structural triggers usually justify a full redesign. The first is a span-and-layer breach across the organisation, not in one team. The second is decision-rights ambiguity exposed under stress, for example when a pricing crisis or a regulatory issue shows that nobody can make the call. The third is a business plan that has moved on while the workforce plan has not, such as a shift from product to services, a new market, or a decision to move a function into a GCC.

Gartner’s September 2026 prediction points in the same direction: organisations that establish continuous work redesign as a core capability will be twice as likely to sustain AI-driven work transformation by 2028. Gartner defines that capability as continuously redesigning workflows, decision rights, jobs and talent deployment. The practical lesson is that restructuring should become a regular review, not a once-a-decade event.

For founder-led companies, the right timing is usually before a funding round or a major market entry, when the structure is about to be tested and before new capital locks in the existing shape.

Organisation Design vs Organisational Structure vs the Org Chart

The three terms are often used interchangeably, but they describe different things:

• Organisation design is the process and the set of choices: how work, authority, roles and people are arranged to deliver the strategy.

• Organisational structure is the result of those choices: the reporting lines, the grouping of roles into functions, divisions or a matrix, and the number of layers. The common types are functional, divisional, matrix and flat structures, and most scaling companies run a hybrid.

• The org chart is the picture of the structure at a point in time. It shows who reports to whom. It does not show who decides, how work flows between teams, or whether the shape matches the business plan.

A company can redraw its org chart without redesigning anything. It can also redesign decision rights, spans and the workforce plan while leaving most of the chart unchanged. The design is what matters; the chart is the record.

How Astravise Services Approaches Organisation Design

Astravise Services treats spans and layers, decision rights and the workforce plan as one diagnostic rather than three separate projects, because each one distorts the others. Narrow spans create extra layers, extra layers push decisions upward, and a headcount budget without a workforce plan quietly recreates both problems within a year.

The work runs as part of the Astravise Strategic CHRO advisory, which covers organisational design and workforce planning that scales with growth:

1. Map the decisions. Build the decision inventory, identify where authority actually sits today, and set owners and thresholds.

2. Measure the structure. Run the spans-and-layers baseline by function, and separate management roles from senior individual contributor roles.

3. Rebuild the workforce plan from the business plan. Translate the next two to three years of the plan into capabilities, structure and a sequenced hiring and redeployment programme.

4. Set the review cadence. Agree the metrics, the owner and the frequency, so the design is reviewed before it drifts rather than after it breaks.

People strategy is business strategy, and a structure is only as good as the decisions it allows people to make. For companies building an India capability centre, the design work connects to the Astravise GCC advisory and management practice, where the question of what sits in India and what stays with the parent is settled at the start. Where organisation design needs a senior owner but not a full-time hire, the Astravise guide to when to engage a fractional CHRO sets out the scope and cost.

^[1][2][3][4]