Hire an AI team change announcement planner

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A priority-shift memo that names the change, the reason and what stops
• A rollout plan: who hears first, where and when
• The announcement, manager talking points and hard-question answers
• A listen-first talk plan for each person who will push back

How it does the job well

• Base people decisions on job-related evidence, applied the same way to everyone.
• Write in plain, respectful language the person affected could read.
• Keep personal data to what the task needs, and handle it privately.
• Check local employment law and company policy before advising on hiring, pay or exits.

Mistakes it avoids

• Biased wording in job ads, reviews or interview questions.
• Plans with no owner, timing or way to check progress.
• Treating a template as legal advice.

What a good result looks like

An example, not your task: You are moving the company's main effort from one thing to another.

• Step 1: Memo. A short memo naming the shift, why now, what stops and what each team does differently.
• Step 2: Rollout plan. Who hears first, in what setting, how far apart, and what each group can do the week after.
• Step 3: Announcement. The leader message, manager talking points, town hall script and honest answers to hard questions.
• Step 4: Listening talks. A listen-first talk plan for each person likely to push back, to hold before the announcement.
• HAND-BACK SUMMARY. Each step's file, any step not run and why, and every MISSING line in one list.

How the work is checked

• Each step passed its own checks, or the run stopped at the step that failed and says why.
• The steps ran in order, and each one used the result of the one before.
• Nothing was invented to fill a gap. Every gap is a MISSING: line.
• Nothing was sent, published or paid for without a clear yes.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Stephen Covey and Dale Carnegie would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Write the memo. Writes a short memo that names the shift, the reason, what stops and what each team does differently, in the manner of Gates's 1995 memo.
• Plan the rollout. Plans who hears first, where, how far apart, and what each group needs the week after.
• Write the announcement. Writes the leader announcement, manager talking points, the town hall script and hard-question answers.
• Plan the listening talks. Plans a listen-first talk with each person who will push back, to hold before the announcement.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id announce-a-change-of-direction-and-bring-the-team-with-you only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/announce-a-change-of-direction-and-bring-the-team-with-you/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The change: what starts, what stops and why
• Your teams and what each works on now
• Who it touches most and who will push back
• The timeline you have
• Your notes or a draft, if you have one (optional)

Helpful context (optional)

• The numbers behind the change
• A past memo in your voice
• Your team list with roles

Tools and access

• Any good chat AI: Every step is a plan or a piece of writing.
• Your calendar: Book the listening talks before the all-hands.
• Any good chat AI: It organises facts and writes a short memo in plain text.
• A shared document: Leaders can read, comment and confirm their part in one place.
• Claude, ChatGPT or Gemini: Planning and rewording are text work. No files, web access or paid tools needed.
• A friend to practise with: Say the listening phase out loud once. Reading it silently hides how hard it is not to answer back.

Functions and deliverables

• Team change announcement planner: Draft a change memo, rollout plan, team messages and listening talks before you announce a new direction.
  • A priority-shift memo that names the change, the reason and what stops
  • A rollout plan: who hears first, where and when
  • The announcement, manager talking points and hard-question answers
  • A listen-first talk plan for each person who will push back
• Top-priority shift memo writer: Write a one-page memo that resets your team's top priority after a market change, with a stop and a start for each area.
  • A one-page memo of about 450 words with the new top priority in the first lines
  • A stop, a start, an owner and a date for each area
  • A request to each leader to try the new thing and report one lesson
  • A date when the plan is revised, and what would bring it forward
  • MISSING lines for anything you did not tell it, so nothing is made up
• Change rollout planner: Describe a re-org or tool switch. Get a rollout plan, message templates and a plan for pushback.
  • A stage-by-stage rollout plan
  • Message templates for each group
  • Answers to likely pushback
  • Ways to keep the change in place
  Source: Alireza Rezvani.
• Workplace change announcement writer: Turn change details and staff concerns into leader announcements, manager notes, and town hall scripts.
  • Leader announcement
  • Manager talking points
  • Town hall script
  • FAQ and hard-question answers
  • Timing and channel plan
  Source: Tuan Duc Tran.
• Listening conversation planner: Prepare a hard conversation. Get a plan to listen until they feel heard, say your side once and agree one next step with a date.
  • A plan for the setting and for giving them the floor
  • A list of the urges you will feel to defend yourself, each with a quiet response
  • Five to eight phrases that show you understood, plus a check that they feel heard
  • Your side in three or four sentences, and two curious questions
  • One next step with a date and an owner
• me.md builder: Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.
  • One me.md file with up to ten dated sections
  • A list of facts taken from memory, for you to check
  • A short note of what it removed for privacy
  • The two next steps, to save it and set it up
• Stephen Covey: Plan priorities, handoffs or a hard talk using Stephen Covey’s recorded approach. State the goal, listen first and agree a next step.
  • Your problem worked on the way Stephen Covey would: their questions, their method, their push-back
  • The answer or the work, in Stephen Covey's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Dale Carnegie: Rewrite a tense message or prepare a people conversation using Dale Carnegie’s recorded approach. See the other side, give sincere credit and ask clearly.
  • Your problem worked on the way Dale Carnegie would: their questions, their method, their push-back
  • The answer or the work, in Dale Carnegie's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• You are moving the company's main effort from one thing to another.
• A past change was announced once and quietly ignored.
• A few senior people will dislike the change and you need them on side.

Limits to check before starting

• You are making a small tweak nobody needs to hear about: just tell your team in one message.
• You are announcing layoffs or pay changes: talk to HR and a lawyer first, then use this for the wording.
• You only want one decision recorded with its dissent: use the Team decision and dissent note writer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
• Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
• Paste the change, the reason and who it touches. It writes the memo and the rollout plan.
• Read the announcement and the hard-question answers. Cut anything you would not stand behind.
• Hold the listen-first talks before the all-hands, then announce.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/announce-a-change-of-direction-and-bring-the-team-with-you for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.