Engineering says "the API is non-deterministic under load." The finance leader needs the dollar version. The board needs the one-line version. Same insight. Three audiences. Three formats. One prompt pattern.
Pin this. You'll use it every day.
| Format | When to use it | Output shape |
|---|---|---|
| Executive summary | Decision needed from a single exec | 3-5 sentences, lead with the decision, end with recommended action |
| Slack-ready update | Cross-team awareness, low-stakes | One short paragraph + bullet list of next steps, no formal opener |
| Board slide | Standing board agenda or escalation | 8-word title, three bullets, one footnote with the key data point |
| Email update | Async stakeholder, async response | Subject line, 2-paragraph body, clear ask or "no action needed" closer |
| All-hands talking points | Verbal delivery, mixed audience | 30-second plain-spoken script, end with one sentence the speaker can repeat verbatim if they freeze |
These five drop into the Reshape Prompt's [format] slot — the prompt that handles both audience and format in one move.
Most analyst work isn't producing one brief. It's reshaping the same insight for different rooms.
You sit between rooms. Engineering, finance, legal, ops, leadership — each speaks a different language. The data is the same. The framing has to change. So does the format. The finance leader wants a paragraph; the board wants a slide; Slack wants three lines.
The reshaping job has two knobs: audience and format. Most prompts only turn one. The good prompt turns both.
A 6-page incident report on a database outage.
Replication lag exceeded 30s during the 14:22 traffic spike. Failover triggered but secondary replica was 18 minutes behind. Root cause: missed alarm threshold in the previous deploy. Action item: re-baseline replication alarms in next sprint.
47-minute outage on May 1. Estimated revenue impact: $128K. Refund credits issued: $34K. No contractual SLA breach. No finance action needed unless Q2 churn spikes.
Customer-visible outage tied to a monitoring gap, not a platform failure. Process fix is in production. No further board action required.
Same incident. Three audiences. Three formats. One source.
Copy this. It handles both knobs.
Example with variables filled in:
Plug in the variables. Run it. ~30 seconds per audience.
Pull a brief you've already written this quarter. Don't write a new one — use existing source material.
Inside the Status Vault, run the Reshape Prompt once:
Compare the output to the original brief.
You'll notice two things: the audience reshape changes what's emphasized; the format reshape changes what shape it takes. Both knobs, independently controllable.
The reshaping job is undervalued because it's invisible. When you do it well, every team feels like the data was written for them. When you do it badly, leadership thinks engineering is hiding things and engineering thinks leadership doesn't get it.
You're already doing this work in your head. The Reshape Prompt makes it repeatable — and the Vault makes it instant.
Day 4 takes the reshaping idea one step further. Right now you're reshaping per-document. Tomorrow you'll build Stakeholder Reads — saved prompt variants for each named person you brief regularly. Build them once, use them every week.
Tomorrow you stop tuning the audience knob. The Vault tunes it for you.