Conduct a Structured After-Action Review to Turn Experience into Improvement

Act as an organizational learning facilitator experienced in U.S. Army-style After-Action Reviews (AARs) and agile retrospectives. Guide me through a rigorous after-action review for a recently completed project, initiative, or significant event so I can extract maximum learning and apply it going forward. Here is my context: - What was completed: [PROJECT/EVENT NAME AND BRIEF DESCRIPTION] - Original objectives and success criteria: [LIST 2-4 OBJECTIVES] - Actual outcomes achieved: [DESCRIBE WHAT ACTUALLY HAPPENED] - Timeline: planned [PLANNED DURATION] vs. actual [ACTUAL DURATION] - Team members involved: [LIST ROLES OR NAMES] - My initial gut feeling about how it went: [POSITIVE/MIXED/NEGATIVE — brief explanation] Please structure the AAR as follows: 1. **Outcome Scorecard**: Create a table comparing each original objective against the actual result, scored as Exceeded / Met / Partially Met / Missed. Add a one-line 'why' for each score. 2. **What Went Well (Sustain)**: Identify 5 specific things that contributed to success. For each, explain the underlying behavior or decision that made it work and how to systematize or replicate it in future projects. 3. **What Didn't Go Well (Improve)**: Identify 5 specific shortfalls or problems. For each, apply a brief root-cause analysis (not blame assignment) and distinguish between issues within our control vs. external factors. 4. **Surprises & Discoveries**: List 3 things that were unexpected — positive or negative — and what they reveal about blind spots in our planning process. 5. **Key Lessons Learned**: Distill the analysis into exactly 5 numbered, actionable lessons phrased as principles (e.g., 'Always validate assumptions with data before week 2'). Each should be specific enough to act on, not vague platitudes. 6. **Forward Action Items**: Create a table with columns: Action Item, Owner, Deadline, and Which Lesson It Addresses. Include at least 5 concrete next steps to embed the lessons into our workflow, templates, or checklists. 7. **One-Page Summary**: Provide a condensed one-page version of the entire AAR suitable for sharing with leadership or filing in a project knowledge base.