Weekly Founder Review: What to Review, Decide, and Stop
A practical weekly founder review for separating activity from progress, surfacing decisions, reviewing evidence, stopping low-value work, and setting a small number of priorities.
A weekly founder review should make the next week simpler
The purpose of a founder review is not to recreate every meeting, task, or metric from the previous seven days. It is to step out of the operating stream long enough to notice what changed, what deserves a decision, and where attention is being spent without enough return.
A good review creates fewer priorities and clearer commitments.
1. Start with what materially changed
Write the few changes that could affect company decisions: customer behavior, sales quality, product evidence, cash position, hiring, market movement, operational risk, or an important experiment result.
Avoid turning this section into a chronological activity log. Ask what is different now.
2. Review the current strategic priorities
For each priority, answer:
- What outcome were we trying to create?
- What evidence shows movement or lack of movement?
- What is the main blocker?
- Does the priority still deserve the same level of attention?
If a priority cannot be connected to an outcome, rewrite it.
3. Surface unresolved decisions
List decisions that are waiting, repeatedly reopening, or being avoided. Add the owner and the missing information.
Some decisions need more evidence. Others are simply uncomfortable. The review should make that distinction visible.
4. Check the important assumptions
What did the company assume about customers, pricing, acquisition, product behavior, hiring, or delivery? Did anything happen this week that increases or decreases confidence?
You do not need to maintain a giant assumption registry. Focus on beliefs that materially influence current bets.
5. Review a small KPI set
Look at the metrics tied to the current business model and priorities. Use the numbers to ask questions rather than treating movement as a conclusion.
If a metric changed, check whether the definition, segment, volume, or context changed too.
6. Look at customer and market signals
Bring a small sample of real evidence into the review: customer quotes, sales objections, support themes, lost-deal reasons, product behavior, competitor changes, or search demand.
A founder operating rhythm becomes stronger when strategy stays connected to the outside world.
7. Identify work to stop or reduce
Ask which meeting, report, campaign, process, feature, or commitment no longer justifies its cost.
Founders often add systems faster than they remove them. A stop list protects capacity for the priorities the review says matter.
8. Review risks and exceptions
Look for issues that could become expensive if ignored: cash, delivery quality, customer concentration, security, legal commitments, infrastructure, key-person dependencies, or another material risk for the business.
The aim is not a generic risk register. It is to prevent important exceptions from hiding behind routine work.
9. Choose the few outcomes for next week
Select a small set of outcomes or decisions that deserve attention. Write an owner and a definition of done.
“Work on onboarding” is weak. “Identify the two highest-friction steps from five observed onboarding sessions and decide which one to test” is much clearer.
10. Record decisions separately
Keep a decision log for choices that future-you may otherwise forget: what was decided, why, what evidence mattered, what trade-off was accepted, and when the decision should be revisited.
This prevents the same debate from restarting without new information.
A 30-minute review structure
A lightweight version can be:
- Five minutes — what changed?
- Five minutes — priority outcomes and KPIs.
- Five minutes — customer and market evidence.
- Five minutes — unresolved decisions and risks.
- Five minutes — what should stop?
- Five minutes — next week’s few outcomes and owners.
The exact timing is not important. The discipline is.
Keep the system lightweight enough to survive a busy week
If the review requires two hours of preparation, it will disappear when the company gets busy. Use a one-page template, link to deeper data only when necessary, and keep the focus on decisions.
A founder operating system is useful when it reduces ambiguity. The weekly review is the moment where scattered work becomes a small number of visible choices.