On the quiet
rigour of a weekly
review.

In the course of programme operations at AmpliSkill, I get to spend a strange amount of time around senior leaders. I help them through admissions interviews. I sit in on faculty conversations. I read their cohort reflections. I watch how they handle the small organizational frictions of a residential programme — the room change, the schedule shift, the late session.

Across this work, I have started to notice something. The leaders who consistently come across as the most composed, the most grounded, the most capable of holding multiple difficult things in mind at once — they almost all do the same small thing. They keep some version of a weekly review.

It is not a productivity ritual. It is not a journaling habit. It is not, in the way the term is sometimes used, a system. It is something quieter and more durable than any of those. And the way they describe it bears almost no resemblance to the way the practice is usually written about.

Section 01A small, recurring observation

I started paying attention to this maybe two years ago, almost by accident. We had asked a cohort of programme participants to write a short reflection on a habit or practice they had carried with them through their career. The responses came in. And among the senior-most participants — the CEOs, the senior partners, the founders — an unusually large fraction described some version of the same thing.

One called it her Friday hour. Another called it Sunday morning. A third referred to a notebook he had been keeping for fifteen years. The vocabulary varied. The substance did not.

Each of them, once a week, for somewhere between thirty minutes and two hours, sat down by themselves with a notebook or a document and quietly reviewed their week.

Section 02What it isn't

It is worth being precise about what this practice is not, because the genre of writing about "weekly reviews" has, over the last decade, accumulated a great deal of clutter.

It is not, first, a productivity system. None of the leaders I am describing were running a Getting Things Done methodology, or processing inboxes to zero, or moving items between contexts. The version they describe is much less concerned with task management and much more concerned with sense-making. Their tasks were handled in the normal flow of the week.

It is not, second, journaling. The journaling tradition emphasizes emotional processing, gratitude, and self-discovery. The leaders I am describing were not, for the most part, doing this. Their reviews were focused outward, on the work and the organization, more than inward, on the self.

And it is not, third, an optimization exercise. The leaders did not seem to be looking for ways to do next week better. They were, more simply, looking at what had happened and trying to understand it.

Section 03What it actually looks like

When I have asked them to describe what they actually do during the hour, the answers have been remarkably consistent. There is a structure that recurs.

They start with a quick narrative of the week. Not a calendar walk-through, but a paragraph or two summarizing what actually happened — what was decided, what shifted, what surprised them, who they spoke to that mattered. Several of them write this in past tense, as if narrating it to a future reader. One described it as "writing the week down so I have somewhere to put it."

They then look for patterns. Reading back over the previous three or four weeks, they look for things that have been quietly recurring. The same person mentioning the same concern. The same kind of decision arriving in slightly different costumes. A theme that has been showing up at the edges. Most of them say the patterns are easier to see at a four-week distance than a one-week distance — and that they would not see them at all if they did not write them down.

They identify, at most, two things they want to do something about. Not a long list of resolutions. One or two things, often quite specific. A conversation that has been deferred for three weeks and needs to happen. A decision that has been drifting and needs a closing date. A question that needs to be put on the next executive agenda.

They close with a short, almost private note. Several of them describe writing a sentence or two in the first person about something they got wrong, something they want to remember, or something they are uncertain about. This is the most personal part of the practice and the one they describe with the most reluctance — but several of them said it was the part that made the rest of the hour worth it.

Section 04Why it works

I am not the right person to write a definitive theory of why this practice works as well as it seems to. I have not done the research. What I can offer is what the leaders themselves have said, when I have asked them.

The most common answer is some version of: it makes me less reactive. The discipline of pausing once a week, in writing, to notice what is happening seems to give them a layer of distance from the daily flow of work that they would not otherwise have. Several have described it as the difference between being inside the week and watching the week.

The second most common answer is: it surfaces things I would have missed. The slow accumulation of a recurring concern, the quiet drift of a decision, the small change in someone's tone — these are easy to miss in the flood of normal work and surprisingly easy to see when you sit down once a week to look for them.

The third answer, more rarely, is: it reminds me what I am here to do. Several of the most senior leaders I have asked described their weekly hour as a private re-orientation. They sit down with the week, look at the four-line note from a year ago, and remember — sometimes with mild embarrassment — what they had been trying to build at that point. They reconnect with the longer arc.

A modest practice.

I find it striking, in writing this, how unremarkable the practice is. Thirty minutes once a week with a notebook. Four lines of structure. No system, no app, no productivity philosophy. Nothing that would survive being turned into a book.

And yet the leaders who do it consistently come across, in our work with them, as more grounded, more deliberate, and more in command of the long arc than the leaders who do not. The correlation is not perfect, of course. There are excellent leaders who do nothing of the kind. But it is striking enough that it has changed how I think about my own week.

If you have been considering some version of this and have been put off by the genre's tendency toward over-engineering, take heart. The leaders I am describing are not running a system. They are sitting down once a week with a notebook and writing down what happened. That, evidently, is enough.