You set goals in January, and by April you can’t say which still matter, which are quietly dead, or whether anything you did each week moved the needle. A yearly plan is too slow to catch drift, and a weekly plan is too close to see it.
One 90-minute session every 13 weeks closes that gap. It has four jobs: audit what last quarter actually produced, score the numbers that predicted it, choose one theme for the next 90 days with 30-60-90 checkpoints, and put that theme in your calendar before you close the notebook.
Why most quarterly reviews change nothing
The common version is a mood check. You ask “how did the quarter go?”, answer from memory, and write a fresh list of eight goals. Memory over-weights the last three weeks and the loudest project, so the plan repeats last quarter’s mistakes.
The second failure is reviewing only one side. Field research on after-event reviews that examine both successes and failures found they build richer mental models of what drives results than reviews of failures alone. Ask why the wins shipped, not only what went wrong.
The third failure is ending with intentions instead of calendar entries. If the theme has no recurring time on Monday morning, the quarter goes to whatever lands in your inbox.
The 90-minute session, phase by phase
Before you start, gather your calendar for the past 13 weeks, your task list including completed items, any tracking you kept (a habit log, a done list, a spreadsheet) and your annual goals. Gathering takes about ten minutes and sits outside the 90.
| Phase | Time | Question to answer | Written output |
|---|---|---|---|
| 1. Past quarter audit | 25 min | What did I start, finish, stall and abandon, and why? | Project list tagged Completed / Stalled / Abandoned / Ongoing, with a kill-defer-reshape decision for each non-finished item |
| 2. Leading vs. lagging scorecard | 20 min | Did I do the inputs I planned, and did the outcomes follow? | One row per goal: input target vs. actual, outcome target vs. actual, diagnosis |
| 3. Next 90-day theme and checkpoints | 30 min | What single result would make the next 13 weeks a success? | Theme sentence, day-30/60/90 deliverables, two weekly input targets, one named obstacle |
| 4. Calendar block setup | 15 min | Where, exactly, will this work happen each week? | Recurring theme blocks, two checkpoint reviews, next quarterly review booked |
Phase 1: Audit completed and abandoned projects (25 minutes)
Scroll through the calendar week by week and list every project you started, not just the ones you planned. Tag each one Completed, Ongoing, Stalled or Abandoned. Start with the completed items: for each, write one line on what made it ship (a deadline, a collaborator, a fixed weekly slot).
Then make a formal decision on every stalled or abandoned item: kill it, defer it to a named quarter, or reshape it into something smaller. Research on goal disengagement links explicitly letting go of unattainable goals, and reinvesting in alternatives, to better well-being. Half-abandoned projects otherwise keep claiming attention without getting work.
Follow one example through all four phases: a GIS technician who wants to move into machine-learning work. The audit finds 11 projects started, 4 completed, 4 stalled and 3 abandoned. Two completions had a fixed deadline set by another department; none of the stalled ones, including an online machine-learning course, had any calendar time.
Phase 2: Score leading and lagging metrics (20 minutes)
A lagging metric is the outcome you wanted: revenue, chapters drafted, talks accepted, a race time. A leading metric is the input you control that should predict it: pitches sent, writing sessions held, training runs completed. Write the target and actual for both, for every goal from last quarter.
Put the scorecard on paper or in a sheet rather than eyeballing it. A meta-analysis of 138 experimental studies found that monitoring goal progress increases goal attainment, with larger effects when progress is physically recorded.
Then read each row against this diagnostic:
| Inputs (leading) | Outcome (lagging) | Diagnosis | Next-quarter move |
|---|---|---|---|
| Hit | Hit | The model works | Keep the inputs; raise the target modestly or move on to a new theme |
| Hit | Missed | Wrong inputs, or not enough time for results to show | Change the input, or give it one more quarter with a clear checkpoint |
| Missed | Missed | Execution problem, usually no protected time | Lower the input target and fix the calendar before touching the goal |
| Missed | Hit | Luck or an unmeasured driver | Find out what actually caused the result before repeating it |
The technician aimed for two accepted talks at regional GIS conferences (lagging) through six submitted abstracts (leading), but sent only two and had one accepted. That is an input problem, and the stalled course has the same cause. Both goals need protected time, so the talks move to Q3 and the machine-learning work gets the next quarter.
Phase 3: Choose one theme and set 30-60-90 checkpoints (30 minutes)
Pick one primary theme. Experiments on pursuing multiple goals at once show competing goals fight over the same limited time and effort, with people shifting resources toward whatever feels most urgent. Give every other area a written maintenance minimum, such as “two runs a week” or “savings transfer automated,” so it keeps running without competing for your best hours.
Write the theme as a verb, a domain and a finish line: “Ship a working machine-learning portfolio project using land-cover imagery,” not “get into AI.” If yours is still large, use the method for breaking big goals into actionable steps to find the next 13 weeks of it; if you prefer numeric key results, the personal OKR method slots in here unchanged.
Split the theme into three checkpoints. The 30-60-90 horizon comes from Michael Watkins’s The First 90 Days, written for leaders starting new roles; each checkpoint is close enough to feel urgent. Brian Moran and Michael Lennington’s The 12 Week Year makes a similar case: a shorter cycle removes the “plenty of time left” feeling of annual plans.
Each checkpoint should be something you can show. The technician sets: day 30, the course’s modules one to four finished and an imagery dataset chosen; day 60, a baseline classification model trained and evaluated; day 90, a demo map deployed with a short write-up. Two leading measures carry weekly targets: four 60-minute study blocks and one pushed commit.
Finish by naming the one obstacle most likely to sink the theme. Gabriele Oettingen’s research on mental contrasting found that picturing a desired future alone can sap effort, while pairing it with the obstacle in the way builds commitment. The technician’s obstacle: evenings disappear into ad-hoc map requests.
Phase 4: Translate the theme into calendar blocks (15 minutes)
Estimate the hours. Four 60-minute blocks a week across 12 working weeks is 48 hours, with week 13 kept as buffer. If 48 hours can’t produce the deployed map, shrink the deliverable now (a published notebook instead of a live map, say) rather than discovering it in week 11.
Then create recurring blocks at specific times, placed against that obstacle: for the technician, 7:00 to 8:00 Tuesday through Friday, before work. Add a busy-week version, such as two blocks instead of four, so a deadline week shrinks the input instead of erasing it.
Cal Newport argues for turning quarterly and weekly plans into dedicated time blocks so priority projects get real hours instead of leftover ones; our time blocking guide covers the mechanics. Before you finish, book a 30-minute monthly checkpoint review on day 30, another on day 60, and the next 90-minute quarterly review.
Your weekly planning then only has to defend those blocks and pick what goes in them; a 15-minute weekly plan is enough.
The 45-minute version for a chaotic quarter
If the quarter was dominated by a move, a launch or a family crisis, compress the review instead of skipping it:
- 10 minutes: tag projects and make kill-defer-reshape calls only for the stalled ones.
- 5 minutes: score just the one goal you care about most.
- 20 minutes: set a theme with a single day-90 deliverable and one weekly input target.
- 10 minutes: book two weekly blocks and the next review.
A small quarter that gets reviewed beats a skipped review that rolls three abandoned projects forward unexamined.
Running the January review as an annual reset
The first review of the year does double duty. Add 20 minutes before Phase 1 to look at the whole past year instead of the last 13 weeks.
Lay the four quarterly scorecards and kill notes side by side. Mark which goals survived all four quarters, which never got a calendar block, and which were deferred twice; a goal deferred in two consecutive reviews should be dropped rather than carried into another year.
Then write three to five annual outcomes as things you will do or have, not things you will quit. A large experiment on New Year’s resolutions found approach-oriented goals succeeded more often than avoidance-oriented ones, so “cook dinner at home four nights a week” beats “stop ordering takeaway.”
Run the normal session with one constraint: the Q1 theme must be the first 90-day slice of one annual outcome. Sketch the likely Q2 to Q4 themes in a line each and revisit them at every review, so January doesn’t become a dozen resolutions started at once.
Wording for pausing and killing commitments
The audit usually ends with commitments to pause. Say so explicitly instead of letting them fade.
- To a manager: “I’m pausing the onboarding docs refresh until July so the pricing page ships by 30 April. If the docs are more urgent, tell me which of the two to move.”
- To a side-project collaborator: “I can’t give the podcast real hours this quarter. Rather than half-show up, I’m stepping back until October. Can we talk then about whether it still makes sense?”
- A kill note to yourself: “Stopped the newsletter on 2 April. Reason: 3 issues, no growth, no paid interest. Revisit only if a client asks for it.”
- At a missed day-30 checkpoint: “Checkpoint missed by about two weeks. Cut the day-60 scope, keep the day-90 date, add one study block.”
Written decisions stop the same project from resurfacing as guilt in every weekly plan. When the next quarterly review arrives, those notes are the first thing Phase 1 reads.
2 Comments