Reorganize a team when a recurring problem can be traced to how people are grouped, who controls resources, or who has authority to decide. Before approving a new org chart, ask the sponsor to walk through one recent case. Under the proposed structure, who would make a different decision, and when would that change the outcome for the customer?
Suppose Sales and Operations want to merge because customers wait ten days for a pricing exception. If the request crosses between teams on the first morning and then sits in a director’s approval queue, the merger proposal has a question to answer. What happens to that queue the day after the move?

When should you reorganize a team?
A reorganization changes where work, people, or authority sit. It is worth considering when a boundary repeatedly prevents someone from delivering an outcome they own. For example, a service leader may be accountable for installation dates while two regional managers independently allocate the same installers. Everyone can do their assigned job well and still promise incompatible dates.
Start with the narrowest explanation that fits the evidence. A manager who already has approval authority but lacks reliable pricing information faces a different problem from a manager who has the information and must still escalate every decision. Moving either person into another department helps only if the move changes the condition causing the delay.
| What you observe | What to investigate first |
|---|---|
| Two teams commit the same scarce capacity. | Who can reconcile competing promises before customers receive dates? |
| Completed requests wait with one approver. | Which decisions can be delegated, and within what limits? |
| Work returns repeatedly for missing information. | What does the receiving team need at the handoff? |
The CIPD guide to organisation design places structure in the context of strategy and how work gets done. The five questions below are a practical way to apply that perspective to a proposed team move. They draw on System Shaping by asking which conditions repeatedly produce the outcome.
Five questions to ask before changing the org chart
1. Which recurring problem should the reorganization solve?
Choose an outcome someone experiences: a customer waits for a quote, a technician arrives without the right equipment, or two managers promise different delivery dates. Ask the people involved for recent cases and one case that went well. The exception can reveal what the org chart alone cannot explain. Did the successful case have a clear owner, spare capacity, or an approver who happened to be available?
2. Where does the current structure produce the problem?
Reconstruct the order of events. Record when the request arrived, when it was ready for a decision, who could decide, and when the customer heard back. Ask the person who actually handled each step to check the timeline. The handoff people complain about may be where they first see the delay rather than where the delay begins.
3. What would happen to the same case under the proposed structure?
Replay the case with the proposed responsibilities. Stop at the first point where someone can act differently. Write down the role, the decision, and the authority or resource the role gains. “One shared director” is incomplete. “The service owner can reserve an installation slot before Sales confirms the date” is specific enough to test.
4. What smaller change could test that explanation?
Pick one request type, team, or customer segment. Temporarily delegate the decision or give one person control of a defined pool of capacity. Agree on exceptions that still require escalation. If the pilot only works because a senior sponsor personally chases each case, record that dependency before proposing a permanent design.
5. What result would justify the disruption?
Set the decision criteria before the pilot. Agree on the improvement customers should experience, how many comparable cases the review needs, and which side effects would be unacceptable. Include transition costs: time to transfer customer relationships, teach unfamiliar work, and cover vacancies. Name the person who can approve the move, extend the test, or close the proposal.
Worked example: Should Sales and Operations merge?
In this illustrative case, Sales and Operations leaders review three recent pricing exceptions. Customers waited about ten days. In each case Sales handed the request to Operations promptly. The longest interval began after Operations assembled the information and ended when the pricing director approved the exception. Both teams would still need that signature after their proposed merger.

Decision: pilot delegated authority for routine exceptions. The pricing director defines an eligible discount range and names an Operations lead who can approve requests within it. Unusual contract terms stay with the director. Sales records when each eligible request arrives, and Operations records when the customer receives a binding answer.
At the review, compare similar requests before and during the pilot. Examine elapsed time, pricing errors, reopened cases, and the oldest request still waiting. If routine cases move faster within the agreed safeguards, the teams have evidence for keeping delegated approval. If approval is faster but customers still wait ten days, trace the time after sign-off before approving a merger. Three cases justified a test; they did not establish the answer for every customer.
When a reorganization is justified
Consider a different team reviewing failed installation promises. Sales can commit customer dates. Operations can reassign installers across regions. Neither owns the combined schedule. A shared planning meeting makes conflicts visible, yet whichever manager speaks to the customer last can still make a promise the other cannot honor.
Here a structural change has a clear mechanism. A single installation service owner could control the pool of installers and the authority to confirm dates. Regional managers could retain responsibility for local delivery and escalate exceptions to that owner. Replaying a missed installation now produces a different event: the owner checks a real slot before anyone promises it.
The case for proceeding depends on whether the new owner can actually resolve competing priorities and whether local teams can still respond to emergencies. Review both with the people inheriting the work. If the disagreement is mainly about departmental incentives, see why reorganizations can leave organizational silos intact.
Reorganization decision worksheet

Completed example: pricing exceptions
Proposal: Merge Sales and Operations. Finding: Three customer cases waited longest for pricing approval. Decision replay: The pricing director would still approve each exception at the same point. The proposed merger removes no approval step.
Decision: Pilot delegated approval within the agreed discount range. Owner: Pricing director. Review: Compare eligible cases after four weeks. If too few comparable requests arrive, extend the observation period. Reopen the merger question if cases still stall at a team boundary after the approval delay is removed.
What to record before approval
Leave the meeting with one sentence everyone can check later: “We authorized this change because it gives this role the authority to make this decision, and we expect customers to experience this improvement.” Attach the baseline, transition cost, accountable owner, and review date. Give staff a clear route for reporting consequences the proposal missed.
If the decision is to proceed, capture the baseline while the old structure is still in place. Use the reorganization success scorecard and 30-, 60-, and 90-day review guide to follow the original cases through the transition. The first useful test of the new chart is whether the next customer gets a better decision.