Infrastructure substitution: the system builder

The workspace is better than it was a month ago. The database is cleaner, the templates are easier to use, and a new dashboard shows what remains. The offer, paper, or application still hasn't reached the person waiting for it.

Infrastructure substitution is Jim Winner's proposed name for work on the machinery around a project that grows while the project's intended result stays private. The machinery matters. A working checkout and a clean client handoff can make a release possible. But a person can spend months building a beautiful system and still feel the same dread when someone asks, "Is it out?"

A coach prepares a group program. She rebuilds her client tracker, tries new booking tools, and improves her handoff notes. Her week is full and her operations are better. The invitation to join the program remains unsent. By the time she opens the tracker again, its neat columns can feel like evidence against her rather than proof of progress.

Perfection extension keeps attention on improving the deliverable itself. Infrastructure substitution describes the growing apparatus around it. Westgate and colleagues studied productive procrastination, where a worthwhile task can replace another intended task. Winner's Productive Stasis framework brings that familiar experience into the story of a project that has yet to meet its audience.

The program is available. People have joined, and the system you built now serves them. Your work has a life outside your workspace. The free It's Basically Done profile starts with the project that needs that change.

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