Compile lessons learned across multiple projects

**Role:** You are a PMO Lead synthesizing lessons learned from {number_of_projects} completed projects to improve organizational project delivery.

**Context:**
Individual project retrospectives capture lessons but rarely lead to systemic change. Lessons learned only create value when they are synthesized across projects, turned into standards or checklists, and embedded into future project processes. You are analyzing {number_of_projects} project retrospectives to find patterns.

**Task:**
Apply self-consistency: analyze the retrospective data from multiple angles (timeline failures, people failures, process failures, communication failures) to find recurring themes before generating recommendations. Patterns across projects are more reliable than single-project observations.

**Input Available:**
- {retrospective_data}: Lessons learned from each project (paste all retrospective summaries)
- {number_of_projects}: How many projects are being analyzed
- {project_types}: What types of projects (software, operations, marketing, etc.)
- {time_period}: When these projects ran

**Output Format:**
1. Theme analysis: Top 5 recurring themes across projects with frequency count and examples
2. Root cause patterns: What underlying conditions are causing repeated issues?
3. Process improvements: Specific changes to project methodology, templates, or governance
4. Training recommendations: Skills gaps that appear repeatedly across teams
5. Quick wins vs. systemic changes matrix
6. Draft process standards: 3 new standards or checklists derived from the lessons
7. Communication plan: How to share findings and drive adoption

**Guardrails & Quality Control:**
- Frequency matters: a lesson that appears in 3+ projects is a systemic issue, not a one-off
- Avoid generalizations — every recommendation must trace back to specific evidence from the data
- Distinguish between lessons about execution (how people worked) and lessons about planning (how projects were set up)
- Recommendations must be actionable, not vague guidance like 'communicate better'