Organizational Design

What org design covers

People often equate org design with drawing boxes on an org chart. The chart is the visible result, but a sound design answers several questions first:

• Structure: how work is grouped. By function, by product, by customer segment, by geography, or a mix.
• Spans and layers: how many people each manager leads and how many levels sit between the frontline and the CEO. See span of control.
• Roles and decision rights: who owns which decisions, and who must be consulted. Ambiguity here causes more friction than the structure itself.
• Processes and handoffs: how work flows across teams, for example from recruiting to onboarding to the operations floor.
• Jobs and levels: what roles exist and how they are leveled, usually through a job architecture.

Common organizational structures

• Functional: teams grouped by expertise (Finance, HR, Operations). Efficient and good for deep skills, slower at cross-team work.
• Divisional: teams grouped by product, customer or region, each with its own functions. Faster for each division, but duplicates roles.
• Matrix: people report to both a functional and a business or project leader. Useful when both expertise and client focus matter; demands clear decision rights or it stalls.
• Flat or team-based: few layers, wide spans, more autonomy. Works for small or highly skilled teams; strains when a manager has 40 direct reports needing coaching.
• Hybrid: most large employers. For example, a shared services HR function serving divisional business units.

There is no best structure. The right one depends on what the strategy needs the organization to be good at.

A practical design process

1. Start from strategy. Write down the three or four capabilities the organization must excel at, such as faster client onboarding or lower cost per contact.
2. Diagnose the current state. Map spans and layers, decision bottlenecks, duplicated work and pain points. Interview frontline managers, not just executives.
3. Set design criteria. For example: no more than six layers, minimum span of eight for frontline supervisors, single owner for each client.
4. Develop and test two or three options against the criteria. Walk real scenarios through each option.
5. Design detail: roles, decision rights, headcount by team, job levels and cost.
6. Plan the transition: people selection, communication, legal steps for any role eliminations, and a timeline.
7. Review after six to twelve months and adjust.

A worked example

A staffing firm with 14 branches lets each branch manager run sales, recruiting and payroll locally. Clients with sites in several states deal with several branches and complain about inconsistent fill rates and invoices.

The redesign keeps branches for local recruiting, creates a national accounts team that owns each multi-site client, and moves payroll into one shared service. Branch managers lose some decision rights over large accounts, which needs careful handling. Spans for recruiting supervisors are set at 8 to 10 recruiters. Twelve months later, the firm has one point of contact per national client and payroll errors fall because one team owns the process end to end.

How org design connects to workforce planning

Org design decides the shape of the organization; workforce planning decides how many people with which skills are needed in that shape, and when. Run them together. A redesign that adds a national accounts team creates hiring needs, internal moves and possibly role eliminations, and the recruiting plan needs to be ready before the announcement, not after.

Mistakes that make reorganizations fail

• Designing around people. Building boxes to fit current leaders locks the current problems in place. Design the roles first, then select people.
• Changing structure but not decision rights. If the same approvals still go through the same three executives, nothing improves.
• Reorganizing too often. Each reorganization costs months of productivity. If the answer to every problem is a new chart, the problem is probably elsewhere.
• Ignoring the legal side. Role eliminations can trigger WARN Act notice and adverse impact review. Rules vary by state and country.