Some work keeps getting refined long after it has already done its job - a deck on its ninth revision, a report reworded again, a feature endlessly tuned. The problem isn’t that the team doesn’t care; it’s that it cares so much it can’t see the work is already finished. The versions keep improving the artefact - and change the outcome by nothing. This activity finds the point at which the work achieved its purpose, shows what the effort since then has brought, and sets a line to stop at.
Imagine a customer presentation that’s already strong enough to win approval. The team still spends three more days refining the wording, adjusting layouts and polishing slides - but the customer would have made the same decision using Tuesday’s version. This activity finds the ‘done’ point, shows what all the extra effort actually achieved, and decides where to stop next time.
You start by defining the outcome the work was meant to achieve - the outcome, not the artefact. Then you walk through the versions, find the one that first achieved it, and mark it as the Done Line. Then the uncomfortable part: from that version to now, what changed in the outcome? Usually nothing - while the effort (revisions, hours, review rounds) accumulated. Seeing zero outcome gain against all that effort is the recognition. Then you set a fit-for-purpose line to stop at and redirect the saved effort to work that still needs it.
This is not about lowering standards. It’s about seeing the work that was already done - and putting the effort where it still moves the outcome.
Team: one person acts as the facilitator - they run the activity using the Facilitator Guide while everyone else takes part. (Works solo too.)
Solo ✓ Team ✓ · About 20–25 minutes, with a facilitator for teams.
The time required is indicative and will depend on the nature of the work.
The facilitator should read the short facilitation guide first - about 8–10 minutes. It is a downloadable PDF on this page.
Bring a real piece of work with a history of versions or revisions - a deck, report, feature, proposal - that keeps being refined past the point at which it was fit for purpose.
Use it whenever:
You’ve done it well when: someone says ‘we improved the deck, not the decision’ - and the team sets a fit-for-purpose line and moves the saved effort to work that still needs it.
The moment of recognition: the work first achieved its purpose at version five. Versions six to twelve improved the artefact - and changed the outcome by nothing. It was finished on Tuesday.
The hardest part isn’t recognising that work is finished - it’s accepting it. For people who take pride in quality, continuing to polish feels responsible, even when it no longer changes the outcome - so no one calls the stop, and you don’t see the cost. Comparing the outcome before and after the extra work makes that invisible cost impossible to ignore. You can’t defend polish that bought nothing.
You’ll need:
Without version history, the activity won’t work - the reveal depends on finding where the work first achieved its purpose. If you can’t see the earlier versions, reconstruct the stages from memory or review rounds before you start.
Output / Takeaways
You leave with:
Important rules
Planning to facilitate this activity? Access the resources below to get started.