Project Retrospective and Knowledge Retention

The end of a project isn’t the finish line. Distilling the experience of one project into reusable knowledge assets means the next project can avoid the same pitfalls. This case shows how to use LanMate to run a structured retrospective and retain the results in a team knowledge base.

Skills Used

• Built-in skills (installed with LanMate, ready out of the box): Word documents (lanmate-docx)
• Skill Store: Project Retrospective — structured review with the KISS method; PARA Knowledge Organizer — classify and archive lessons learned; Root Cause Analysis — dig into root causes with the “5 Whys”

Pain Points

• Retrospectives become a formality: only successes are summarized, root causes aren’t reviewed
• Experience stays in individuals’ heads: a new project manager steps in and the same pitfalls happen again
• Experience is too generic to be actionable: “improve communication” and “plan ahead” can’t be reused
• Knowledge isn’t archived: the retrospective report is written and then shelved

Recommended Workflow

Prompt Examples

Project Retrospective

Please conduct a structured retrospective for the "XX System Migration Project" based on the project materials I uploaded.
Retrospective dimensions:
1. Goal review: the project's goals and key milestones at kickoff
2. Results assessment: actual completion status, deviations from the plan
3. Root cause analysis: fundamental causes of deviations (dig deep using "5 Whys")
4. Experience summary: organized using the KISS method
   - Keep: what practices were effective and should be maintained
   - Improve: what practices were effective but need improvement
   - Start: new practices to start next time
   - Stop: what practices were ineffective and should be stopped
5. Improvement actions: each experience item corresponds to an actionable improvement action

Requirements:
- Each experience item must be specific — no generic statements like "improve communication"
- Root cause analysis must dig to the root, not stop at surface symptoms
- Improvement actions must include an owner and a completion date
Output a Word retrospective report.

Experience Distillation

Please distill 3-5 reusable experience items from the retrospective results, each containing:
- Experience title: a one-sentence summary
- Applicable scenario: what types of projects it applies to
- Operational suggestions: specific steps (2-3 actionable steps)
- Risk notes: what to watch out for when using this experience
- Source: which specific event in the project this experience comes from

Knowledge Archiving

Please classify the distilled reusable experience using the PARA framework:
- Projects: experience directly usable by similar projects currently underway
- Areas: domain knowledge requiring ongoing attention (e.g., project management methodology)
- Resources: reference materials (templates, checklists, tool recommendations)
- Archives: historical records of completed projects

Tag each experience item (e.g., migration project, risk management, communication and collaboration)
for easy retrieval and reuse later.
Output a knowledge archive list.

Acceptance Criteria

• The retrospective covers goal deviations and root cause analysis (digging deep with 5 Whys)
• All four KISS categories have specific content, not empty talk
• Each experience item includes applicable scenarios and actionable operational suggestions
• Improvement actions have owners and completion dates
• Knowledge archiving has classification tags for easy retrieval

Common Mistakes