Post-implementation review
Purpose. Evaluate the implementation against its objectives and KPIs, capture
what worked and what did not, and turn that into a change in practice.
Run 30–90 days after go-live, when there is real operating evidence.
Project details
| Field | Detail |
|---|
| Project | |
| Review date | |
| Participants | |
| Period reviewed | |
Objectives — met or not
| # | Objective | Measure | Target | Actual | Verdict |
|---|
| 1 | | | | | Met / Partly / Not met |
| 2 | | | | | |
KPI review
| KPI | Baseline | Target | Actual | Trend | Comment |
|---|
| Deployment frequency | | | | | |
| Lead time for change | | | | | |
| Change failure rate | | | | | |
| MTTR | | | | | |
| Availability | | | | | |
| Workload-specific KPI | | | | | |
What worked
| Item | Why it worked | Worth repeating? |
| --- | --- | --- | --- |
| | | |
What did not
| Item | Why it did not | What should change |
|---|
| | |
Incidents during the period
| Incident | Impact | Detection | Resolution | Root cause |
|---|
| | | | |
Risks that materialised
| Risk | What happened | Was it anticipated? | Mitigation effective? |
|---|
| | | |
Benefits realised
| Benefit | Expected | Actual | Evidence |
|---|
| | | |
Benefits not yet realised
| Benefit | Why not | What is needed | Owner |
|---|
| | | |
Recommendations
| # | Recommendation | Rationale | Owner | Due |
|---|
| 1 | | | | |
Continuous improvement plan
| Area | Action | Owner | Measure of success | Review date |
|---|
| Process | | | | |
| Tooling | | | | |
| Skills | | | | |
| Governance | | | | |
Stakeholder feedback summary
| Stakeholder group | Sentiment | Key themes |
|---|
| Sponsor | | |
| Engineering | | |
| Operations | | |
| Business users | | |
Conclusion
A short statement: did the implementation deliver what it set out to deliver, and
what is the single most important change for the next engagement?