📊 Stakeholder Updates

Weekly Product Update Email for Execs (3-Bullet Format)

Drafts a crisp weekly exec update in a 3-bullet format (progress, risks, asks). Built for PMs whose leadership wants to know status in 60 seconds, not 60 minutes.

This prompt produces a weekly exec update in a 3-bullet format: progress this week, risks and blockers, explicit asks. The structure is modeled on the Amazon weekly update pattern used to keep exec reviews under 10 minutes.

When to use this prompt

Use this every week to turn your raw notes, sprint data, and customer signals into a short exec update. You will need a list of the week's shipped work, known risks, and any asks from leadership. The prompt enforces discipline: no more than 3 bullets per section, no corporate filler, and a clear ask. Execs will skim the update; the value is extreme concision. Do not use it for broad stakeholder broadcasts (those need more context); this format is specifically for the people who already have enough context and just need the delta.

The Prompt

Role: Product Manager Variables: {{week_context}}, {{shipped}}, {{risks}}, {{asks}}, {{metrics}}, {{week_identifier}}

You are a product manager writing a weekly update email for an executive audience. The email must fit in 3 sections (progress, risks, asks), each with a maximum of 3 bullets. The total length should be under 250 words.

Context for this week:
{{week_context}}
Shipped this week: {{shipped}}
Risks or blockers: {{risks}}
Current asks: {{asks}}
Key metrics movement: {{metrics}}

Produce the email in this exact format:

Subject: Product Update — {{week_identifier}}

Hi team,

**PROGRESS**
- Max 3 bullets. Lead each with the outcome, not the activity. Include a metric if one moved meaningfully. Use active verbs.

**RISKS**
- Max 3 bullets. Each should name the risk specifically and what you are doing about it. If there are no risks this week, write "None material this week." rather than padding.

**ASKS**
- Max 3 bullets. Each must be a specific request addressed to a named leader, with a deadline. If there are no asks, write "None this week."

[Signature]

Rules:
- No generic phrases like "we continue to make progress."
- No jargon unless execs already use it.
- No bullet should be longer than 2 lines.
- If a section has only 1 bullet, that is fine; do not pad.
- Every metric must include the current value and the direction.

Example Output

Subject: Product Update — Week of April 8

Hi team,

**PROGRESS**
- Invoice overdue sort launched to 5 beta customers; 3 already report 40 percent time savings on morning reconciliation.
- Bulk invite CSV import shipped behind flag; internal dogfood starts Monday.
- NPS for billing admins up 4 points week over week (from 32 to 36).

**RISKS**
- Timezone computation bug found in beta affecting non-UTC accounts; patch scheduled for Wednesday, rollout paused until verified.
- Dependency on auth refactor at risk of slipping 1 sprint, could push bulk invite GA to early May.

**ASKS**
- Priya: need legal sign-off on invoice disclaimer copy by Thursday to unblock Stage 2 rollout.
- Dan: can you confirm whether we can send the beta customer email in the CEO's name this week?

— [Name]

Recommended Tools

Google Workspace (Gmail) is the most common exec-update delivery channel, and the prompt output pastes cleanly into a compose window. Notion projects keeps a persistent log of weekly updates for future reference and retrospectives. Linear generates many of the data points (shipped this week, current risks) via its weekly review exports. Use Linear to gather the data, Notion to log it, and Google Workspace to deliver it.

Google Workspace73/100 Notion Projects76/100 Linear74/100

Frequently Asked Questions

When should I use this prompt?

Use it every week at the same time (Friday afternoon or Monday morning) so execs expect the rhythm. Consistency matters more than content; a predictable update that always arrives builds trust faster than occasional long reports. Do not use it for major launches or milestones; those deserve their own announcement with more context. Also skip it during weeks where there is genuinely nothing to report; a 'nothing material this week' update is better than fake progress, but do not send one every week or the rhythm loses signal value.

What if my exec wants more detail?

Offer a 1:1 follow-up rather than expanding the email format. The 3-bullet structure is valuable precisely because it is constrained; if you let it grow, you lose the discipline that makes it useful. If an exec frequently asks for more detail, either their needs do not match this format (they probably want a dashboard instead) or the bullets are too vague and need to be sharper. Most 'more detail' requests are actually a signal that the current bullets are not specific enough, not that the format needs to expand.