When planning becomes the project

The plan acquires its own life. There is a new board for it, a more complete list, a better taxonomy, a calendar, and a folder of examples. None of those things is foolish. The original deliverable, though, has not moved toward a recipient.

Productive Stasis gives a name to the painful gap between a growing plan and an outside result that has yet to happen. A founder may know that the next meaningful event is a conversation with a buyer, yet spend another month polishing a feature map. A writer may know an editor needs to read the manuscript, yet keep reorganizing a submission tracker. Both examples are hypothetical.

The work has an immediate payoff. A system can be improved in private and judged by the person building it. A customer, editor, or collaborator can surprise them. The proposed framework calls one version of this infrastructure substitution. Another version, research extension, keeps adding information after the decision it was meant to inform has become sufficiently clear. Winner develops both terms in his research paper.

Existing research helps explain why private preparation can be so appealing. Sirois and Pychyl discuss procrastination through short-term mood regulation. Pan and Etkin found that perceiving procrastination as productive can lengthen delay. The papers describe adjacent experiences. Winner's term centers the project that has absorbed so much planning and still has no audience.

A plan can become a place where the project lives for months. Imagine instead the conversation with a buyer, the manuscript with an editor, or the course available to the people who asked for it. The plan finally has a world to support.

Research paper. James (Jim) Winner (2026). Productive Stasis: Naming a Failure of Conversion in Capable Goal Pursuit. DOI: 10.5281/zenodo.23069801.