The Signal #5: You didn't lose the project because the plan was wrong. You lost it because someone who mattered didn't know what was happening.
Sending the same status report to every stakeholder group is a communication failure - not a time-saving shortcut. Your executive needs decisions and risks. Your client needs milestones and outcomes. Your team needs blockers and owners. One report can’t serve all four, and most of them aren’t reading the parts that matter to them anyway.
Your executive sponsor skims it in 30 seconds and misses the escalation on page two. Your client reads the internal jargon and emails you for a translation. Your team lead ignores the governance section - nothing in it affects their sprint. The steering committee chair asks for a decision summary they can review in the car.
Four audiences. One report. Four failures.
The Signal
Stakeholder communication isn’t a formatting problem. It’s a translation problem. Every stakeholder needs a different version of the truth - not a different truth, but a different translation. Different detail level. Different framing. Different action focus.
An executive needs decisions and risks. A client needs milestones and outcomes. A team needs blockers and owners. A governance board needs pre-reads and recommendations.
Most PMs know this. The reason they send one report to everyone isn’t ignorance - it’s time. Writing four versions of the same update is four times the work. The report cycle already takes too long. Nobody has capacity for audience-specific communication on top of everything else.
This is where AI fits cleanly. Not as a writer, but as a translator. One body of project data in. Audience-adapted communications out. Same facts, different framing - calibrated for each reader’s decision context.
The Noise
“I send the same status report to everyone. They can read what’s relevant.”
They don’t. Research on executive communication consistently shows that senior stakeholders make decisions based on the first 30 seconds of any document they receive. If the escalation is on page two, it doesn’t exist. If the ask is buried in a paragraph about risk mitigations, it won’t be actioned.
One-size-fits-all reporting isn’t efficient. It’s a communication failure disguised as process.
The Tool
A prompt for translating your project status into an executive briefing. Paste this into Claude, Gemini, or ChatGPT, then add your project data.
You are a Senior PM Communication Specialist. I'm going to give you
project status data. Produce a 1-page executive briefing:
1. PROJECT RAG STATUS - Overall, Schedule, Budget, Scope, Resources
(one sentence each)
2. TOP 3 RISKS - executive-relevant only, with decision needed Y/N
3. DECISIONS REQUESTED - each with 2-sentence context and deadline
4. KEY MILESTONES - next 30 days
5. ONE THING TO KNOW - the single most important takeaway
Rules: Maximum 400 words. No jargon the exec wouldn't use. Every
section present even if "None this cycle." Tone: confident, concise,
professional.
[PASTE YOUR PROJECT DATA BELOW]Try it with your most recent status report. Compare the executive briefing output with what you actually sent to your sponsor. If they’re materially different, that gap is where communication failures live.
Yes, AI helped me to write this :)
Want the full set? The Stakeholder Communicator includes 5 free audience-specific prompts - executive briefing, client update, team summary, escalation email, and governance pre-read. Download the free pack at projectorpm.com.