The personal quarterly review

A personal quarterly review is a half-day, four times a year, in which you audit how you actually spent your time, energy and attention against what you said mattered — then set one priority for the next quarter. It is the same discipline a board applies to a company, applied to the operator. Most founders review their business quarterly and their own operating pattern never; this closes that gap.

Why quarterly, and not weekly or annually?

Because a quarter is the shortest period over which your patterns become visible and the longest over which they remain fixable. A week is noise: one bad sales week or one heavy delivery sprint tells you nothing about trajectory. A year is too long: by the time an annual review catches a drift — a service you resent, a calendar you no longer control — you have compounded it for twelve months.

Quarterly also matches how commitments decay. In pipeline terms, this decay is well documented: most firms stop at two follow-up touches while deals typically need five or more. Personal commitments behave the same way. The intention set in January is, by March, on touch two of five — still alive, but only if something deliberately re-engages it. The quarterly review is that deliberate touch.

Within The Personal Operating System, the review is the governance layer: the weekly routines do the running, and the quarterly review decides whether they are running in the right direction.

What do you actually review?

Evidence, not memory. Memory reliably reports the quarter you intended to have. Three sources tell you about the one you had:

• The calendar. Count the hours by category: delivery, sales, admin, management, thinking. The proportions are usually a surprise, and the surprise is the finding.
• The written record. Notes from your weekly thinking blocks, decisions made, projects started and quietly abandoned. Thinking blocks generate the raw material; the review is where it gets judged.
• A handful of numbers. Revenue, pipeline, hours worked, weeks of holiday actually taken. Five is plenty. The point is trend, not precision.

Then three questions against that evidence: What did I say the priority was? Where did the time actually go? What is the gap, and what caused it — a wrong priority, or a calendar that never protected it?

How do you run the review?

The mechanism, in order — each step feeds the next:

1. Book it like a client meeting. Half a day, out of the office if you can, recurring in the calendar for the year ahead. When it is booked in advance, then it survives busy quarters — which are precisely the quarters that need it.
2. Gather the evidence first. Thirty minutes assembling calendar counts, notes and numbers before any judgement. When evidence precedes opinion, the review audits; when opinion comes first, the review rationalises.
3. Write the gap analysis. One page: stated priority, actual allocation, the difference, the cause. Prose, so the reasoning has to hold together.
4. Decide the next quarter's one priority. Exactly one. When you name a single priority, then every scheduling conflict for the next thirteen weeks has a default answer. That single item becomes the top of your Now list and stays there until it is done or deliberately replaced.
5. Change one system, not five. Pick the single mechanism that would have closed this quarter's gap — a protected block, a delegation, a rule about new commitments — and install it before you leave the room.

Two to four hours, run this way, is enough. Longer reviews mostly produce longer documents.

What should come out of it?

Three artefacts, all short: a one-page written record of the quarter (the gap analysis), one named priority for the next quarter, and one system change with a date on it. If you cannot state all three in under a minute, the review produced reflection rather than decisions, and reflection without decisions does not change the next quarter.

Keep the one-pagers. After four of them you have something rare: a founder's honest operating history, in your own words, unavailable from any other source.

Why do these reviews usually fail?

Three ways. They get skipped in busy quarters — solved by booking all four a year ahead and treating them as client work. They turn into planning sessions, producing a thirty-item wish list instead of one priority — solved by the one-priority rule, however uncomfortable. Or they turn into self-criticism, which feels rigorous but changes nothing — solved by the systems framing: every gap is treated as a mechanism to redesign, not a character verdict. You would not close a board meeting by concluding the company should simply try harder. Do not close this one that way either.

---

Keep the thinking coming: The Format — a fortnightly letter on business and personal systems. Subscribe by email.