The Operator's Guide to Disciplined Weekly Reporting
Most weekly reports are theatre. They summarize what already happened, dress up the numbers, and consume an hour of the leadership team's attention without changing anyone's decisions. Worse, they create the illusion of accountability without the discipline of it.
The format that works is small, structured, and built around the questions a leadership team is actually asking. It takes thirty minutes to produce and ten minutes to read. Here is the shape.
Three Sections, No More
Numbers. Five to seven indicators, one line each, with the prior week for comparison. The point is not to chase completeness. Pick the indicators that, if they moved sharply in either direction, would force a meeting.
Revenue, gross margin, net new customers, top-of-funnel conversion, and one operational metric that varies by business — uptime for SaaS, repeat purchase rate for consumer, on-time delivery for physical goods. Everything else either doesn't move weekly or doesn't change decisions.
What changed since last week. Two or three sentences per item, maximum three items. This is where the format forces honesty: "we expected the Acme renewal to land Tuesday, it didn't, follow-up is in progress" tells you more than "renewals progressing on plan." Resist the temptation to soften what went wrong.
What we're deciding this week. Three to five open questions the leadership team should resolve. Not status. Not narrative. Questions like "do we extend the enterprise pilot one more week or convert them at the current terms?" and "do we escalate the integration delay now or wait for the Friday code freeze?"
A weekly report that contains three unanswered questions is more valuable than one that contains twenty answered ones.
What to Cut
Cut executive narrative — a paragraph summarizing the state of the business in prose. If your numbers need a paragraph to interpret them, the numbers are wrong.
Cut trend charts unless they answer a specific question. A line chart with a flat twelve-week trajectory tells no story. A line chart that breaks the trend in the most recent week tells the story you should be writing about, not charting.
Cut sections that summarize meetings. If a meeting's outcome doesn't change numbers or decisions, it doesn't belong in the weekly report. Notes from those meetings belong in the meeting's own documentation — not here.
What to Add
Add a single "lead measure" per team. A lead measure is the activity that, if it happens, predicts the lag measure lands later. Sales demos booked predicts revenue closed. Production runs shipped predicts on-time delivery. Customer success touchpoints completed predicts renewal rate.
When the lead measure drops, the lag measure is going to drop in three to six weeks. The weekly report is supposed to catch that before it becomes a problem, not after.
The Reading Time
A weekly report should take ten minutes to read. If it takes longer, the format is wrong. The point of weekly reporting is not exhaustive coverage — it's decision support. Ten minutes is the budget the format has. If the format exceeds it, leadership will skim instead of read, and skimming produces skimming-shaped decisions.
Invest the time in the questions section. That's the only part guaranteed to change behavior.
The Discipline
The discipline is showing up even when the news is bad. The week a major renewal doesn't close is the week the report matters most. Skipping it because "we're still working it" is the moment the report loses its value. The point of weekly reporting is to surface issues while they're still addressable, not after they have already cascaded.
Start Monday morning with the numbers, finish Tuesday afternoon with the questions, distribute Wednesday. Once the cadence is established, the discipline becomes its own diagnostic — if the report slips a week, the business is telling you something before the numbers are.