When the Bottleneck Is Structural: fix the system, not the person.

How can you tell a process problem from a people problem?

Chapter 11 describes structural bottlenecks: a process that is too slow, an inadequate tool, incomplete or delayed information, insufficient resources, a poorly designed sequence, decision authority that is unclear or too centralised. Unlike human constraints they are impersonal, built into how the organisation works regardless of who works in it, and fixing them usually means changing the system. The Act stage redesigns the structure: the process is redesigned, the tool replaced, information systems improved, resources reallocated, authority clarified.

The chapter’s central diagnostic warning is that what looks like a human constraint is often structural. Someone appears to perform poorly, but the process around them is so inefficient that no one could perform well in it. The reverse also happens: a new tool speeds up the process, but a team member still cannot use it and needs training. Most complex constraints, the book says, have both human and structural elements, and mature execution addresses both.

Structural fixes have trade-offs. They scale, because a faster process helps everyone who runs it, and they are often easier to sustain, since the system does not regress as long as the structure is maintained. But they may need capital or significant redesign effort, they meet resistance from people used to the old way, and output can dip while a new process or tool is learned. The doctrine values them because they are reproducible across cycles and across the organisation.

The runtime’s Structural Constraint Chamber is built on this chapter. Chapter 10 covers the human side of the same diagnosis.