The Weekly Retrospective: How to Run Sprints on Your Life

The fourth step of the engineering framework for a life is speeding up the cycle. Most of us run the parts that matter most on the slowest possible cadence.

By Peter Plötner. Aerospace engineer and Wayfinder Life Coach. More about Peter →

Here is a fact that sounds backwards until you have lived inside it.

A rocket engine factory that builds four hundred engines a year has fewer quality problems per engine than one that builds twenty. Not more. Fewer. The faster line makes better engines.

When you build a small number of complex things slowly, every problem is a special case. You can work around it. You can document it. You can hand it to the one specialist who understands it. The system tolerates a lot of mess because the mess is rare.

When you build at high cadence, you cannot work around problems anymore. They show up too often. They have to be fixed at the root, or they pile up and stop the line. High cadence is not just a measure of speed. It is a forcing function for quality.

You see the same thing with trains. The Tokaido Shinkansen runs trains every few minutes and counts one as delayed if it arrives more than a single minute late. Deutsche Bahn runs its long distance trains every half hour to an hour and counts one as on time if it arrives within six minutes. Even with that much gentler definition, only about 62 percent of German long distance trains were on time in 2024. The Shinkansen, using a far stricter standard, measures its average delay in seconds. The system that runs at higher cadence is, by an enormous margin, the more reliable one. It has to be. You cannot run that often on a system full of unsolved problems.

This is the fourth step of the framework I have been writing about. After you question your requirements, delete what you can, and simplify what remains, you speed up the cycle. And most of us are running the most important parts of our lives on the slowest possible cadence.

The annual review is the problem

Think about how rarely we actually check the systems that matter most.

We review our careers once a year, if a manager forces us to. We reflect on our marriage when something goes wrong. We check in on our health when a symptom finally gets too loud to ignore. We think about whether our work still means anything roughly never, until a birthday with a zero in it arrives and the question shows up uninvited.

The cadence is so slow that we never have to fix anything at the root. We just work around it. Again and again, year after year, until something big enough breaks that we cannot route around it anymore.

A slow life can hide an enormous amount of quiet wrongness. A fast cycle cannot. That is the whole point of speeding up. Not to do more. To find the problems while they are still small enough to fix.

For a life, the fast cycle has a simple name. The weekly retrospective.

What mine actually looks like

I want to be honest that I have not perfected this. My weekly check-in changes all the time, and it changed the most when I had a wife and small children, because now my week depends partly on their needs and not just my plans. That turned out to be a gift. My kids are one of the biggest reasons I work on my patience and my emotional awareness at all. They are also a daily reminder of how much lighter everything gets in the moments I meet it with joy and peace instead of friction.

The check-in itself is short. Three to five minutes. I ask a small set of questions.

What are my priorities right now. Have they changed since last week. Did last week actually reflect them. Does next week reflect them. And the most useful one: what is sitting on my schedule that I can drop, because it is not actually one of my priorities at all.

Some weeks I write it down and some weeks I do not. It depends on how complex the week is. One of my standing priorities is my coaching hours, and I do not need to write that down, it is always there. But when we are traveling, which we do often, I write down every small detail, because the small details are exactly what fall through the cracks.

That is it. No app. No elaborate system. A few honest questions, once a week.

Why I started

I did not always do this. For years I ran my side projects on mood. I worked on them when I felt like it. It was slower, but things still got done, because I had time to spare. If I was not in the mood today, there was always next week.

Then I had a wife, two kids, and a full time job, and I decided to train as a coach anyway.

My family comes first. That is not in question. But it does mean that coaching, the thing I had chosen to build on the side, got whatever was left over. And what was left over was about sixty minutes a day.

And I learned something uncomfortable. If I waited until I was in the mood to use those sixty minutes, coaching went nowhere. The mood did not come often enough. The time was too scarce to spend it waiting.

The honest lesson, the one that stings a little: this approach would have worked even better back when I had more time. I just could not see it then, because I had enough slack to hide the cost. Scarcity taught me what abundance never could. When the cycle is tight, you cannot coast. And not coasting turns out to be the whole secret.

The difference between a retro and a beating

There is a way to do this that makes your life better, and a way to do it that just makes you feel bad. The line between them matters more than the practice itself.

A useful retrospective sounds like this. That is what happened. That would have worked better. How can I use what I learned for next week. It is honest, and it is kind at the same time. Those two are not in conflict. The trap is the fake honesty that is really just being mean to yourself in a costume. I should have known. I always do this. I ruined it again.

In engineering we have a cleaner way to think about this. We do a small root cause analysis, and we do not look for who is at fault. We look for what the actual cause was, because the cause is almost always a system or a process, and almost never one bad person having one bad week. Root cause is rarely a single thing.

So the weekly question is not who failed. It is what is one small thing I could change to make next week one percent better. I did the best I could with what I had. What is the best I can do next time. That is the whole tone. A tiny, kind root cause analysis, once a week, aimed at one percent.

When something clearly did not work, I run it through three options I picked up in my coaching training, the three B's. Bag it, because it was never actually a priority and it can go. Barter it, because someone else can do it better or it was never mine to carry. Or better it, because it matters and the current version is just rough. The mistake is reaching for better it when the honest answer was bag it. Do not optimize the part that should not exist. We covered that two essays ago, and it shows up here every single week.

Why consistency beats intensity

Here is the engineering principle hiding underneath all of this. An object at rest stays at rest. An object in motion stays in motion. Newton's first law. Inertia.

Your habits obey the same law. When I am having coaching sessions every week, the next session is easy. The system is in motion and it wants to stay in motion. But when life happens and I miss a few weeks, restarting takes far more energy than continuing ever did. The object at rest does not want to move. I have felt this dozens of times. The cost of stopping is not the weeks you miss. The cost is the activation energy to start again.

This is the real argument for a weekly cadence. Not discipline for its own sake. Inertia. A weekly retrospective keeps the flywheel turning, and a turning flywheel is cheap to keep turning. A stopped one is expensive to restart.

And some weeks you will stop anyway. Life happens. Sometimes you are in reactive mode instead of proactive mode, and that is genuinely okay. The skill is not never stopping. The skill is noticing you have stopped, without the beating, and gently getting the flywheel moving again.

It will not work the first week

The most common reason people quit a weekly check-in is that they expect it to work immediately. They try it twice, feel nothing, and conclude it is not for them.

But think about how anything real gets learned.

A child needs to taste a new food somewhere between eight and fifteen times before they accept it. Not once. Not twice. Eight to fifteen exposures, most of them apparent rejections, before the thing clicks. The parent who gives up after the third try never finds out that the twelfth would have worked.

Nobody concludes a vegetable is hopeless because a toddler spat it out twice. We understand, with food, that repetition with small variations is how a taste gets built. We just forget to extend the same patience to ourselves.

A weekly retrospective is the same. The first few will feel clumsy and pointless. That is not the practice failing. That is the practice working, exactly the way learning always looks from the inside. More tries, with the learning folded back in each time, is just a higher chance of success wearing an uncomfortable disguise.

I should also be honest that the soft side of this is harder than the engineering side, not easier. In engineering you have a spec, and the solution either meets it or it does not. With the human skills, there is no clean spec. You are either slightly too sure of yourself or not sure enough, and being exactly the right amount is almost impossible to hold. It is like running an optimization to find the best point on a curve, except the curve has many dimensions and it keeps moving while you search. You never arrive. You just keep adjusting. The weekly cycle is how you keep adjusting without losing the thread.

Try this week

Pick a day. Any day. Give it five minutes.

Ask yourself four questions, and be kind while you do it.

What actually mattered to me this week? Did my week reflect that? Does next week reflect it? What can I drop that was never really mine to carry?

Write down whatever needs writing down and leave the rest in your head. Then stop. Do not turn it into a project. Do not build a system around it. Five minutes, four questions, once.

It will feel small and slightly pointless the first time. Do it again next week anyway. You are not looking for a breakthrough. You are looking for one percent, and a flywheel that keeps turning because you kept showing up to give it a push.

The process is the point. Not the destination. The whole life is built one quiet week at a time.

Frequently asked questions

What is the difference between a weekly retrospective and just journaling?

A journal records what happened. A retrospective asks one more question: what would I change for next week? It is short, it is forward-looking, and it ends in a tiny adjustment. Three to five minutes, four questions, aimed at making next week one percent better. If your journaling already does that, you are already running a retro.

How long should it take and how often?

Five minutes, once a week. That is the whole point. The value is not in the depth of any single session, it is in the cadence. A short check-in you actually do every week beats a deep review you do twice a year and then abandon. If it grows into a thirty-minute ritual, you will quietly stop doing it.

What are the three B's?

When something on your plate did not work, you have three honest options. Bag it, if it was never really a priority. Barter it, if someone else can do it better or it was never yours to carry. Or better it, if it matters and the current version is just rough. The common mistake is reaching for “better it” when the honest answer was “bag it.”

How do I keep it from turning into self-criticism?

Treat it like a root cause analysis, not a search for who is at fault. In engineering, the cause is almost always a system or a process, rarely one person having one bad week. Ask “what is one small thing I could change,” not “why do I always do this.” Honest and kind are not in conflict. If it feels like a beating, you are doing the wrong version.

What if I miss a few weeks?

You will, and that is okay. The skill is not never stopping. It is noticing you have stopped, without the beating, and gently starting again. A stopped flywheel is expensive to restart, so the sooner you give it a small push, the cheaper it is. One five-minute check-in is enough to get it turning again.

This essay is the fourth step of an engineering framework for redesigning a life. The whole algorithm starts in Stop Optimizing Your Life. Start Specifying It. The deletion step is The Best Part Is No Part, and the simplification step before this one is Why Your Life Won't Run Smoothly Until You Stop Trying. If you want a place to start, the Essential Self Diagnostic is fifteen questions that take about sixty seconds, a quick read on which parts of your life are still carrying their weight.