Organization design

An organization design engagement is appropriate when a strategy has changed materially — through growth, a new market, an acquisition, or a shift in business model — but the structure, decision rights, and role definitions supporting it have not kept pace with that change. It is also warranted when recurring symptoms point to a structural cause rather than an individual one: decisions consistently taking longer than the business situation allows, senior leaders absorbing decisions that belong at a lower level, or roles whose actual complexity has quietly outgrown their formal scope. The engagement is not appropriate as a first response to a single performance problem or a personality conflict, where the cause may be individual rather than structural. Commissioning a design engagement when the underlying issue is actually about capability or leadership fit, rather than structure, tends to produce a redesign that does not resolve the original problem.

Organization design starts from the complexity the strategy requires and builds structure, roles, and decision rights to carry it, while a cost-driven restructuring starts from a headcount or expense target and rearranges the existing structure to meet it, often without examining whether decisions sit at the right level. The two can overlap — a well-executed design can produce cost efficiency as a byproduct — but the sequence and the starting question differ, and starting from cost alone frequently produces a structure that meets the target while leaving the original structural problem intact. Organizations that restructure repeatedly on a cost basis without ever redesigning tend to find themselves solving the same structural friction every budget cycle. A design-led approach treats cost discipline as a constraint to design within, not the objective the design exists to serve.

An organization design engagement produces a defined structure — roles, decision rights, and reporting relationships — matched explicitly to the complexity the strategy requires, along with the rationale connecting each structural choice to that complexity so the design can be explained and defended, not just implemented. It typically includes a clear statement of decision rights at each level, role definitions calibrated to actual complexity rather than convenience, and an implementation path that sequences the transition rather than attempting to change everything simultaneously. The output is meant to function as an operating structure the organization actually runs on, not a slide deck that describes an aspiration. Where the engagement also touches capability, it identifies where current people fit the redesigned roles and where a gap exists that development or hiring must close.

Disruption during a redesign is managed by sequencing the transition deliberately — changing the highest-leverage structural elements first, communicating decision rights clearly as they shift, and giving people affected by role changes enough context to understand why the change is happening, not just that it is. A redesign that changes everything at once, without sequencing, tends to create a period where no one is certain who decides what, which is more disruptive than the redesign itself needs to be. Disruption is also reduced by distinguishing which changes require immediate implementation from which can follow on a longer timeline, rather than treating the entire redesign as equally urgent. The goal is not to eliminate disruption entirely, since genuine structural change inevitably unsettles some existing patterns, but to keep it contained and time-bound rather than open-ended.