Internal Newsletter Prompts That Don't Read Like AI Wrote Them

Internal newsletters die for three reasons:

One, nobody reads them because they're all the same shape. Two, they're written by HR or comms in a voice nobody trusts. Three, when AI gets involved it sounds like AI.

These prompts solve all three.

The structure that works

The internal newsletters people actually read share a structure: - One specific thing they need to know - One specific number that changed - One person doing something interesting - One thing that's going to happen they should pay attention to - One opinionated take from a leader

Not seven topics. Not seventeen bullets. Five specific items.

Prompt 1: The weekly business update

``` Draft a weekly internal newsletter for a {SIZE}-person company.

Input data: - Key metrics that changed this week: {METRICS} - One initiative making progress: {INITIATIVE} - One person to highlight (with what they did): {PERSON} - One thing happening next week the team should care about: {UPCOMING} - One opinionated message from leadership: {LEADER_TAKE}

Voice: the way the CEO actually talks. Reference style: {2-3 SAMPLES_OF_CEO_WRITING}

Length: 350-450 words total. NOT 600. NOT 200.

Format: - Subject line that's a specific claim, not a topic - Open with the highlighted person (not a generic intro) - Then the metric - Then the initiative - Then upcoming - Close with the leader take

Banned phrases: "team", "everyone", "we are excited to", "we are proud to", "as always", "going forward", "moving the needle", "synergy", "leverage", "robust", "seamless".

Mention specific names. Mention specific numbers. Avoid abstractions. ```

The "specific claim" subject line is half the battle. Open rates triple when subject lines are specific.

Prompt 2: The product/release update

``` Draft a release-notes-style internal update for a product team.

What shipped: {LIST_WITH_OWNERS} What's known to be broken: {KNOWN_ISSUES} Customer feedback this week: {FEEDBACK_NOTES} Next week's planned shipments: {NEXT_PLAN}

Voice: matter-of-fact, no marketing energy. Engineers and PMs hate marketing energy in internal comms.

Length: 250-350 words.

Format: - "Shipped this week" section (3-7 items, with owner credit) - "Known issues" section (be honest about what's broken) - "What customers said" section (one quote, one paraphrased pattern) - "Next week" section (3-5 specific shipments)

Banned: "we're excited to announce", "we have launched", "we are proud", "team", "industry-leading". No hype. Just what shipped. ```

The "known issues" section is the trust builder. Newsletters that hide what's broken get ignored.

Prompt 3: The all-hands recap

``` Draft a recap email after an all-hands meeting.

Transcript or notes from the all-hands: {NOTES} The CEO's top 3 messages: {KEY_MESSAGES} Questions asked by employees: {Q_AND_A} Any decisions announced: {DECISIONS}

Voice: factual, slightly informal, the way a smart employee would summarize for a colleague who missed the call.

Length: 300-400 words.

Format: - Open with the most important decision or message (not the agenda) - Then a 3-bullet "what was said" section - Then a Q&A section (3-5 questions with concise answers) - Close with a "what to expect next" sentence

Banned: meeting-speak ("the team had a productive discussion"), corporate fluff, vague references ("we discussed several initiatives"). Be specific. ```

The "most important decision first" rule is the entire pattern. Most all-hands recaps bury the lede.

Prompt 4: The Friday wrap

``` Draft a Friday wrap-up newsletter for a small team.

What got done this week: {WINS} What we learned that we didn't know Monday: {LEARNINGS} One specific shoutout: {SHOUTOUT} What's the focus next week: {NEXT_WEEK_FOCUS}

Voice: end-of-week energy. Warmer than the weekly update. Personal but not gushing.

Length: 200-300 words.

Format: - 1-paragraph open about the shape of the week - A "things we shipped" mini-list (3-5 items, one line each) - "We learned" mini-list (2-3 items) - The shoutout (specific, named, with what they did) - "Monday morning we're..." closing line

Banned: "team", "everyone", "have a great weekend", "see you Monday", any phrase that could be on a corporate motivational poster. ```

The shoutout is the part that gets forwarded. Spend the most prompt effort on making sure it's specific and named.

Prompt 5: The "we need your input" ask

``` Draft an internal email asking employees for their input on a specific question.

The question being asked: {QUESTION} Why we're asking now: {REASON} How input will be used: {USE} The deadline for responses: {DEADLINE} What we won't do with responses (the boundary): {BOUNDARY}

Voice: respectful of their time, specific about what we want, honest about how input will be used.

Length: under 200 words.

Format: - One sentence stating the question - One sentence on the reason - 3-5 specific prompts they could respond to - One sentence on how we'll use the input - One sentence on what we WON'T do (the boundary — "this won't directly determine X, but it will inform Y") - Deadline

The boundary sentence is the trust builder. Tell them what's NOT being decided. ```

The boundary sentence is the most important sentence. Without it, internal feedback requests are treated as theater.

The meta-pattern

Every internal newsletter prompt has: - Specific input fields (not generic categories) - Voice samples or reference style - Hard length range (not "concise") - Banned phrase list (the AI-tells and the corporate-tells) - Format requirements (what comes first, second, third) - A specific named individual or specific number requirement

The bad internal newsletter prompts are 2 lines. The good ones are 15-20 lines. The extra structure earns its keep.

What I do operationally

Internal newsletters are batched. Monday morning prep, Tuesday send. The CEO records a voice memo of the leader take. The data is pulled from the metrics dashboard. The draft is generated. The CEO reviews, edits, sends.

Total CEO time: 8-12 minutes per newsletter. Total quality: noticeably better than what they were sending before. Open rate change: 28% to 64%.

What I'd build first

The Friday wrap. Lowest-stakes. Most personal. The one where AI assistance is most accepted because it's a relationship email, not a formal one.

Get the Friday wrap working. Use the same pattern for the weekly update. By month two you'll have internal comms that nobody dreads.