org-design

Org design

Structure determines what is easy and what requires heroics. Most persistent coordination problems are structural and cannot be fixed by asking people to communicate better.

Design from the work

Start with the work that must happen and its natural boundaries — where handoffs are expensive, and where they are cheap. Draw team lines at the cheap handoffs.

Then check: can each team deliver something meaningful without waiting on another? A team that cannot ship without three dependencies is not a team, it is a queue.

Design the org for the work, not around the people currently in it. Then reconcile deliberately, noting where you have compromised and why. Structures built around individuals fail when those individuals leave, and everyone can see they were built that way.

Spans and layers

Wide spans push decisions down and starve people of attention. Narrow spans give attention and breed layers, which add latency to every decision.

Roughly: five to nine reports for a manager whose people need coaching; more where the work is consistent and the people are experienced. Every layer must add decision value — a layer that only passes information along should be removed, and it is usually obvious which one it is.

Ownership

Every outcome has exactly one owner. Where two teams share an outcome, neither owns it, and it fails in the gap. Where an owner lacks the authority to deliver, the accountability is fictional.

Write down the boundaries — what each team decides alone, what needs consultation, what needs approval. Ambiguity between senior teams is expensive and does not resolve itself.

Workforce planning

Plan roles against the work and the plan, not against last year plus a percentage. For each proposed role: what does not happen without it, what does it take off someone else, and what is the ramp before it contributes?

Sequence hires so each has someone to learn from. Hiring three juniors before the senior who leads them is a common and expensive ordering error.