←Back to Blog
Deep Insights| 2026-11-13

How PM Teams Can Improve Three Outcomes

David Sterling
Staff Writer
How PM Teams Can Improve Three Outcomes

The report sat in her inbox for two days. I know because I checked the read receipt, which is a small humiliation I recommend to anyone who wants to learn how little of their writing gets consumed.

It was a good report. Thorough. Fourteen bullets covering everything the platform team touched that week. And it lost to a Slack thread about a broken build, because the Slack thread had a subject line and the report had a wall.

Here's the fix I've used since: write the report so the first three lines answer the only question your manager has at 11:40 on a Friday. Everything below that is for the person who forwards it.

Lead with the decision, not the chronology

Most weekly reports are written in the order work happened. That's the order that matters to you and the least useful order for anyone else.

Flip it. Open with what changed that requires a human to do something, or what you now know that you didn't know Monday. A reader who stops after line three should still be able to act.

Weak opening:

This week the team continued work on the onboarding flow, held three planning sessions, and made progress on the API migration.

That sentence is technically true and tells the reader nothing. Compare:

Onboarding redesign is now two weeks behind because the design review slipped. Decision needed by Wednesday: ship the current version to 10% of users, or hold until the full flow is ready.

Same week. Same facts. One version gets a reply in an hour.

The four-block structure that survives forwarding

I've settled on four blocks, in this order. They fit on one screen and they answer the questions a reader asks in sequence.

1. The headline. Two sentences. What's the state of the work and what do you need. If nothing is needed, say "no decisions needed this week" — that's information too.

2. What moved. Three to five bullets, each one a change in state, not an activity. "Shipped the export endpoint to production" beats "worked on export endpoint." If you can't tell whether something moved, it didn't.

3. What's stuck. Name the blocker, name the owner, name the date you need it cleared. Vague blockers ("waiting on legal") are how reports become decoration. "Waiting on legal review of the DPA, Priya has it, need it by Thursday or the launch slips a week" is a request.

4. What's next. Three bullets max. This is where you show you've thought past Friday, and it's the section your boss will quote back to their boss.

That's it. No appendix unless someone asked for one. If they want the detail, they'll ask, and then you send the fourteen bullets as a separate doc — which is the right home for them.

Write the subject line like it's the whole report

Your report competes with forty other things in a queue. The subject line is the only part guaranteed to be read.

Bad: Weekly Report — Platform Team — Week of March 3 Better: Platform: onboarding slips 2 weeks, decision needed Wed

The second one gets opened because it contains a fact and a deadline. It also survives being forwarded to someone who never opens attachments, which is most of them.

One caution: don't manufacture urgency to get opens. If every week is a crisis, readers learn to ignore the format. Reserve the alarm for weeks that deserve it.

The 20-minute drafting ritual

The reason weekly reports are bad is that they're written from memory on Friday afternoon, which is the worst possible narrator. I write mine in three passes across the week instead.

  • Monday, 2 minutes. Start the draft with the four headers and one line under each: what you expect to move this week.
  • Wednesday, 5 minutes. Update the "what's stuck" block. This is the one that rots fastest and matters most.
  • Friday, 15 minutes. Rewrite the headline last, after you know what the week actually was. Read only the first three lines and ask whether you'd act on them.

The Wednesday pass is the one people skip and the one that pays. Blockers caught Wednesday can still be cleared by Friday. Blockers surfaced Friday become next week's problem, and next week's report.

What to cut

Three things make weekly reports unreadable, and all three are easy to remove:

Status words with no content. "On track" and "in progress" are placeholders. If something is on track, say what's true about it. If it's in progress, say what's done.

Percentage complete. Nobody believes it, including you. Report milestones reached and the next one due.

Narrative of effort. Hours, meetings, calls, "lots of alignment." Your reader wants to know what's different now. Effort is not a state change.

The test that matters

Before you send, read only your headline and your "what's stuck" block. If a reader who stopped there would still know whether to worry and what to do, you're done. If they'd have to scroll to find out, you've written a diary, not a report.

The read receipt is optional. The rewrite isn't.

Generated by Reportify AI — Automate your team's status reports, standups, and weekly updates. Try free →

Stop Drowning in Reports

Turn your scattered meeting notes into executive-ready PPTs and Word docs in 30 seconds.

Get the App