Fixing Reporting Workflows with Better Reader

The report lands at 6:47 p.m. Friday. By 9:15 Monday it's buried under forty-two unread emails, three calendar invites, and a Slack thread about the staging server. Nobody read it. Not because it was bad — because it was written for the person who wrote it, not the person who has to act on it.

A weekly report has one job: give your reader enough to make a decision or take an action without opening another tab. If it can't do that on a phone screen while someone waits for coffee, it failed.

Here's the structure I've landed on after years of writing reports that got skimmed, ignored, and occasionally — when I got it right — quoted back to me in a leadership meeting.

Lead with the decision, not the chronology

Most weekly reports read like a diary: Monday we did this, Tuesday we did that, Wednesday the thing broke, Thursday we fixed it. The reader has to reconstruct the point from the timeline. That's work you're offloading onto them.

Flip it. Open with the one thing that changed this week and what it means.

Bad opening:

This week the team continued work on the checkout redesign. We held three design reviews and completed the API integration.

Better opening:

Checkout redesign is one week behind. The payment provider's sandbox broke the integration test, and we're waiting on their fix. If it lands by Wednesday, we hold the launch date. If not, we slip to the 22nd.

The second version tells the reader what to worry about in four seconds. Everything after it is supporting evidence.

The five-block skeleton

I use the same five sections every week. You can copy this into a doc and never redesign it again.

1. Headline — one sentence: what's the state of the work?
2. Decisions needed — what you need from the reader, with a deadline.
3. What moved — the two or three things that actually progressed.
4. What's stuck — blockers, with the owner and the ask.
5. Next week — the two or three things you'll finish.

That's it. If a section has nothing in it, write "Nothing this week" and move on. An empty section is information too — it tells the reader you checked.

Make "decisions needed" impossible to miss

This is the section that earns the report its keep. Most weekly reports bury the ask in paragraph four of a status update, then wonder why nobody responded.

Put it at the top, name the person, and give a date.

Decision needed from Priya by Tuesday: Do we ship the billing fix behind a flag this week, or hold for the full regression suite? Holding costs us the enterprise pilot. Shipping behind the flag risks two known edge cases.

Notice what this does. It states the options, the cost of each, and who decides. Priya can reply "ship behind the flag" in one line. That's a report doing its job.

If you have no decisions needed, say so explicitly: "No decisions needed this week." Readers who scan for the ask will stop scanning once they trust that the section is always there.

Write for the reader who reads one line

Assume your reader will read the headline and nothing else. Then assume a second reader who reads the headline and the decisions. Then a third who reads everything. Your report has to work for all three.

That means the headline carries the weight. Test it: if someone read only that sentence, would they know whether to worry? If the answer is "not really," rewrite it.

"Progress on Q3 initiatives" — tells the reader nothing. "Q3 initiative 2 is at risk; the other two are on track" — tells them where to look.

Kill the status theater

The fastest way to make a weekly report useless is to fill it with activity instead of outcomes. "Held six stakeholder meetings" is not progress. "Got sign-off from legal on the data retention policy" is.

Before you write a line, ask: did this change anything a reader cares about? If not, it doesn't belong in the report. It belongs in your own notes.

This is also where AI tools earn their place. If you're already using an assistant to draft meeting notes or summarize a thread, paste the raw notes into your weekly report draft and ask it to pull out decisions and blockers. Then edit hard. The model will happily hand you a tidy list of activities — you have to strip it back to outcomes. Treat the AI output as a first pass, not a finished report.

A real example, filled in

Here's a complete weekly report from a fictional PM, start to finish. Steal the shape.

Headline: Search revamp is on track for the 15th. Two open decisions below.

Decisions needed

• From Marcus by Tuesday: Approve the new empty-state copy, or keep the current version for launch and revisit in v2. Approving now means a copy review Thursday.
• From Dana by Wednesday: Confirm whether the analytics event schema change ships with this release or the next one. Shipping now means a one-day delay; shipping later means we lose week-one funnel data.

What moved

• Search results page passed accessibility review — no blocking issues.
• Backend indexing job cut average query time from 340ms to 190ms.
• Design handed off all twelve screens; engineering started Monday.

What's stuck

• Localization for the German market is waiting on the vendor's glossary. Owner: me. Ask: vendor call Thursday, expect resolution by Friday.

Next week

• Ship the results page to staging.
• Close out the analytics decision and update the tracking plan.
• Run the first usability session on the new empty states.

That's roughly 180 words. It fits on a phone screen. It names two people, two deadlines, and one blocker with an owner. A reader can act on it in under two minutes.

The Monday-morning test

Before you hit send, run this check: imagine your reader opening this at 9 a.m. Monday with eleven other emails waiting. Can they find the decision they need to make in ten seconds? If not, the report isn't done.

The other test: does it survive being forwarded? If your manager forwards your report to their manager, does it still make sense without you in the room? If it depends on context only you have, add one line of it. A weekly report that travels well is worth ten that don't.

One habit that makes all of this easier

Keep a running draft all week. Every time something gets decided, unblocked, or stuck, drop one line into the doc. By Friday you're editing, not writing from scratch. The report takes ten minutes instead of an hour, and it's better — because it's built from what actually happened, not what you can remember at 6:47 p.m.

That's the whole method. Lead with the decision. Name who needs to act. Cut the activity. Write it for the person who reads one line. Then send it and go home.