In this guide
Design how the work can happen
  1. 01Find the recurring decision
  2. 02Compare arrangements
  3. 03Connect roles and conditions
  4. 04Rehearse end to end
A practical inquiry across structure, coordination, capability and incentives. A reporting-line change alone does not establish improvement.

Organization design connects the work an organization must accomplish with its roles, decisions, coordination, capabilities and incentives. An organization chart shows reporting relationships, but it cannot by itself explain who resolves an exception or how two departments complete a shared task.

Start with a recurring decision or end-to-end service that the current arrangement handles poorly. Investigate it with the people involved before choosing a new structure. This extends change contracting from agreeing the assignment to designing an operating arrangement that can carry it out.

Use a framework to widen the inquiry

Jay Galbraith’s Star Model brings together strategy, structure, processes, rewards and people. Its practical contribution is a broader set of design questions. Changing reporting lines while leaving incompatible measures, missing skills and broken coordination untouched can leave the central problem unresolved.

The framework does not prove that every difficulty is a design problem or identify the right structure automatically. A temporary capacity shortage, a faulty system or an unclear instruction may need a more focused response. Ask what evidence makes an organizational change a reasonable hypothesis.

Distinguish the formal design from actual practice. Staff may use informal contacts to resolve cases that the official route cannot handle. Those contacts can reveal essential coordination work, but relying indefinitely on particular helpful people leaves a fragile dependency. Culture analysis helps investigate the routines behind the stated arrangement.

Start with the decisions the organization must make

Consider a hypothetical distributor handling damaged parcels. Customer service can promise a replacement, the warehouse can inspect returns and finance can authorize certain adjustments. When a case falls between those decisions, the customer repeats the same account while teams wait for each other.

Two adjacent work areas handle damaged parcels with separate piles of paperwork.
Figure 1. Start with the decisions the organization must make.Illustration credits

Map a recent type of case from the first report to a completed resolution. Separate what each team knows, what it may decide and what it must obtain elsewhere. Ask who owns the result experienced by the customer, including exceptions rather than only the routine route.

The GOV.UK Service Standard recommends solving a whole problem across team boundaries. Applied by analogy here, it suggests looking beyond each department’s closed ticket. It does not mean that all responsibility must move into one large team or that a private distributor must adopt a public-service operating model.

Write the design problem in observable terms: for which cases is the next decision unavailable, which information is missing and what work waits as a result? “We need a matrix structure” is already a proposed solution. “Nobody can resolve a disputed damage claim within the current authority boundaries” is a problem to investigate.

Compare arrangements against explicit criteria

Agree the outcomes and trade-offs before comparing structures. The distributor may value clear customer ownership, consistent decisions, specialist expertise and manageable workload. These can conflict. Concentrating authority may simplify a case while overloading a small group or distancing expertise from daily work.

Develop more than one operating option. The existing teams might keep their reporting lines but create a shared exception role. A cross-functional service team might own a defined class of cases. A simpler change in decision authority might solve the problem without moving people at all.

Use a comparison table that keeps assumptions visible:

Design questionWhat to examine
PurposeWhich user or organizational outcome is the arrangement for?
Decision authorityWho may decide which exceptions?
CoordinationHow do information and commitments cross boundaries?
CapabilityWhich skills and access must be available?
Measures and rewardsWhat behaviour does the arrangement encourage?
CapacityWhat happens when demand exceeds the planned coverage?

The table is an original inquiry aid, not an organizational maturity scale. Use a weighted decision matrix only if a transparent comparison genuinely helps; the scoring should not hide unresolved authority or a non-negotiable constraint.

Design the work before moving the boxes

GOV.UK’s multidisciplinary team guidance emphasizes having relevant skills and appropriate access to decisions. For the fictional distributor, a shared team would need more than people with different job titles. Its members would need access to parcel information, an agreed authority boundary and a practical escalation route.

Define the ordinary and exceptional routes. A clear receiving role is important when a case crosses a boundary. Record what information is needed, how acceptance is confirmed and who remains responsible while clarification is underway. Interface management provides a more detailed way to design that handoff.

Check the consequences for other work. Moving an experienced warehouse colleague into a shared service team may remove expertise from inspection. A coordination improvement in one place can create a new queue elsewhere. Include those dependencies in the comparison instead of treating them as implementation details for later.

Test one end-to-end arrangement

Before a full reorganization, rehearse the proposed route using representative case types and the people who would operate it. For the fictional distributor, walk through an ordinary damaged parcel, a missing photograph and a disputed account. These are proposed test scenarios, not reported incidents.

A warehouse worker and service colleague examine a parcel together at a shared exception station.
Figure 2. Test one end-to-end arrangement.Illustration credits

Ask each participant what they know and can decide at every step. When someone says they would ask a manager, name the manager and check whether the authority and availability exist. A rehearsal should expose these dependencies rather than smooth them over.

If a bounded operational trial is appropriate, define its scope, support and review. Track the customer outcome together with waiting, rework and workload across teams. The service blueprint guide can connect the visible experience to the supporting work.

Keep employment-related decisions and commitments within the organization’s proper processes. A workshop about coordination is not itself an agreement to change someone’s job. Make the scope of participation clear and involve the people authorized to address the consequences of a proposed redesign.

Make disagreement usable

Edmondson’s research on psychological safety and learning behaviour offers a reason to examine whether people can raise concerns without undue interpersonal risk. It is not evidence that a particular organizational design will succeed or that all disagreement reflects low safety.

Ask people what the proposed arrangement makes harder for them, which dependencies it assumes and what would fail on a busy day. A concern from the current structure’s defenders may reveal real operating knowledge. Conversely, a proposal from a confident sponsor still needs the same evidence and trade-off discussion as other options.

Use stakeholder mapping to find affected groups, including people whose influence is low but whose daily work changes substantially. Give them a meaningful route to correct the design assumptions. State which decisions remain with the sponsor and explain how feedback was used.

Evidence limits and a useful design brief

This guide combines a model-owner framework, public-service guidance and research about team learning. It does not establish that a matrix, shared-service centre or cross-functional team is universally superior. The distributor is hypothetical, and its proposed arrangements have not been tested.

Prepare a design brief with one observed problem, the decisions it involves, the people affected, alternative arrangements and a bounded way to examine them. Use change readiness to check whether authority, capacity and support exist for the next step. Approve a larger redesign only when its operating consequences are sufficiently understood for that commitment.

Sources: