Most founders evaluate too often or not at all.
Too often looks like checking metrics daily, reading the scoreboard for emotional confirmation, course-correcting against weekly noise that is not actually signal. Not at all looks like the annual review that arrives 12 months after a problem could have been caught.
Neither produces good decisions. The right cadence is weekly for tactical, monthly for operational, quarterly for strategic. This post is the protocol for the weekly version, what most founders skip, and why skipping it lets the business drift in ways that compound expensively over time.
Why Weekly
Weekly is the cadence at which the small course corrections matter.
Daily is too short. Most metrics fluctuate enough day-to-day that interpreting the variation as signal produces panic-driven decisions. Daily reviews tend to look at metrics that move every day for reasons that have nothing to do with strategy, traffic from one viral post, a customer who happened to email back, an ad that performed weirdly for 24 hours.
Quarterly is too long for the tactical layer. Twelve weeks of accumulated small drifts can produce a serious gap between intention and reality. A founder who reviews quarterly catches the drift after it has compounded. A weekly review catches it while it is still 5-10% off, when it can be corrected with a small adjustment rather than a major reorientation.
Monthly is the right cadence for operational metrics, revenue, customer count, churn rate. Quarterly is the right cadence for strategic metrics, whether the broader trajectory is on track. Weekly serves the layer above day-to-day execution and below operational evaluation. Specifically:
- Did the activity that was supposed to happen this week actually happen
- Did the leading indicator targets get hit
- What is the priority shape of next week
- What needs to come off the plate that snuck on during the week
Done well, the weekly review takes 30-60 minutes and produces a calmer, clearer next week. Done badly or skipped, the business drifts.
The Five Questions
A weekly review answers five questions. In writing. Same time every week.
Question 1: What did I actually do this week?
Pull up the calendar. Look at what got executed versus what was planned. The gap is informative.
If most of what was planned got done, the calendar design is working, Monday's intentions survived contact with the actual week. If significant blocks got displaced, the displacement is itself the data. Why did it get displaced. Was the displacement legitimate (an actual emergency) or symptomatic (chronic overcommitment, unclear priorities)?
The honest answer to "what did I actually do" reveals the gap between the operating system as designed and the operating system in practice.
Question 2: What did the leading indicator do?
Pull up the daily leading indicator number, the one number that is supposed to predict whether the business is on track. Look at the week's average versus the target.
If the average is at or above target, the activity that produces revenue happened. The week was, by definition, productive in the way the business needs.
If the average is below target, the underlying activity is off pace. Either the activity needs to increase next week (more output of the same kind), the activity is misallocated (right volume, wrong target), or the assumption behind the leading indicator is wrong (more on this in question 5).
Question 3: What is the priority shape of next week?
Not a to-do list. The shape: what is the dominant focus of next week, what are the 2-3 specific outcomes the week needs to produce, and what is the buffer level on the calendar.
The shape sets the frame for how the calendar gets built. A week dominated by a launch looks different from a week dominated by recovery from a launch. A week with a customer in town looks different from a week without. Naming the shape up front prevents the week from becoming whatever happens to land in the inbox.
Question 4: What needs to come off the plate?
Each week accumulates commitments, meetings agreed to in passing, projects that grew beyond their original scope, tasks that snuck onto the list because they felt urgent at the time. By the end of the week, some of those commitments are no longer worth keeping.
The honest pruning question: if I were starting next week from scratch, what on the calendar would not be there. Whatever the answer is, that is the work to either cancel, reschedule, or delegate.
Most founders skip this question because pruning feels uncomfortable. Sending the email that says "I need to step back from this" feels worse than carrying the commitment for another week. The compounding effect of unpruned commitments is what produces calendar collapse over time. Weekly pruning prevents the collapse.
Question 5: What did I learn this week that should change something?
Specific events that reveal something about the operation. A customer asked a question that pointed to a gap in the offer. A piece of marketing landed differently than expected. A recurring task took twice as long as it should have. A team member raised an issue.
The question is not "what happened", it is "what did I learn that should change something next week or in the system."
This question often produces the highest-leverage outputs of the review. Most weekly insights get noticed in the moment, then forgotten by the time they would matter. Capturing them in the review makes them actionable rather than ephemeral.
The Logistics
Three logistical points that determine whether the review actually happens.
Same time every week. The weekly review survives only if it is on the calendar at a fixed time. Friday afternoon and Monday morning are the most common slots. Friday afternoon allows the week to be reflected on while it is still recent and lets the upcoming week be designed before the weekend ends. Monday morning lets the upcoming week be designed with fresh perspective but reflects on the previous week from a slightly stale memory.
Either works. Pick one and protect it. Reviews that float to "whenever I have time" do not happen.
In writing. The review's value comes from the writing, not the thinking. Thinking about the questions in your head produces vague conclusions. Writing the answers produces specifics. The discipline of putting words on paper or screen is what surfaces the insights that thinking alone misses.
A simple template, five questions, a half-page each, is enough. Many founders use a recurring document, with each week's review filed in chronological order. This produces a long-term archive that becomes useful for spotting patterns months later.
45 minutes maximum. Reviews that take 2-3 hours either drift into rumination or get scheduled less consistently because they feel burdensome. The 45-minute version, done weekly without fail, beats the elaborate version done monthly. Constraint forces the review to focus on what actually matters.
What to Avoid
Avoid 1: Confusing the review with planning. The weekly review reflects on the past week and sets the shape of next week. It is not the place to plan the launch in October, design the new product, or rethink positioning. Those are different exercises with different cadences. Mixing them collapses both into shallow versions.
Avoid 2: Avoiding hard answers. The questions in the review sometimes produce uncomfortable answers, the leading indicator was missed, the calendar got displaced, a commitment needs to come off the plate. Founders who write softer answers to make themselves feel better are sabotaging the value of the review. The discomfort is the data. Better to write it down honestly.
Avoid 3: Reviewing in someone else's framework. There are popular weekly review templates with 30+ questions, elaborate scoring systems, gratitude sections, intention setting. Most of them produce reviews that look impressive but do not change what happens next week. The five-question version above is enough. Add complexity only if the simple version proves insufficient, most founders find it does not.
Avoid 4: Treating the review as optional during busy weeks. The busiest weeks are the most important to review. They are also the weeks the review is most often skipped, because there is no time. The compounding effect: weeks that needed a review most are the ones that did not get one, which means the drift goes uncaught, which makes the next busy week worse. Protecting the review during busy weeks is the test of whether the discipline holds.
What the Review Reveals Over Time
A weekly review done consistently for 12 weeks produces a different kind of insight than any single review.
Patterns emerge. Maybe the leading indicator gets missed every third week, and the third weeks have a common feature (a recurring meeting that displaces work, a particular kind of client work that bleeds energy). Maybe certain commitments keep showing up on the "should come off" list but never come off. Maybe the priority shape of the week tends to get hijacked by Wednesday for similar reasons each time.
These patterns are invisible to single-review introspection. They appear only across multiple reviews, when the documentation accumulates. This is the deeper value of writing reviews down, the archive becomes diagnostic.
A founder who reads back through 12 weeks of reviews can see the structural issues that single-week observation misses. Those issues then become the focus of monthly or quarterly work, where structural changes happen.
What This Produces
The weekly review changes the trajectory of the business through accumulation, not single events.
Within 30 days. The first 4 reviews establish the rhythm. The first 1-2 are awkward, the questions feel forced, the writing is stilted. By review 4, the format has settled. Each week's review takes less time and produces sharper output.
Within 90 days. The first quarter of weekly reviews has produced enough archive to read back. Patterns become visible. The leading indicator's variability has been observed across 12 weeks, which produces a much better sense of what is signal and what is noise. The calendar has been pruned of commitments that did not earn their keep.
Within a year. The compounding shows. Each week's small course correction has prevented the kind of major drift that requires major rework. The business has not had to do an emergency reorientation in the past year, because the small ones happened weekly and prevented the need.
Across years. Weekly reviews build the habit of evaluating before committing further. Founders who run weekly reviews consistently across multiple years tend to have businesses that grow steadily without dramatic ups and downs. The flat parts of the trajectory get caught and corrected before they become canyons.
The metrics cascade is what closes the gap between goal and daily activity. The weekly review is what keeps the cascade honest. Done weekly, in writing, against the same five questions, the review is the smallest, most reliable, most underrated discipline in operations.
That is the protocol. Five questions. Same time, in writing, 45 minutes maximum. Done weekly without exception, especially during busy weeks.
The week that gets reviewed is the week that produces compound improvement. The week that does not is the week that drifts.
The Seven Figure Framework. An email series on positioning, metrics, and execution for founders ready to scale. Free.