# Lead a Project Retrospective Discussion Walk through a significant past project as a retrospective. Explain the hardest part, how the team addressed it, the trade-offs you made, what happened, and what you would do differently now. ### Constraints & Assumptions - Use a real project and protect confidential information where needed. - Separate your decisions and actions from collective team work. - Choose a difficulty that required judgment, not merely long hours. - Include evidence of outcome and learning, including disappointing results when relevant. ### Clarifying Questions to Ask - Would you prefer technical depth, execution and collaboration, or both? - How much project context should I provide before focusing on the difficult part? - Is there a particular competency you want the retrospective to illuminate? - May I generalize sensitive metrics while preserving their direction and scale? ### Hints - Spend less time on background and more time on the decision under uncertainty. - Compare at least one credible alternative. - Show how the lesson changed later behavior. ### What a Strong Answer Covers - Problem, stakeholders, constraints, personal scope, and success criteria. - A specific obstacle, its root cause, and why the obvious answer was insufficient. - Alternatives, evidence, disagreement, decision, execution, and risk management. - Outcome with honest attribution, metrics, limitations, and unintended effects. - A concrete lesson demonstrated in subsequent work rather than a generic slogan. - Clear communication that invites technical and behavioral follow-ups. ### Follow-up Questions 1. What did you believe initially that turned out to be wrong? 2. Who disagreed with your approach, and how was the decision resolved? 3. Which trade-off had the largest long-term cost? 4. What would you change if you had half the time or twice the scale? 5. How did this project alter how you lead later work?