The most valuable thirty minutes in any freelance project is the thirty minutes you spend after it ends.
Not on the next project. On understanding what just happened.
Most freelancers do not do this. They close the project, file the invoice, and immediately context-shift to whatever is next. The learning that could make the next project better stays implicit rather than extracting.
The Four-Question Debrief
At the end of every project, answer four questions in writing.
What went well that I should repeat deliberately?
Not every success is repeatable. Some things go well by luck or because of factors outside your control. But some go well because of something you did or decided. Naming it makes it repeatable.
"The two-day buffer I built into the timeline absorbed the unexpected API issue without affecting delivery." That is a decision you can repeat.
What went wrong or unexpectedly?
Be specific. "Communication was difficult" is not useful. "The client's stakeholder review process added two unexpected revision cycles because I had not confirmed who needed to sign off on designs" is useful.
What would I change about how I scoped, priced, or managed this project?
This is the highest-leverage question. The answer usually points to a process change rather than a one-off fix.
What did I learn about this type of client or project?
Some learning is specific to this project. Some of it generalizes. A client type that consistently requires one type of additional work, or a project category that consistently underruns or overruns specific phases.
What to Do With the Debrief
Keep a running document. Review it before starting any project in the same category as one you have debriefed.
After ten debriefs, patterns are visible. The same issues recur. The same things go well. Seeing the pattern is the difference between experience and learning.
The Freelance Command Center includes a project tracker where debrief notes can be linked to client and project records. EUR 17.
Top comments (0)