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. Each addition has a purpose. The original deliverable, though, has not moved toward a recipient.

Productive Stasis treats this as a question of proportion and timing. Planning is often necessary. The concern begins when planning keeps expanding after the next external event is already clear. 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 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. Both describe what fills the time between deciding on an outside action and carrying it out.

Related research examines why useful activity and delay can coexist. Sirois and Pychyl discuss procrastination through short-term mood regulation. Pan and Etkin found that perceiving procrastination as productive can lengthen delay. These accounts direct attention to what the planning accomplishes in the immediate moment and what happens to the intended outcome over time.

The sharp question is what the planning is for. If it is serving a decision that still needs evidence, it may be doing its job. If the plan has become the safest place for a project to live, the visible activity may conceal a stalled external outcome.

By James (Jim) Winner
Research and publication history