Skip to content
Founder & Exec · Playbook

Who, what, why, and what stays the same. Before the rumors start.

An announcement of a team or reporting change that answers the questions people will have, with the order of conversations to hold before it goes out.

IncludedNative Claude Skill + plain .md for ChatGPT, Gemini & every LLM
100 Playbooks in the catalogDelivered as Claude Skill + plain .mdReviewed Oct 22, 2026Instruction-only · verifiable

Most organizational announcements describe the change from the company's point of view, in phrases like better alignment. Employees want to know one thing: what it means for them. When the message does not say, they fill in the answer themselves.

Org Change Announcement starts with the ten questions people will ask and marks each as answered, undecided, or not shareable. It writes a message of under 250 words in your voice, plans who hears first, and reminds you to check notice and consultation duties where you operate.

What you get

What it produces.

  • →A short announcement that answers the likely questions
  • →A question list marked answered, undecided, or not shareable
  • →The order of conversations before the message is sent
  • →A one-sentence honest reason for the change
Who it's for
  • ✦Founders moving a team under a new leader
  • ✦Executives changing reporting lines or merging teams
  • ✦Managers announcing a change to a team they lead
What's included
  • →org-change-announcement.zip: a native Claude Skill. Upload to Settings → Skills in Claude, or unzip to ~/.claude/skills/
  • →org-change-announcement-skill.md: plain markdown. Works in ChatGPT Custom GPTs, Gemini, Claude Projects, agent system prompts, anywhere
  • →A README inside the zip with install steps for Claude, ChatGPT, and Gemini
Delivery
Emailed within 60 seconds of payment
Compatibility
Claude, ChatGPT, Gemini, any LLM
License
One-time purchase, yours to keep
Sample output

What it does with a real question.

The brief

I need to announce that our platform team's 9 engineers will start reporting to Priya Raman, our new Director of Infrastructure, on March 3. Their current manager, Dan Ortiz, is moving to lead the data products group, but he'll stay available for handoff through April. Nobody's role, title, or compensation is changing.

Tell the nine engineers' reasons before they ask. The risk in this change is not the reporting line itself, since roles, titles, and pay are all staying put. The risk is that nine people hear "new boss" and "Dan is leaving" in the same breath and fill the gap with rumor. So the announcement has to answer their first questions in order: who is my manager, what stays the same, why now, and who do I ask.

The honest reason is that Dan is moving to lead data products, and Priya was hired to run infrastructure. Say exactly that, in one sentence, with no talk of alignment or synergies. Open the message with March 3 and Priya's name, then state plainly that nobody's role, title, or pay changes. Name Dan's handoff through April as a feature, because it tells the team the transition is orderly and he is still reachable.

Sequence matters more than wording. Dan should tell the platform team in person before anything goes out, ideally together with Priya, so the nine hear it from a face they trust. Priya then holds short one-on-ones within her first week. Give the wider company the announcement only after the team has heard it, within a few hours, so nothing leaks ahead of the conversation.

Next move: Draft a 200-word message in your voice using that order, and book Dan's team conversation for the morning it goes out. Since no roles or pay change, formal consultation likely doesn't apply, but confirm that with your adviser first.

The full Playbook runs the whole procedure and writes the complete deliverable, not this excerpt.

Written by claude-sonnet-5-5 with this Playbook loaded, 2026-10-11. Checked automatically for length and for copied framework text.

One-time purchase
$12.99
Yours to keep
No subscription · free updates within v1.x

Works as a Claude Skill (.zip) and as a plain .md for ChatGPT, Gemini & every LLM
Delivered to your email within 60 seconds · Secured by Stripe
Price includes UK VAT where applicable

Questions

Before you buy.

How is this different from just asking Claude directly?

Asked cold, Claude writes a polished, upbeat announcement that sounds like corporate communication. This builds the message from the questions each group will ask, marks what is still undecided, and sets the order in which people are told.

How is this different from a Tool?

Playbooks are systematically produced to a fixed template and priced accordingly ($12.99). Tools are hand-built, one at a time, and go deeper ($39 to $199). A Playbook gives you a reliable method for routine work; a Tool is for when the judgment matters more than the format.

Will this work with ChatGPT, Gemini, and other LLMs?

Yes. You get a native Claude Skill (.zip) that auto-invokes in Claude, plus a plain .md you can paste into a ChatGPT Custom GPT, a Gemini system prompt, or any LLM. The procedure travels with the file.

Can I share this with my team?

It's licensed for your own personal and professional use. The output it produces is yours to circulate. To put the Playbook itself in the hands of a whole team, email hello@authority.md about team licensing.

What if it doesn't work for me?

If the file hasn't been delivered, or arrives defective or empty, we refund in full: see our refund policy.

More Founder & Exec Playbooks

Other Playbooks.