30-Minutes Retrospective

You finished the project. You celebrated. You moved on. And six months from now, you'll make exactly the same mistakes — because nobody spent 30 minutes asking why.

Be honest: how many times has your team repeated the same scope creep, the same estimation error, the same client miscommunication — project after project? Not because you're bad at what you do. Because finishing a project and learning from it are two completely different activities, and your team only does the first one.

The 30-Minute Retrospective is the book for every small team that's tired of making the same avoidable mistakes. It gives you a dead-simple framework — four questions, 30 minutes, no facilitator training required — that turns project hindsight into your team's biggest competitive advantage.

This is NOT an Agile book. No sprints. No Scrum Masters. No methodology you need to adopt first. This is for the team of 3 or 12 or 20 that runs projects — software, design, marketing, consulting, construction, anything — and has never done a retrospective in their lives.

Inside, you'll find:

• Why teams don't learn — the five traps that guarantee you'll repeat every mistake, and how to break them

• A complete 30-minute retrospective format anyone on your team can facilitate, with a minute-by-minute guide

• How to make it genuinely blameless — not "pretend nobody did anything wrong" blameless, but "fix the system, not the person" blameless. Including exactly what to say when someone gets defensive or tries to point fingers

• What to do with what you learn — because a lessons-learned document nobody reads is worse than useless. You'll get a one-page summary format, a 5-minute follow-up check, and a team learning log that becomes your institutional memory

• How to run retrospectives during a project, not just after — the 15-minute mid-project check-in that catches problems while you can still fix them

• A solo retrospective for freelancers and one-person businesses — five questions, 15 minutes, after every project

• How to build a learning culture that survives past the first three attempts — because starting retrospectives is easy; keeping them alive is the real challenge

Every chapter opens with a real-world story of a team that got it wrong, delivers one practical concept, and closes with something you can use this week. No theory. No jargon. No fluff.

The most expensive lesson is the one you learn twice. This book makes sure you don't have to.