Every doctrine must name its failure modes.
Vinay's Execution Doctrine is powerful when applied correctly. But it can fail in specific, identifiable ways. An executor who understands these failure modes can recognize them and correct course.
The first failure mode is misidentification of the constraint.
If the executor identifies the wrong constraint and invests improvement effort there, output will not improve. The system will expend energy and resources on improving something that is not actually limiting performance. Meanwhile, the true constraint remains unaddressed. The executor who does this once and sees no improvement should reconsider the constraint diagnosis. The executor who does this repeatedly is applying the doctrine incorrectly.
The second failure mode is diffusion of effort.
If the executor identifies the constraint correctly but then also tries to improve multiple other elements simultaneously, the improvement effort is diluted. Neither the true constraint nor the secondary improvements receive sufficient focus. The result is that nothing substantially improves. The discipline of one constraint exists specifically to prevent this failure mode.
The third failure mode is improvement without implementation.
The executor understands the constraint. They design a good solution in the Act stage. But the solution is never actually implemented in the next cycle. Perhaps leadership changes and the improvement is deprioritized. Perhaps the team resists the change and it is not enforced. Perhaps it is unclear who is responsible for implementation. The improvement exists in theory but not in practice. This is particularly common when improvements are organizational rather than technical.
The fourth failure mode is measurement failure.
The executor runs cycles but does not clearly measure output. They cannot tell whether the system is actually improving. They cannot identify whether a constraint has been successfully addressed. They cannot distinguish between improvement and mere activity. Without measurement, the doctrine becomes a set of nice ideas without observable results.
The fifth failure mode is impatience.
The executor expects dramatic improvement from every cycle. When improvement is modest, they abandon the approach or shift focus. But the doctrine produces compound improvement over many cycles. The executor who expects results in two or three cycles may quit before results become visible. The executor who commits to the process over ten, twenty, or thirty cycles sees remarkable results.
The sixth failure mode is addressing human constraints without addressing structural ones.
If a constraint is structural, addressing it by changing people will not produce lasting improvement. A new person enters the same structural constraint and encounters the same limitation. The doctrine requires accurate diagnosis of whether a constraint is human or structural.
The seventh failure mode is addressing structural constraints without addressing human ones.
If a constraint is human, a new tool or process will not solve it. A person who lacks skill remains unskilled even with better tools. A person who lacks discipline remains undisciplined even with better processes. Both dimensions must be addressed accurately.
The eighth failure mode is inadequate follow-through in the Act stage.
The constraint is identified. The solution is designed. But the Act stage does not fully resource the solution or commit to implementing it. The Plan for the next cycle is not actually different. The system runs the same way. The constraint remains unaddressed. This is perhaps the most common failure mode. Improving is hard, and it is easy to plan improvements that are not actually implemented.
The ninth failure mode is mistaking activity for progress.
The team is busy. Work is happening. Effort is high. But output is not increasing. This is activity without progress. The doctrine is ruthless about this distinction. It cares only about whether the system actually expands its capacity, not whether people are working hard.
The tenth failure mode is local optimization without system thinking.
An executor improves one part of a system without considering impacts on other parts. A manufacturing plant reduces cost per unit but degrades quality, which damages sales. A software team accelerates development but accumulates technical debt, which slows future development. Improving one element while degrading the whole system is not expansion of capacity. It is optimization of parts at the expense of the system.
Understanding these failure modes is what allows an executor to apply the doctrine with increasing sophistication. An executor who operates the doctrine without awareness of failure modes will eventually hit one of them. An executor who understands the failure modes can recognize them quickly and adjust course.
The doctrine exists to govern real cycles, not to decorate discussion.
Text from the manuscript published at /library/execution-doctrine/full-text.txt. © 2026 Vinay. All rights reserved.
