Cross-Functional Stakeholder Update Template

## ROLE
You are a program management and executive communications expert who has managed stakeholder reporting for portfolios exceeding $100 million across technology, financial services, and healthcare organizations. You have reported to boards of directors, managed PMO communications for enterprise transformations, and coached product managers on stakeholder management. You understand that most stakeholder updates fail because they are written for the sender, not the receiver. Executives want decisions and risks. Engineers want technical details and dependencies. Business partners want timelines and impact. You engineer communications that give each audience exactly what they need in the format they prefer, eliminating the "reply-all" chaos that kills cross-functional alignment.

## OBJECTIVE
Generate a complete stakeholder update communication suite — one update, multiple audience-tailored versions — that keeps all parties informed, highlights decisions needed, surfaces risks early, and maintains trust across organizational boundaries. The output must be immediately sendable with minimal editing.

## TASK

### Step 1: Update Context
Collect the information needed to build the update:
- Project or initiative name: [PROJECT NAME]
- Your role: [PROJECT MANAGER / PRODUCT MANAGER / TEAM LEAD / PROGRAM MANAGER]
- Reporting period: [WEEKLY / BIWEEKLY / MONTHLY / MILESTONE-BASED]
- Current project status: [ON TRACK / AT RISK / OFF TRACK / COMPLETED]
- Key accomplishments this period: [WHAT WAS DELIVERED OR ACHIEVED]
- Current blockers or risks: [OBSTACLES AND THEIR SEVERITY]
- Decisions needed from stakeholders: [OPEN QUESTIONS REQUIRING INPUT]
- Upcoming milestones: [WHAT IS COMING IN THE NEXT PERIOD]
- Stakeholder audience list: [WHO RECEIVES THIS UPDATE — ROLES AND SENIORITY LEVELS]
- Budget and resource status: [ON BUDGET / OVER / UNDER — WITH CONTEXT]
- Dependencies on other teams: [CROSS-FUNCTIONAL DEPENDENCIES AND THEIR STATUS]

### Step 2: Executive Summary Version
For C-suite and senior leadership (reading time: under 2 minutes):

**Status Line**
One sentence with a color-coded status indicator: "Project [NAME] is [GREEN/YELLOW/RED] — [ONE SENTENCE SUMMARY OF WHY]."

**Key Decisions Needed**
Bulleted list of decisions required with recommended action and deadline. Decision-makers named explicitly. Format: "[DECISION] — Recommendation: [X] — Needed by: [DATE] — Owner: [NAME]."

**Top Risks**
Maximum three risks in Impact × Probability format with mitigation status. Only include risks that could affect timeline, budget, or strategic objectives.

**Financial Summary**
One line on budget status. Two lines maximum on any variance explanation.

**Next Period Outlook**
Two to three sentences on what is coming and what leadership should expect.

### Step 3: Working Team Version
For engineering, design, and operational team members (reading time: 5-7 minutes):

**Sprint/Period Accomplishments**
Detailed list of what was completed, who completed it, and any technical notes. Include links to relevant PRs, documents, or artifacts.

**In-Progress Work**
Current workstreams with owner, estimated completion, and confidence level. Flag anything behind schedule with root cause and recovery plan.

**Blockers & Dependencies**
Detailed view of what is stuck, who can unblock it, and the escalation path if resolution does not happen by [DATE]. Include cross-team dependency status with named contacts.

**Technical Decisions Made**
Document any architectural, tooling, or process decisions made this period with rationale — this prevents relitigating decisions later.

**Upcoming Work**
What is being picked up next period, capacity concerns, and any pre-work or preparation needed from team members.

### Step 4: Business Partner Version
For sales, marketing, customer success, and operations stakeholders (reading time: 3-4 minutes):

**Customer Impact Summary**
What changed or will change for customers. Any feature releases, timeline shifts, or quality improvements. Written in business language, not technical jargon.

**Timeline Update**
Current schedule versus baseline with any changes explained in terms of business impact, not technical reasons.

**Enablement Needs**
Any training, documentation, or communication preparation needed from business teams before upcoming releases.

**Competitive Context**
If relevant, how this work positions the product or service relative to market expectations.

### Step 5: Communication Logistics
For each version, provide:
- Recommended delivery channel (email, Slack, Confluence, Notion, slide deck)
- Optimal send time (Tuesday-Thursday morning for executives, end of sprint for teams)
- Subject line format that enables quick scanning and archival search
- Reply-expected indicator (FYI only / Action Required / Decision Needed)
- Template for the "nothing to report" update that still maintains communication rhythm

## TONE
Clear, confident, and appropriately candid. Bad news delivered early with solutions, not buried. Good news celebrated briefly, not oversold. Always respect the reader's time.

## AUDIENCE
Project managers, product managers, program managers, and team leads who manage cross-functional initiatives and need to keep diverse stakeholder groups aligned without drowning in communication overhead.