Lessons Learned

Lessons learned is a structured close-out activity at the end of a professional services engagement in which the delivery team documents what worked, what did not, and what should be done differently on the next similar engagement.

The value is not in the documentation itself but in what happens next: actionable outputs must be incorporated into delivery templates, runbooks, and estimating models, or the exercise produces nothing of lasting value.

Difference from a retrospective

A retrospective is a recurring ceremony within an engagement, typically at sprint or milestone intervals, focused on improving the current delivery. A lessons learned review is a final close-out activity covering the entire engagement, focused on capturing knowledge for future ones. Both are useful; neither replaces the other.

What makes the output actionable

The failure mode is producing observations so generic they apply to any engagement ever run. Actionable entries name the specific change and where it belongs:

• “Discovery is scoped at two weeks but consistently requires four weeks for this client type. Update the estimate model for financial services implementations.”
• “The data migration runbook does not account for legacy system quirks. Add a pre-migration data quality validation step.”
• “The client lacked a named decision-maker until week six. Add client RACI confirmation to the kickoff checklist.”

Each entry has a clear home in a template, runbook, or checklist.

The three-category structure

1. What worked well: processes, tools, and team structures that produced good outcomes. Encode these in engagement templates and reuse them.
2. What did not work: failures, near-misses, and friction points. Factual description without attribution of blame.
3. What to do differently: specific, concrete changes to how the next similar engagement should be run.

Running the session

Keep the session to 90 minutes. Send a structured pre-work survey at least 48 hours before so participants arrive with observations already formed, and the session time is spent on synthesis and prioritization rather than data collection.

Attendees should include the full delivery team and the engagement manager. For engagements where the client had an active project team, inviting the client project sponsor provides a fuller picture of what worked and what did not from both sides.

Closing the loop

Assign each actionable item to a named owner with a deadline to update the relevant template, runbook, or estimate model. The practice lead should verify completion before the engagement is archived. A lessons learned review whose outputs are not tracked to completion produces a document, not a change.

Lessons learned that are encoded into engagement templates and runbooks contribute to a firm’s institutional memory, reducing dependence on individual practitioners and improving the accuracy of future estimates.