Status Updates, Strategy Memos and Exec Briefs

Three writing tasks dominate the calendar of any middle manager: weekly status updates, longer-form strategy memos, and executive briefs. Together they consume four to eight hours a week. With the right prompts and process, you cut that to one or two — and your writing actually gets sharper, not softer.

This lesson gives you four copy-paste prompts plus a manager review checklist. Use them this week.

What You'll Learn

• The "raw notes in, polished doc out" workflow
• A copy-paste prompt for weekly status updates
• A copy-paste prompt for strategy memos and decision documents
• A copy-paste prompt for exec briefs (one-pagers)
• A manager review checklist for AI-drafted writing
• How to keep your voice instead of sounding like ChatGPT

The Core Workflow: Raw Notes In, Polished Doc Out

The single biggest mindset shift for managers using AI for writing: stop trying to "write a prompt that produces the document." Instead, dump raw notes — bullet points, fragments, half-sentences, decisions, numbers — and let the AI structure them into the document format you want.

Your raw notes are the asset. The AI is the formatter, not the thinker.

This matters because:

• AI cannot invent the substance. The substance is what you know.
• Raw notes preserve your context, your numbers, your judgment.
• The output sounds like you if you fed it your raw thinking.

A typical raw-notes input for a weekly status update looks like this:

- Shipped reliability work — error rate down 38% week over week (Tues)
- Hiring: 2 final-round candidates on Sr SRE, both strong; need decision by Fri on offer
- Data team migration: stuck. Lila waiting on InfraSec for cloud account; we'll lose week 3 of timeline if not unblocked Mon
- Q3 OKR: still tracking green on reliability, yellow on platform migration
- Concern: morale dip on data team after Lila's offer rejection; 1:1s scheduled this week
- Decision needed from VP: 2x Sr SRE offers approved? Recommend yes, both.
- Skipping: minor infra paper cuts (not exec-level)

That is five minutes of typing. The prompts below turn that into a polished status update, exec brief, or memo.

Prompt 1: Weekly Status Update

You are an experienced senior engineering manager writing a weekly status update for your VP. She reads on her phone Monday morning in under 90 seconds. Her current focus is shipping reliability work and unblocking the data team.

Using my raw notes below, write a status update with this exact structure:

1. Headline — one sentence, ends in a verb, captures the most important thing this week.
2. Wins — up to 3 bullets. Each starts with a past-tense verb and includes a quantified outcome if available.
3. Risks — up to 2 bullets. Each names the risk, the owner, and the one concrete next step.
4. Decisions needed — bullet each decision with deadline, owner, and the option I recommend.
5. Nothing else.

Constraints:

• No filler ("happy to share," "wanted to flag," "as you may know")
• No buzzwords ("leverage," "synergy," "circle back," "low-hanging fruit")
• No exclamation marks
• No emoji unless I included one
• If a required field is missing from my notes (e.g., no quantified outcome on a win), ask me before drafting

Raw notes: [paste]

This single prompt, used weekly, saves most managers 60+ minutes a week. Over a year that is 50+ hours.

Prompt 2: Strategy Memo / Decision Document

For longer documents — strategy memos, decision docs, pre-mortems — the structure is different. You want clear logic, a recommendation, and a defensible "why."

You are a senior chief of staff writing a strategy memo for an executive audience. The reader has 5-7 minutes and wants to understand a recommendation and the reasoning behind it.

Using my raw notes below, draft a memo with this exact structure:

1. Recommendation (2-3 sentences). State the recommendation up front. The reader should be able to stop here and act.

2. Why this matters now (1 short paragraph). What is the deadline, opportunity, or risk that makes this timely?

3. The options we considered (a numbered list, 2-4 options). For each option, one sentence describing it, then a one-line "Why this works" and a one-line "Why we rejected it" (except for the recommended option, which gets "Why we chose it").

4. The case for the recommendation (3-5 bullets). The strongest reasons, with quantified evidence where possible.

5. The strongest counter-argument we considered (1 paragraph). What is the best objection? How would we respond?

6. What we need from you (a bulleted list). Decisions, approvals, or unblockers required. Each with an owner and a deadline.

7. Appendix (optional). Detail only — assumptions, math, references.

Constraints:

• Total length: 600-900 words excluding appendix
• Active voice, present tense where possible
• Do not invent numbers; if data is missing from my notes, mark "[missing data]" inline
• No hedging phrases ("it could be argued," "some might say")

Raw notes: [paste]

A good strategy memo prompt is the single biggest writing-time saver of the role. The output is also more rigorous than what most managers produce under deadline pressure — because the prompt forces you to consider counter-arguments and alternatives.

Prompt 3: Executive One-Pager

The exec brief is its own genre. Executives skim. Make every sentence earn its place.

You are writing a one-page executive brief for a busy senior leader. She will read it in 60 seconds and make one decision.

Using my raw notes below, write the brief in this exact structure on ONE page:

• TL;DR (2 sentences). What you need her to do, in plain language.
• Context (3 bullets). Where we are. What changed. What is at stake.
• The decision (one sentence + 2 options). The decision needed, followed by Option A and Option B, each one sentence.
• My recommendation (2-3 sentences). Which option and why.
• What happens next (3 bullets). What you'll do once she decides.

Constraints:

• Maximum 250 words total
• No introduction, no warm-up, no closing pleasantries
• Numbers, owners, and deadlines are mandatory; do not omit them

Raw notes: [paste]

If the AI tries to write more than 250 words, send it back: "Cut to 250 words. Remove anything not load-bearing."

The Manager Review Checklist

Never send AI-drafted writing without running this checklist. It takes 90 seconds.

1. Substance check. Is every claim in the draft something I would say in person? Mark anything that feels like AI invented it or stretched it. Cut or correct.

2. Numbers check. Are all numbers correct? AI confidently produces plausible-but-wrong numbers. Verify every figure against your raw notes.

3. Names check. Are people's names spelled right? Did the AI assign work or credit to the wrong person? AI sometimes shuffles attributions.

4. Tone check. Read the draft out loud. Does it sound like you? Common AI tells to remove:

• "It's important to note that..."
• "Whether you are X or Y..."
• "In today's fast-paced..."
• "We are excited to..."
• Three-bullet lists where two would do
• Excessive parallel structure

5. Cut check. Is there a sentence I can delete without losing meaning? Cut it. Repeat. Most AI drafts get 15-25% shorter and 30% better with this single pass.

6. Decision check. Does the reader know what to do next? If not, add it.

The checklist is the difference between "AI-drafted slop" and "writing my exec actually wants to read."

How to Keep Your Voice

A common manager fear: "If I use AI for my writing, I'll start sounding like everyone else."

Three habits that protect your voice:

1. Always start from raw notes, not from a blank "write a memo about X." The AI cannot copy your voice if you do not give it your voice as input.

2. Build a voice prompt. Add one paragraph to every prompt that describes your writing style: "I write in short sentences. I use active voice. I prefer concrete nouns over abstract ones. I never use the word 'leverage' as a verb. I open with the answer, not the setup."

3. Hand-edit the final 10%. The opening line. The closing line. The one sentence in the middle that carries the key idea. Hand-write those. The AI handles the connective tissue. The voice lives in the load-bearing sentences.

The 5-Minute-a-Week Habit

Pick one writing task you do every week. Build the PROMPT-shaped prompt for it. Add it to your team's prompt library. From then on, the workflow is: dump raw notes (5 minutes), run the prompt (30 seconds), run the review checklist (90 seconds). You just got a 60-minute weekly task down to 7 minutes.

Do this for your top three weekly writing tasks. You will reclaim a half day a week.

Key Takeaways

• The "raw notes in, polished doc out" workflow is the core manager-writing pattern
• Three core prompts cover most weekly writing: status update, strategy memo, exec one-pager
• Always run the six-point manager review checklist before sending
• Protect your voice by starting from raw notes and adding a voice description to every prompt
• Hand-write the load-bearing sentences (open, close, key idea); let AI handle connective tissue
• Three good prompts plus the checklist save most managers four to eight hours per week