Frameworks & Tools
A few years ago, I started noticing a pattern in almost every project I touched, whether it was a workshop I'd just wrapped, a pageant interview a client had just walked out of, or a community event I'd spent months building toward. The event would end. Everyone would exhale. And then, almost without exception, we'd move straight on to the next thing without ever asking what the last thing had actually taught us.
I used to think that meant we all just needed to be more disciplined about reflecting. The more I watched it happen, though, the more I realized it wasn't a willpower issue at all. Most of us were simply never handed a system for what to do with an experience after it happens, so we default to one of three things: we forget it entirely and move on, we replay it in our heads until we've talked ourselves into feeling bad about it, or we only celebrate the parts that went well and quietly skip the parts that didn't. None of those are reflection. They're just what fills the space when reflection doesn't have a structure to live in.
The tool I use to fill that space is called an After Action Review, or AAR. I didn't invent it. It comes out of military and organizational debrief practice, and if you've ever run an agile sprint retrospective, the shape will feel familiar to you: look at what happened, name what worked, name what didn't, and decide what changes before you do it again. What I've done is adapt it into something I now use in nearly every part of my work, with executive coaching clients evaluating a quarter, with pageant clients debriefing an interview round, and with organizations closing out a workshop or a launch.
What an After Action Review Actually Is
An AAR is a structured way to debrief once something wraps, before the details fade and before your feelings about it have hardened into a story you're no longer questioning. It's built to do four things:
- Help you reflect intentionally, instead of just emotionally
- Capture what worked, and why it worked, so you can repeat it on purpose
- Unpack what didn't work without turning it into self-criticism
- Turn the whole thing into a repeatable system, so momentum builds instead of resetting every time
The point isn't to ask “how did that go?” The point is to capture what you genuinely can't afford to forget next time, and to turn it into something you can actually use instead of a feeling you carry around.
Why Most Reflection Doesn't Work
If reflection were natural, everyone would already be doing it well. Most people don't, and it's usually for one of three reasons. Some people avoid it completely and just move to the next thing. Some people get stuck in a loop of unproductive self-critique, replaying a mistake without ever landing on what to do differently. And some people only reflect on the wins, which feels good in the moment but skips the exact information that would help them improve.
What changes when you embed reflection into your process, when it becomes the default step at the end of anything rather than something you do occasionally, is that you start building three things you can't get any other way: clarity on what actually matters versus what just felt urgent, systems that evolve alongside you instead of staying static, and a kind of confidence that isn't dependent on the outcome, because you know you'll learn from it either way.
The Framework
This is the version I use across every setting I coach in, whether the client in front of me is a titleholder debriefing an interview, an executive closing out a quarter, or an organization wrapping a community initiative. I ask the same five questions every time. What shifts is who's sitting across from me and what they're debriefing.
- Start with the good. What went well? What contributed to that success? What do you want to do exactly the same way next time?
- Explore what didn't go as planned. Where did things feel misaligned, confusing, or clunky? What slowed things down? What surprised you?
- Look forward. What could improve next time? What needs to shift at the systems level, not just the effort level? Where is there room to experiment?
- Assign action steps. Turn every insight into something concrete, with a deadline attached. Delegate what needs delegating. Make sure the changes actually get implemented instead of just written down.
- Close with reflection. What are you proud of? How did this experience grow you? What's the one takeaway you don't want to lose?
The Same Framework, Three Different Rooms
What I keep coming back to is that this framework doesn't change shape depending on who's using it. It just gets pointed at different material.
In organizational strategy work, I use this after a workshop, a strategic planning session, or a launch. The team debriefs together, often with sticky notes and a whiteboard, and the fifth question (what's the one takeaway) usually becomes the thing that actually shapes the next quarter's priorities, not just a nice thing someone said in a meeting.
In career and leadership coaching, this becomes the structure for a quarterly check-in. Instead of vaguely asking a client how their year is going, we run the actual framework against a specific project or decision. It turns “I feel like things are going okay” into something a client can act on.
In pageant coaching, I use a version of this worksheet to debrief interview rounds, stage presence, and prep strategy with clients immediately after competition, while the details are still sharp. It's the difference between a titleholder who improves every time she competes and one who just hopes the next round goes better.
That's the whole idea behind design thinking as a transferable skill rather than a topic you study once. The same framework that helps an executive team learn from a product launch is the one that helps a candidate learn from a five-minute interview, because what's actually being taught was never the subject matter. It was the system for getting better at anything, once you've done it.
A Debrief Isn't Just for the Big Moments
You don't need a major event to justify running an AAR. I use the same system after speaking engagements, after a particularly demanding season winds down, or any time a routine or workflow starts to feel stale and I can't immediately name why. What makes something worth debriefing was never really the scale of it. It's simply whether you did it, and whether there's something in it you could learn from.
Where to Start
You don't need a productivity overhaul to make this work. You need to build one pause into your rhythm, the one where you stop before moving to the next thing and ask what the last thing actually taught you. Do that consistently, and you find the momentum was never about doing more of anything. It was about getting a little better every single time.
If you want a structured way to start, I built a free AAR worksheet you can use to debrief your next event, campaign, workshop, or milestone, solo, with your team, or inside a coaching session.
And if you're ready to build this kind of intentional system into how you or your organization grows, let's talk.