The Stakeholder Read.

Each person you brief reads documents differently. Build prompt variants once, get pre-tuned outputs forever.

The hidden re-explaining tax

Every time you brief your finance leader, you mentally retune. Lead with dollars. Skip the platform language. End with risk-adjusted asks.

Every time you brief your operations leader, you retune again. Three bullets. No preamble. Timelines first.

You do this a dozen times a week. It's invisible work — nobody sees you tune the dial — but it's a tax. And it's the part of your job that compounds best with Claude, because tuning is exactly what prompts encode.

A Stakeholder Read is a saved prompt variant for one named person. You build it once. Then every brief for that person uses it.

What a Stakeholder Read looks like

Three components. Short.

Priorities — what this person cares about.
Anti-priorities — what to leave out.
Output shape — length, format, opener style.

Example: Operations leader.

When generating output for [name — operations leader]: - Priorities: timeline impact, dependencies, what's blocking, what unblocks it. - Anti-priorities: revenue projections, board framing, customer sentiment. - Output shape: 3 bullets, no preamble, no closer. First bullet is the headline; second is the constraint; third is the ask.

Example: Finance leader.

When generating output for [name — finance leader]: - Priorities: dollar impact, risk-adjusted views, contractual exposure, working-capital effects. - Anti-priorities: technical implementation detail, internal politics, anything "directional" without numbers. - Output shape: single paragraph (max 5 sentences) followed by a 3-row table — Cost / Risk / Recommendation. End with the dollar amount or percentage in bold.

Example: Board-level.

When generating output for [board / executive sponsor]: - Priorities: strategic implications, regulatory or reputational risk, decisions requiring board approval. - Anti-priorities: operational detail, named individuals below VP level, anything that doesn't survive a 60-second skim. - Output shape: 8-word title + 3 bullets + 1 footnote. Markdown.

Replace these examples with your actual three stakeholders. The shape is what matters — Priorities, Anti-priorities, Output shape — not these specific titles.

These are templates, not prompts you run alone. They get plugged into the Reshape Prompt from yesterday.

Saving Reads in the Vault

Open the stakeholder roster you built on Day 2. The Reads turn each entry into a saved prompt variant.

Inside your Status Vault, create a single document — markdown, Notion, Google Doc, whatever you prefer. The format doesn't matter, the content does. Name it something like "Stakeholder Reads" and drop each Read into it as a section. Upload it to the Project.

Now your Reshape Prompt gets simpler. Yesterday it was:

Reshape the attached document for [audience]. Their priorities are [...]. Their tolerance for technical detail is [...]. Output as [...]. End with [...].

Today it becomes:

Reshape the attached document using the [name] Read from the Project context.

Claude pulls the priorities, anti-priorities, and output shape from the Read you saved. The reshape happens in one short prompt.

Stuck? If Claude doesn't reference the Read automatically, paste the Read text directly into the prompt. Same result, slightly more typing.

That's the compounding move. You stopped retuning the dial. The Vault tunes it.

Today's exercise (15 minutes)

Step 1. List the three people you brief most often. Names, not just titles.

Step 2. Build a Stakeholder Read for each one. Use the template:

Priorities: 3-5 things they care about.
Anti-priorities: 2-3 things they don't read.
Output shape: format, length, opener style.

Step 3. Save them in a single document and upload it to the Status Vault.

Step 4. Test it. Take a recent brief. Run:

Reshape the attached brief using the [name] Read from the Project context.

Three Reads. One test. You'll know within 30 seconds whether the output landed.

What changes after Reads exist

Before: every brief you write requires a mental tuning step. Each stakeholder, each time. The tuning is in your head and disappears the moment you log off.

After: the tuning lives in the Vault. Six months from now, you open the same Vault and the Reads are still there — sharper, because they've been refined every time a stakeholder pushed back on an output.

Reads are the asset that compounds the hardest. The Decision Frame is a prompt anyone can copy. Your Reads are calibrated to your stakeholders. Nobody else has them.

Why this matters

Most "prompt engineering" advice treats prompts as universal. They're not. The best prompts in an analyst's toolkit are local — calibrated to specific people in a specific org.

Stakeholder Reads are how you build a local prompt library. Three Reads on Day 4. Five by next month. Ten by next quarter, refined every week.

That's the thing no blog post will give you.

Tomorrow

Day 5 ties everything into a weekly rhythm. The four moves — synthesize, store context, reshape, build Reads — get scheduled into four short calendar slots. Under one hour of active Claude time per week.

Tomorrow you stop reacting and start running a system.

Analyst Track Progression

Your 5-day path to a weekly analyst rhythm.

Day 1 → Day 2 → Day 3 → Day 4 → Day 5