When a build goes sideways, we blame the people. Usually the real constraint is the system they're working inside.
When a build goes sideways, the first instinct in the room is to look at the people. The PM and the engineer are pointing at each other, sizing was off, the PRD was thin, somebody dropped a ball. It’s a satisfying story because it has characters in it. It’s also, most of the time, wrong.
I’ve been pulling together examples for an upcoming leadership offsite, and the pattern is hard to miss. A prototype my team can build in a day still takes months to get into production. A feature gets built so self-contained that the next team can’t reuse a line of it without rebuilding from scratch. Quick wins with obvious value sit in an icebox because the planning model has no protected room for anything that isn’t a top priority or a loud escalation. None of those are interpersonal problems. They’re the shape of the system the people are working inside.
The new framing I’m bringing to the offsite is that our process, the way we plan and size and ship, was built for a slower kind of work and can’t keep up with the speed the team now moves at. When design can produce 5x the exploration it used to, something has to give.
When design can produce 5x the exploration, the bottleneck doesn’t disappear. It relocates to wherever the system is most rigid.
Right now that’s the path from a working prototype to a shipped thing, and no amount of goodwill between two people will widen it. This matters for how you spend your leadership energy. If you treat structural drag as a people problem, you end up coaching individuals to collaborate better while the actual constraint sits untouched, and everyone gets a little more frustrated for no reason. The more useful move is to name the structure out loud, in front of the people who can change it, and take the blame off the humans who are mostly doing their jobs well inside a process that’s working against them.
The teachable part
Before you coach people to collaborate better, check whether the constraint is actually the system they’re working inside. Speed relocates the bottleneck, it doesn’t remove it.