Most founders do not lack information. They lack a regular moment when the information is forced to become a decision. A weekly review is that moment, and it works only if it is small enough to survive a bad week.
Keep it to thirty minutes, one page and the same slot every week. If it grows into a reporting ritual, it will be the first thing cancelled when work gets busy.
Four questions, in this order
- What did we say we would do last week, and what actually happened?
- What is blocked, and who can unblock it?
- What is the one thing that, if it slipped, would hurt customers or cash?
- What are we deliberately not doing this week?
The fourth question matters most. A list of intentions is easy to write. A list of things you have agreed to leave alone is what protects the week.
Write the answers down
Use a single page, shared with whoever needs it. Date it. Keep the old pages. After a month, reading them in order shows which problems repeat, and repetition is the clearest sign that a decision was avoided rather than made.
Hold the line on scope
The review is not the place to solve problems. Name the problem, assign an owner and a date, and move on. If a topic needs more than five minutes, schedule it separately.
A review earns its place by ending in a decision.
Check the habit, not the tool
Teams spend weeks choosing software for this. A shared document is enough. The test is simple: could someone who missed the meeting read the page and know what changed? If so, the process works, whatever it is written in.
What if nothing happened this week? Say so in one line and stop. A short review in a quiet week is a sign the habit is healthy, not that it failed.