productivity
The Weekly Planning Method I Stole From a Military Officer
February 10, 2026
A military veteran showed me how after-action reviews work. I adapted the process for civilian life. Now I actually learn from my weeks instead of just surviving them.
I met James at a coffee shop. He was someone’s brother-in-law at a dinner party—the kind of person you don’t expect to change how you work. He’d spent twelve years in the military, left to start his own consulting business, and somehow had the kind of clarity that made everyone around him seem perpetually foggy.
We started talking about planning, which, in my world, is the same as admitting you’re struggling. He asked me how I review my weeks. I told him I don’t really—I just look at what didn’t get done and feel vaguely guilty about it, then move to the next week.
He nodded like he’d heard this a thousand times. “That’s the problem,” he said. “You’re not learning. You’re just cycling.”
He described something his unit did called an after-action review. It wasn’t motivational. It wasn’t about celebrating wins or brutal honesty for its own sake. It was structured, specific, and designed to make the next iteration better. He explained it quickly, and I wrote down four questions on a napkin because I could already feel it working.
I’ve been using his system for two years now. It’s the closest thing I’ve found to actually understanding why my weeks go the way they do.
What an After-Action Review Actually Is
The military version comes from a world where feedback loops matter. You run an operation, things happen, you gather people who were in it, and you ask: What did we set out to do? What actually happened? Why was there a gap? What do we do differently next time?
The key insight: it’s not about blame. It’s not about success or failure in the moral sense. It’s forensic. Clinical. You’re looking for the information that helps you perform better.
James adapted it for weekly planning, and the structure is this:
What was supposed to happen? This is your plan for the week. Not vague aspirations—actual commitments. The three things you blocked calendar time for. The projects you said were priority. The goals you named on Monday morning.
What actually happened? This is where you get honest. Which blocks did you keep? Which meetings expanded into your focus time? Which tasks got abandoned because something felt more urgent? Don’t judge it yet. Just document the gap.
Why did things play out this way? This is the hard part. It’s easy to say “I got distracted” or “life got busy.” The useful version is: I underestimated how long the client project would take, so I had no buffer when something came up. Or: I scheduled deep work at 2pm, but I’m a 10am brain, so I spent the time frustrated instead of focused. Or: I didn’t set a clear boundary around Slack, so notifications pulled my attention all day.
What’s one thing you’ll change next week? Pick one. Not five. One thing you’ll do differently because of what you learned. This week I might move focus time earlier. Next week I’ll block Slack off completely. The week after, I’ll give projects a 20% time buffer instead of a 10% buffer.
That’s it. Four questions. Takes about fifteen minutes if you actually think through them.
Why This Actually Works
Most people review their weeks by guilt. They look at their to-do list, see what’s still there, and feel bad about being inefficient. Then they grab the same to-do list, add five more things, and do the same thing over.
You’re not learning. You’re just spiraling with better intentions.
An after-action review doesn’t pretend your week went according to plan. It assumes it didn’t—not because you’re bad at planning, but because reality is more complicated than any plan. The whole point is to figure out why, so the next plan is closer to what actually works. This is why it pairs so well with actual productivity systems that you can iterate on—you’re not just building a system once, you’re building one that learns.
Here’s what changed for me: I stopped thinking of my week as something I failed at. Instead, I think of it as data. Did I build the right plan? Did I understand my own capacity? Did I account for how I actually work, not how I think I should work?
The second thing that changed: I got bored of repeating the same mistakes. When you name it—“I say yes to every meeting, which means my deep work never happens”—it’s harder to keep doing it. You don’t need more willpower. You just need to see the pattern clearly.
Third thing: I started protecting my time differently. Once I realized that my calendar blocks mean nothing if I don’t defend them, I changed how I talk about scheduling. Instead of “maybe I can shift things around,” it became “I’m booked.” Instead of assuming I have infinite flexibility, I started treating my own commitments with the same weight as client meetings.
This is especially important if you’ve read about calendar blocking as a productivity technique—the review process is what makes it actually stick, because you see immediately when blocks aren’t working and adjust them.
How to Actually Do This
Pick a time: Friday afternoon or Sunday evening. Doesn’t matter which. Pick something consistent, so it becomes part of your rhythm instead of something you’ll forget.
Grab a notebook or open a doc. Don’t over-engineer this. Write your four questions and answer them. Actual writing, not just thinking. There’s something about writing that makes you stop at the gap between “what I thought would happen” and “what happened.” Thinking lets you skip over it.
Answer the first two questions like you’re a reporter, not a judge. You planned X, Y happened instead. State it factually. Don’t spin it yet.
The third question is where the work lives. Why did things shift? Be specific. If you say “I got distracted,” follow up: by what? When? Why did that seem more urgent? Did I make a bad call, or was I actually wrong about what mattered? This is where you separate signal from noise—the difference between “I’m undisciplined” (usually not true) and “my system doesn’t account for how I actually work” (usually the real answer).
The fourth question has to be something you can actually do. Not “be better at managing my time.” Not “stay more focused.” Something concrete: “I’ll move deep work to 10am.” “I’ll do a 10-minute planning session every morning.” “I’ll set a Slack status during focus blocks.” You change one thing, see if it works, and then build from there.
This is close to the 2-list strategy for prioritization in one important way: it’s not about doing everything. It’s about changing one variable and seeing what happens.
The Thing Nobody Tells You
After a few weeks of doing this, something shifts. You start to trust your own judgment. Not because you get better at predicting the future—you don’t. You get better at understanding yourself.
You realize: I’m actually a person who needs a buffer before meetings to transition. I’m actually someone who does better with a physical to-do list even though I have three digital systems. I’m actually the kind of person who will skip lunch to finish something, so I need to protect breaks the way I protect meetings.
Those aren’t failures of discipline. Those are facts about how you work. The moment you stop fighting them and start planning around them, everything changes.
James left me with one more thing he said they repeated in the military: “You don’t learn from experience. You learn from reflection on experience.” Everyone gets through their week. Not everyone actually thinks about what it means.
Spend fifteen minutes on Friday understanding what your week taught you. Your next week will be different because you will be different.
And you don’t need a military background to steal that.