A 20-minute retrospective for better scopes
Turn one finished project into sharper assumptions for the next proposal.
The best scope library is built from completed work, not abstract rules. A short retrospective can reveal which assumptions held, where requests expanded and which parts of the quote clients misunderstood.
Compare promise with reality
Put the accepted deliverables beside what the team actually produced. Note added items, repeated revisions and work that was included but never used.
Use neutral language. The goal is to improve the operating model, not assign blame to the client or team.
- Quoted deliverables versus delivered items
- Estimated versus actual effort
- Approval points that moved or failed
Find the missing sentence
Ask what one sentence in the proposal would have prevented the largest ambiguity. It may concern content readiness, stakeholder consolidation, migration volume or browser support.
Write that sentence while the example is fresh. Add it to the appropriate template only if it will help future clients make a clearer decision.
- Assumption to state earlier
- Boundary to make visible
- Question to ask before pricing
Carry forward evidence, not anxiety
Do not react to one difficult project by adding pages of defensive terms. Keep the lesson proportional and specific.
Store the final scope changes and outcomes in Clearcut, then review patterns across several projects. Repeated evidence is a better basis for changing pricing or process than a single stressful week.
- One template improvement
- One pricing adjustment to test
- One workflow habit to repeat
