Learn the warning signs of structural problems, map roles and decision rights, compare design options and test whether a restructure is necessary.
A company can outgrow its organisational structure long before anyone decides to change the org chart. Decisions become slow, managers inherit too many unrelated responsibilities, and teams disagree about who owns customer or employee problems. These symptoms do not always require a major restructure, but they do deserve diagnosis.
This guide explains organisational design for growing companies: how to recognise a structural problem, distinguish it from a process problem and redesign responsibilities without turning every growth challenge into a new management layer.
Signs the current structure may no longer fit
Common warning signs include repeated escalation of routine decisions to the founder, teams duplicating work, unclear ownership at hand-offs and managers supervising more functions than they can meaningfully support.
Another signal is the same disagreement recurring despite repeated meetings. For example, sales may promise delivery dates while operations lacks authority to confirm capacity. Adding another approval step may not solve the deeper question of decision rights.
Look for patterns over time. A busy month alone does not prove an org chart is wrong; temporary demand, tools or staffing gaps can produce similar symptoms.
Separate structure problems from process problems
Ask whether the organisation knows who is responsible but lacks an efficient way to do the work, or whether responsibility itself is uncertain.
- If everyone knows the owner but requests get lost, improve workflow and hand-off controls.
- If two managers can approve contradictory decisions, clarify authority.
- If a role has incompatible priorities, examine how work is grouped and managed.
- If people are overloaded because demand increased, test capacity before introducing a new hierarchy.
This distinction prevents an expensive restructure from becoming an elaborate way to fix a simple checklist or communication problem.
Map work before drawing boxes
Start with major business outcomes: acquiring customers, delivering services, managing people, controlling finances and maintaining quality. Break each outcome into recurring decisions and responsibilities.
For each responsibility, record who currently does the work, who can approve a decision, which teams provide input and where delays occur. Speak to people who actually perform the tasks, not only those whose titles appear on the organisation chart.
A responsibility map is often more revealing than the chart itself. A well-drawn hierarchy can hide work that nobody owns.
Clarify decision rights with a simple worksheet
Use a short format for recurring decisions:
- Decision: what choice needs to be made?
- Owner: who makes the final call?
- Required input: whose expertise must be consulted?
- Information: what evidence is needed?
- Deadline: when does the decision become costly if delayed?
- Escalation: what happens when owners disagree?
Illustrative example: for an urgent recruitment request, HR may coordinate sourcing, the hiring manager assesses skills, finance confirms budget and an authorised leader approves the offer. If approval ownership is unclear, a candidate may wait even when everyone likes the person.
The exact responsibilities depend on the organisation; the example is not a description of any specific client.
Compare design options against the work
A function-based structure groups people by expertise, such as operations, finance and HR. It can help maintain specialist standards but needs strong cross-functional coordination.
A product, project or customer-focused structure groups work around delivery outcomes. It can improve local decision-making but may duplicate specialist resources. A matrix can share expertise across units while creating ambiguity if decision rights are poorly documented.
Do not select a structure because another company uses it. Compare your options on accountability, customer needs, cost, expertise, management capacity and the amount of coordination required.
Test a proposed design before rolling it out
Take five real situations from recent work, such as an unhappy customer, urgent role request or missed deadline. Ask how each would be handled under the proposed structure.
Who sees the problem first? Who decides? Who has the information? Could two people give contradictory instructions? If these questions remain unclear on paper, they will be harder in practice.
Consider workload and spans of responsibility. A new team leader might solve a genuine coaching gap, but it also creates another reporting relationship. Be explicit about what the role improves.
Communicate changes respectfully
People experience restructures as changes to their work, manager, identity and sometimes job security. Explain the business reason, what is known, what remains undecided and when people will hear more.
Listen for operational risks from employees. Those closest to the work may spot gaps in the proposed design that senior leaders cannot see. Handle employment terms, consultation requirements and personal impacts with qualified local advice.
If your challenge is helping people adopt a new way of working, organisational design must be paired with practical change management, not only a published chart.
Measure whether the new structure works
Before the change, identify a small number of relevant measures: decision turnaround time, escalations, repeated hand-off errors, rework, team workload or customer outcomes.
After the change, review whether owners understand responsibilities and whether decisions are faster and clearer. Avoid declaring success solely because every role has been assigned a box on the chart.
A useful review asks: what improved, what moved somewhere else, and what new friction was created? Make adjustments based on evidence rather than defending the original design at all costs.
Practical design worksheet
Use this short planning sequence:
- State the growth or delivery problem being solved.
- List the decisions and workflows most affected.
- Identify duplicated, overloaded or unowned responsibilities.
- Compare at least two realistic structural options.
- Document decision rights and management capacity.
- Test scenarios using real work examples.
- Plan communication, transition and responsible oversight.
- Schedule a post-change review against baseline measures.
Our guide to outsourced versus in-house HR may also help determine which people functions should remain internal and which specialist capabilities could be supported externally.
Frequently asked questions
When should a company reconsider its org chart?
When repeated accountability, decision-making or coordination problems persist after obvious process and capacity fixes. Growth alone is not sufficient reason; diagnose the actual issue.
Is organisational design the same as restructuring?
Organisational design is the broader work of aligning roles, decisions and reporting relationships with strategy. Restructuring is one possible action arising from that analysis.
Can a small business benefit from organisational design?
Yes. A small company may need only clearer decision ownership, role definitions and escalation paths rather than extra management layers.
Build a structure that supports your strategy
RAST Consultants provides organizational development consulting. Contact us to discuss role clarity, operating structures or change requirements. This article offers general business guidance; obtain appropriate legal advice for changes affecting employment rights.