1
0 Comments

The weekly retrospective practice that changed how I build — full template included

I've tried a lot of productivity systems.

Notion dashboards. Time blocking. Pomodoro timers. Task managers with every feature imaginable.

Most of them helped temporarily and then became overhead I stopped maintaining.

The one practice that has stuck for over a year, that I still do every single Friday without skipping:

A 15-minute weekly retrospective.

Not because it's the most sophisticated system. Because it's the most honest one.

The full template:

Section 1: What actually shipped this week?

Not what I worked on. Not what I made progress on. What actually shipped, committed, published, or sent.

The distinction matters. "Working on" is infinite. "Shipped" is binary.

This section is often humbling. I can spend a very busy week and have a short list here. That gap between busy and productive is important to see clearly.

Section 2: What slowed me down that was within my control?

Key phrase: within my control.

I'm not interested in cataloguing bad luck or external blockers — those are real but I can't fix them.

I'm looking for patterns in my own behaviour.

Common things I've found here over the past year:

  • Starting new things before finishing existing ones
  • Spending too long on technical decisions that could have been made quickly and adjusted later
  • Not writing down decisions as I made them, then spending time reconstructing my own reasoning later
  • Doing deep work during the low-energy part of my day and shallow admin during the high-energy part

None of these are surprising when I write them. They're patterns I already know about. But seeing them week after week makes them harder to ignore.

Section 3: What is the one thing that matters most next week?

One. Not three. Not five.

This is the hardest part. It requires deciding what actually matters — not just what's urgent.

The things that are urgent and unimportant will always demand attention. The one thing that matters most often won't shout.

Writing it down on Friday means Monday morning I already know what I'm doing first. Not checking emails. Not planning. The one thing.

What has changed from doing this:

After 3 months: I noticed I was consistently slow on Tuesday afternoons. I changed what I scheduled then.

After 6 months: I noticed a pattern of starting new features before shipping existing ones. I added a personal rule: nothing new starts until the current thing ships.

After a year: I can look back and see the actual shape of how I work — where I'm improving, where I keep hitting the same walls, what kinds of work produce the best output for me.

None of this came from a productivity app. It came from 15 minutes of honest writing every Friday.

Why most productivity systems fail:

They're designed around managing tasks.
This is designed around understanding yourself.

Tasks change. You don't — not without deliberate reflection.

The retrospective is the deliberate reflection.

Anyone else have a weekly reflection practice? What does yours look like?

on June 12, 2026