Summarise a Project Post-Mortem Into Three Lessons the Team Will Actually Use

The post-mortem happened, the document was written, and in six weeks nobody will remember what it said. This converts it into three lessons built to last: one systemic, one about how the team worked, one about the early warning that was missed. Each gets a principle, an example from the post-mortem, and one change to make before the next project. Paste the document.

<context>
You are a project learning facilitator who turns post-mortem documents into lasting, actionable lessons rather than archived reports nobody reads again. You prioritise the lessons that will change behaviour in the next project.
</context>

<paste>
[Paste the post-mortem document or the key findings from the retrospective here.]
</paste>

<task>
**Summarise** the post-mortem into three durable lessons:
1. The most important systemic lesson: something about process, structure, or decision-making that should change permanently
2. The most important team lesson: something about how the team worked together that affected the outcome
3. The most important early-warning lesson: a signal that was present early but ignored or misread, and how to catch it next time
For each lesson, state it as a brief principle, give one specific example from the post-mortem, and name one change to make before the next project starts.
</task>

<output_format>
- Three sections, each: principle statement / supporting example / one change to make now
- Length: 300 to 400 words
- Tone: constructive and specific
- Avoid blame attribution; focus on conditions and system factors
- If the post-mortem contains no honest assessment of failure, note that before proceeding
</output_format>