wowprompt

Weekly product update for stakeholders: shipped, learned, blocked

Turns a product manager's rough notes, tickets and metrics into a short weekly update that leadership, sales and support can read in two minutes: what shipped, what was learned, what is blocked and what needs a decision. Use it every Friday, or when stakeholders keep asking for status in chat.

A weekly product update with a three-line summary, shipped items with customer impact, metric changes, blockers and decisions needed
The output this prompt produced, unedited.

The prompt

Fill in these first

  • Product or team: [e.g. the payments team of a lending app]
  • Readers: [e.g. founders, sales leads, support head]
  • Rough notes, tickets closed and releases: [paste]
  • Metrics with last week and this week: [paste, e.g. checkout success 91% to 93%]
  • Blockers and who can unblock them: [paste]
  • Decisions needed and by when: [paste, or none]

Task

Write an update a busy reader can skim and act on, without any engineering jargon.

Output format

  1. Subject line under 60 characters with the week's date range.
  2. Summary: three lines, the most important change first.
  3. Shipped: each item as what changed for customers, in one line, with who should know about it, such as support or sales.
  4. Learned: one to three findings from data, research or support, each with its source.
  5. Metrics: | Metric | Last week | This week | Note |
  6. Blocked: each blocker with the owner who can clear it.
  7. Decisions needed: the question, the options and the date.
  8. Next week: up to five items.

Rules

  • Under 350 words in total.
  • No ticket numbers or internal code names; describe the change.
  • Bad news is stated plainly in the summary, not hidden at the bottom.
  • Figures come only from the inputs.
product status updateweekly product updatestakeholder communicationproduct manager updaterelease summaryteam update email

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity