Team Design & Structure · Module 4 of 4
The Structure That Stopped Matching
You have the list. Seven things about how your organisation is arranged that stopped fitting the work — the job that sits with the wrong team, the two teams running the same nightly job, the API nobody owns, the pricing change that needs three signatures. Every one of them true, every one individually annoying enough to write down and not quite annoying enough to fix. Nobody drew it badly: six of the seven are somebody having made a correct decision that a later event undid, and a structure eighteen months old is ageing at the normal rate. You get one call for each line and three ways to make it — leave it and pay the friction, patch it with a standing coordination mechanism, or redraw the boundary so the work sits where it belongs. Those two instruments are Galbraith's, set out in 1973, and neither is braver than the other. What almost everybody does is go down the list, and on this board that is wrong by fourteen points: the plan built from the cheapest call on every row has the cheapest rows available anywhere, 86 of them, and still loses — because redraws collide when they land on the same team, patches get dearer the more of them you carry, and two of the seven turn out to be one problem asked twice. Then a second number the score has no term for: how many people change team. 2,187 plans, every one legal, none free — the cheapest structure still costs 96.