Grace Design Studios · Module 12 of 12
Debriefing & Continuous Improvement — Companion Reference & Interactive Tools
A project is closed when all five closures are settled — not when the last file is emailed. Work the list; the total shows how much of the close is actually done.
Keep it short, semi-structured, and blameless. These five questions surface patterns without turning into a blame search.
The original scope, budget, schedule, and definition of success.
The real outcome — on fee, on schedule, on quality.
Patterns and root causes — systems, not people.
The moves that worked and should become habit.
One owned action with a date beats a page of notes.
A lesson logged is not a lesson learned. Learning has only happened when a standard, checklist, or habit actually changed. Run every debrief output through one test:
A lesson is “learned” only when it becomes a changed standard, checklist, or behavior within two weeks — while the project is fresh and the will to change still exists. Otherwise it’s a note, not a change.
If the same lesson appears in the log for a second or third time, the log isn’t working — convert it into an enforced gate (a checklist item, a template change) so it cannot recur as easily.
A finished project is an asset. Before details fade, capture three things beyond the fee:
A deliberate thank-you and a plan to stay in contact with the client.
Metrics, photos, and outcomes worth quoting for marketing and pursuits.
Note the next opportunity with this client while the goodwill is highest.
The best business development is a well-closed project. Hand BD a living asset, not a cold file.