Delivery Retrospective Protocol.

Learn from completed engagements deliberately, so each one improves the next.

The retrospective structure

What went well, worth keeping and standardizing. What went wrong, and the root cause, not just the symptom. What should change, in the methodology, the project management, or the client experience.

Combine the closeout lessons with the engagement metrics and satisfaction data.

Retrospective capture

Engagement

Went well / wrong

Root cause

Change proposed

Owning area

Standardization / PM / Client experience

The output is a specific, owned list of changes routed to the guide that owns each one, carried into the improvement loop. A retrospective that ends in observations rather than owned changes has not done its job.

Your answers stay in your browser on this page and are never sent anywhere. Use Save or print to keep your copy.

Back to the guide, or start over.