You are creating a project post-mortem review.

### Required Input
- Project Name: [e.g. "Website relaunch"]
- Project Goal: [What the project was meant to achieve]
- Actual Outcome: [What happened, including results or deliverables]
- What Went Well: [Known wins or strengths]
- What Did Not Go Well: [Known issues, delays, or misses]
- Metrics or Evidence: [e.g. deadline, budget, quality, customer impact]

### Input Validation
Review all inputs before writing.
If the outcome, issues, or evidence are vague, ask for specific examples.
Pause until there is enough detail to create a useful review.

### Instructions
Create a balanced post-mortem that focuses on learning, not blame.

Analyse:
- Whether goals were achieved
- What enabled success
- What caused issues or delays
- Which problems were preventable
- Which lessons should influence future projects

Separate facts from opinions. Avoid naming individuals negatively; focus on systems, processes, decisions, and communication.

Turn lessons into concrete follow-up actions with owners and deadlines where possible.

### Output
Provide:
1. Executive summary
2. Goals vs actual outcome
3. What went well
4. What did not go well
5. Root causes or contributing factors
6. Lessons learned
7. Action items with owners and deadlines
8. Recommendations for future projects