Create a Post-Project Review and Lessons Learned Report

Document what worked, what failed, and what to improve after project completion.
Operations - Project Management - Create a Post-Project Review and Lessons Learned Report

Who it's for

Project Managers, Operations Leads, Founders, Teams, Consultants

Get Ready

Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.

How to use this prompt

1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.

🔒

Unlock the Full Workflow

Get access to this workflow and 1000+ others designed to save hours and get better results with AI.

Workflow Prompt

				
					You are an operations reviewer. Your task is to analyse a completed project and create a practical lessons learned report that can improve future delivery.

### Required Input
- Project Overview: [Describe the completed project, e.g. “Rolled out a new client onboarding checklist across the success team”]
- Original Objective: [State the intended outcome, e.g. “Reduce missed onboarding steps by 50%”]
- Actual Outcomes: [Describe what happened, e.g. “Checklist adopted by 80% of the team, missed steps reduced by 35%”]
- Timeline Performance: [Compare planned vs actual timing, e.g. “Planned 6 weeks, completed in 8 weeks”]
- What Went Well: [List successes with evidence, e.g. “Pilot feedback helped catch unclear instructions before launch”]
- What Did Not Go Well: [List problems, e.g. “Training was scheduled too close to launch”]
- Team or Stakeholder Feedback: [Include comments, patterns, or survey results, e.g. “Managers wanted earlier visibility into rollout changes”]
- Follow-Up Priorities: [List known next steps, e.g. “Improve training process before next rollout”]

### Input Validation
Review all required inputs before generating the output. If outcomes, timeline performance, or feedback are vague, ask specific clarification questions and pause before creating the report.

### Instructions
Compare the original objective with the actual outcome. Be honest about gaps without overstating failure or success.

Identify what worked and explain why it worked, using evidence from the provided results or feedback. Avoid generic praise.

Identify what did not work and trace each issue to a likely cause, such as unclear ownership, weak planning, dependency delays, insufficient testing, or poor communication.

Convert lessons into actionable improvements. Each lesson should help the team change how future projects are planned, communicated, resourced, tested, or delivered.

Group related findings into themes where useful. Highlight patterns that suggest a repeatable operational issue rather than a one-time mistake.

End with specific recommendations that can be reused in future project planning.

### Output
Post-Project Review and Lessons Learned Report

Project Summary
- Original objective
- Actual outcome
- Timeline result

What Worked Well
- Success factor:
- Evidence:
- Why it mattered:

What Did Not Work Well
- Issue:
- Likely cause:
- Impact:

Lessons Learned
- Lesson:
- Future action:
- Owner role:

Recommendations for Future Projects
- Planning improvements
- Communication improvements
- Resource or timeline improvements
- Process changes

Follow-Up Actions
- Action:
- Owner role:
- Suggested timing:
				
			

Optional advanced instructions

				
					Make the review more critical by highlighting systemic issues and recurring process weaknesses.
				
			

Example output

Support Response: Hardware Power Specification Conflict

Status: Technical Resolution
Reference: Document AL-HW-04 / AL-SW-01
Urgency: High


1. Full Response

Hello,

Thank you for flagging the discrepancy regarding the power input requirements for the Aura-Link mesh nodes. We understand there is conflicting information between the Hardware Manual (referencing 24V) and the Software Setup Guide (referencing 12V).

Our Engineering team has confirmed that the correct power specification is 24V.

The 12V reference in the Software Guide is outdated and specifically referred to an early-stage prototype that is no longer in use. Using a 12V power source on the current production hardware will result in intermittent connectivity drops and may prevent the firmware from synchronizing correctly with the satellite backhaul.

Please follow these steps immediately:

  • Verify Power Source: Ensure all installed nodes are connected to a 24V DC power supply.
  • Safety Check: If any nodes were connected to 12V, please power them down, switch the supply to 24V, and perform a hard reset to ensure the firmware re-syncs.
  • Documentation Update: We have pushed a corrected version of the Software Setup Guide (V2.1) to the Aero-Intel Hub. Please discard any local copies of V2.0.

We apologize for the confusion and appreciate your diligence in catching this before the South Warehouse rollout.


2. Short Version (Executive Summary)

The correct power input for all Aura-Link mesh nodes is 24V. The 12V reference in the Software Guide is an error and should be ignored. Please verify your power sources immediately and download the updated manual (V2.1) from the internal hub.

When to reuse this workflow

You may also like...

🔒

Unlock the Full Workflow

Get access to this workflow and 1000+ others designed to save hours and get better results with AI.

No guesswork. Just proven systems.

  • Copy & paste ready prompts
  • Step-by-step instructions
  • Works with ChatGPT instantly

Change Request Handling Process

Create a clear process for evaluating, approving, communicating, and tracking project change requests.

Milestone Review Checklist

Review project milestones with a structured checklist covering progress, quality, risks, decisions, and next actions.

Project Kickoff Plan

Create a structured kickoff plan that aligns goals, roles, deliverables, risks, and next actions before work begins.

Unlock the full library.

Get access to all workflows, across every sector, with structured systems built for better results.

Get Free Access