Done-Better-Than-Perfect Improvement Loop
Ship workable output, capture lessons, and improve the next cycle.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 99%
The Done-Better-Than-Perfect Improvement Loop separates the quality floor required now from the improvements that can wait for the next cycle. Define what must work, release once that floor is met, and resist delaying for polish that does not change the outcome. Then turn the completed work into learning: recap what happened, record the operational lessons in a living SOP, and use those changes on the next launch, event, or shoot. Pia Mance explicitly warned that 'done' is not the endpoint; Heaven Mayhem pairs fast execution with recaps and updated procedures. The mechanism therefore avoids two opposite failures: perfectionism that prevents feedback and careless speed that never improves. It is suited to reversible, repeatable work, not tasks where an imperfect release could cause serious harm.
Origin
Extracted from The Foundr Podcast. Pia Mance described using 'done is better than perfect' to release work quickly, then requiring recaps and continuously updated SOPs after launches, events, and major shoots.
Core principles
- 01A useful release creates more learning than an unfinished ideal.
- 02Embarrassment is not evidence that a release failed.
- 03Speed without reflection merely repeats mistakes.
- 04Every cycle should leave the next cycle easier or better.
How to run it
- 1
Set the quality floor
Write down what must be true for the output to be useful and safe. Separate those requirements from optional polish.
Pro tip Make the floor observable so the team knows when to stop polishing.
Watch out Never classify safety, compliance, or truthfulness as optional polish.
- 2
Release the workable version
Complete the essential work and put it into use. Accept that early creative output may look less refined in hindsight.
Pro tip Choose a firm release point before perfectionism takes over.
Watch out Fast does not mean knowingly broken.
- 3
Capture the recap
Soon after completion, record what worked, what failed, and what caused avoidable friction. Base the recap on observed events rather than impressions alone.
Pro tip Run the recap while details and responsibilities are still clear.
Watch out A vague retrospective will not change the next cycle.
- 4
Update the operating method
Translate each useful lesson into a concrete change in the relevant SOP. Keep the procedure live rather than archiving the recap without action.
Pro tip Assign each lesson to the exact step it should change.
Watch out Do not collect lessons that nobody applies.
- 5
Raise the next cycle
Use the revised procedure on the next comparable task and evaluate whether it improved the result. Repeat the loop rather than waiting for a perfect system.
Pro tip Judge progress across cycles, not against an imaginary perfect first attempt.
In the wild
Heaven Mayhem releases launches, events, and shoots without waiting for every detail to become perfect. After each one, the team creates a recap and updates a running SOP so the following version can move closer to the desired standard.
→ The brand preserves speed while accumulating operational improvements.
Common mistakes
Stopping at done
Shipping without a recap turns the motto into an excuse for repeated mediocrity. The framework requires learning and procedural change.
Polishing before feedback
Saving for specialist production or refining indefinitely can delay the evidence needed to improve the work intelligently.
Is it for you?
Best for
It is best for repeatable launches, events, content, and creative work where feedback arrives only after release.
Not ideal for
It is not ideal for safety-critical, legal, or irreversible work where defects must be resolved before release.
From the transcript
“Just get it done, get it out there, and then you have next time to improve.”
“Everyone is required to do a recap and like an SOP and keep this SOP running.”
“Done is better than perfect, but like don't leave it at done.”
From the episode
595: She Turned Handmade Jewellery Into $10M Brand
Pia Mance