Org Design Debate
Decide how to structure a team or company as it grows.
A recommended structure with the trade-offs and the first reorganising step.
Reorgs optimise for the diagram and forget the humans inside it, so this council splits the two: the COO and Operations Lead argue how work actually flows versus how the chart claims it does, the Systems Thinker traces the second-order effects — who stops talking to whom — and the People Lead prices the trust cost of moving people. The Strategy Consultant brings the pattern library of structures that worked elsewhere, and the Pragmatist keeps asking whether a smaller change fixes the actual pain.
Help us decide how to structure our team or organisation as we grow. Debate the trade-offs. THE SITUATION: [current size and structure, where it is straining, where you are heading] THE OPTIONS: [the structures you are considering — functional, pods, divisions, etc.] THE PAIN: [what is breaking now — slow decisions, unclear ownership, silos] Debate: 1. What the current structure optimises for, and whether that still matches the goal. 2. The trade-offs of each option — speed vs control, focus vs duplication, autonomy vs alignment. 3. Where decisions get made and how ownership and accountability flow. 4. The communication and coordination cost of each shape. 5. The human cost of a reorg, and how to do it with the least damage. 6. The structure that fits where we are going, not just where we are. FINAL SYNTHESIS: - A recommended structure with the top reasons. - The main trade-off we are accepting, named honestly. - The first reorganising move and how to communicate it.
An illustrative excerpt for a hypothetical brief of this type: A 40-person startup organised by function (engineering, design, sales) finds every feature now needs four managers to agree, and is debating a move to cross-functional pods. Every real run is generated fresh from your specifics, debated across rounds, and audited before the verdict.
Name the real bottleneck before drawing pods: four managers agreeing is a decision-rights problem, not necessarily a structure problem. If ownership of each feature had one named decider today, would the pain persist? If not, you are about to run a company-wide reorg to fix a RACI chart.
Partially disagree — the functional structure is also creating queues: design waits on engineering estimates, sales commitments wait on both. Pods collapse those queues for product work. But pods duplicate skills, and at 40 people some functions have three specialists total; split them across four pods and each pod gets three-quarters of a person.
Whatever is decided, the sequencing is the risk: announce a full reorg and every one of the 40 spends a month wondering who their manager is. The alternative — pilot one pod around the most painful product area, leave the rest functional — gets the evidence without the anxiety. Reorgs are trust withdrawals; make the smallest one that works.
Converging: one pilot pod with a named single decider, staffed fully, for one quarter — success measured by cycle time on that product area versus the functional baseline. If the queue problem dissolves, expand pod by pod. If it does not, you learned the problem was decision rights all along, for one-tenth the disruption.
Prefer drop-and-go? Use the Org Design Debate tool — team pre-seated, included with Plus.
What should I describe about my current organisation?
Current size and structure, where work queues or decisions stall (with an example), what is driving the change, and the options you are considering. The example matters most — the council reasons from the specific pain, and “features need four approvals” leads somewhere different from “nobody owns quality”.
Will it recommend a textbook structure — pods, matrix, functional?
It recommends a structure, but the more valuable output is usually the trade-off named honestly: every structure buys speed somewhere by paying duplication or alignment cost somewhere else. The synthesis states what you are choosing to be worse at, which is the part reorg announcements always omit.
How do I handle the people side of announcing the change?
The final synthesis includes the first reorganising move and how to communicate it — sequencing, who hears it first, and what stays stable. In most debates the People Lead successfully argues for the smallest viable change, because trust spends faster than org charts redraw.