Report the business constraint, what changed in the evidence, the decisions made, work shipped, blockers and the next review date. Keep vanity metrics in an appendix if needed. A weekly report should make it easy for the founder to approve a tradeoff or unblock a dependency.
Lead with the decision
Start with one line: “We are testing whether poor-fit traffic or weak offer clarity causes the demo gap.” Then state the latest evidence and what changed. The founder should be able to understand the judgment without opening five dashboards. This is different from the weekly marketing meeting, which is the forum where the team makes the decision; the report records and prepares it.
Use a five-part structure
Include current constraint, relevant signals, decisions made, work completed and help needed. Every decision should have an owner and review date. If the leader recommends shifting budget, state what will stop and what evidence would reverse the choice. A report that says only “content published, leads up” cannot explain whether the right buyers are moving.
Avoid false precision
Small weekly samples move noisily. Show counts and denominators, and distinguish a directional signal from a reliable trend. If a measure has a long lag, say when it can be judged. Do not invent a confidence claim because the board expects a number. Track definitions in the KPI scorecard so the weekly story remains comparable.
A bounded example
For a hypothetical B2B team: “Twelve demos came from the new page; three met our current fit rule. We will pause the broad keyword group and test a narrower use-case page. Sales will tag rejection reasons by Friday. Review after twenty more qualified visits.” That report makes an action possible without pretending twelve demos prove a durable pattern.
A fill-in weekly update
Use this structure in plain language: “Current constraint: __. New evidence this week: __, based on __ records. Decision made: __; we stopped or deferred __. Work shipped: __. Blocker requiring founder help: __ by __ date. Next evidence check: __.” The blanks force the leader to connect activity with judgment. Link the underlying dashboard or work log for anyone who needs detail, but keep the main report readable in one pass.
Check the report against two questions. Could a founder approve or challenge the next move from it? Could a team member understand why their work changed? If not, add the missing definition or decision, not more charts. For slower measures, use a cohort note such as “not yet mature” and state the expected review week. A weekly update may be short precisely because the business result has not changed; it should not manufacture a new insight every Friday to appear productive.
Frequently asked questions
How long should a weekly CMO report be?
As short as needed to show the current constraint, evidence, decisions and blockers. Detail can live in linked dashboards or work logs.
Should every metric appear every week?
No. Show the few measures that can change a current decision, with definitions and context. Slow-moving outcomes can be reviewed monthly or by cohort.
Do weekly updates list tasks but leave you unsure what to decide?
Bring a recent report and the questions you still had after reading it. We can make reporting serve decisions rather than activity tracking.
Talk through the problem ↗See how we could work together
