Perfection extension: the perfection gate

The project met its original brief three drafts ago. Since then, the edits have become smaller and the release date has moved twice. The newest concern is defensible on its own. Together, the concerns keep changing what “ready” means just as another person is about to see the work.

Perfection extension names that moving standard. It concerns the timing of changes to the completion standard. One observable clue is a usable version that met the earlier agreed standard, followed by new requirements that arise as exposure approaches. The comparison is between requirements that complete the agreed work and additions that keep redefining completion as release approaches.

Imagine a course creator who planned six lessons and a checkout page. Both are complete. Before opening enrollment, she decides the course also needs a resource library, then a redesigned visual system, then interviews with ten more experts. Each addition may make the product better. In this hypothetical example, the question is why the definition of sufficient completion changes only at the moment of release.

The nearest neighbor is exposure resistance. A person showing perfection extension keeps working on the thing itself. A person showing exposure resistance may have a usable version already and keep it unseen while doing other private work. The two can overlap. Looking at whether the deliverable changes, the surrounding work expands, or both makes the sequence easier to describe.

Trait perfectionism is a separate research topic. Frost and colleagues studied its dimensions, while Steel's procrastination review cautions against treating perfectionism as a simple synonym for delay. Perfection extension focuses on the project's changing finish standard. That gives it a specific place within Productive Stasis: the point where a usable result repeatedly becomes another round of work.

By James (Jim) Winner
Research and publication history