You Wrote One Report for Three Audiences. None of Them Read It.

It’s Tuesday morning. You spent the last hour of your Monday pulling data from Amplitude, grabbing screenshots from Figma, and summarizing JIRA tickets. You compiled it all into a crisp, comprehensive weekly update email. You hit send to the product team, your marketing stakeholders, and the VP of Product.

And then… nothing.

No replies. No thumbs-up emoji in Slack. When you ask your lead engineer a question later, it’s clear they never opened it. Your report vanished into the ether, just like last week’s.

You didn’t write a bad report. You wrote an impossible one. You tried to create a single document that would satisfy an executive, a cross-functional partner, and your core team. By trying to speak to everyone, you ended up speaking to no one.

One Document, Three Different Jobs

A single status update is pulled in three directions by three different readers with completely different needs.

• The Executive: Has 60 seconds, probably on their phone between meetings. They want to know if you’re winning or losing. They scan for two things: high-level impact on business goals (revenue, retention, cost) and critical blockers they need to clear. They do not care about which specific tickets were closed.
• The Stakeholder: Has five minutes. This is your counterpart in marketing, sales, or support. They need to know how your work affects their work. They’re looking for timelines, launch dates, changes in scope, and dependencies. They need to know if they need to prepare a campaign or train their team.
• The Core Team: Lives in the details with you. They want to see the direct output of their work and understand the immediate next steps. They need links to PRDs, design files, and key decisions. They’re looking for clarity on priorities and confirmation that everyone is on the same page.

Your single, monolithic report failed because it forced the executive to wade through technical details, forced the engineer to skim past GTM strategy, and buried the launch date your marketing partner needed.

Build a Tiered Report, Not a Monolith

Stop writing a single narrative. Start building a single document with three distinct, audience-specific layers