The short answer.
Tell employees four things about AI, in one announcement from the person who runs the company: what is decided, what each team is asked to do, what stays the same, and where to bring ideas. Say it on the day the plan names its first team and its first workflow, and have every team lead repeat it to their own team that week. The announcement marks a change of gear: experimenting was the right way to start, and from today the company uses AI on purpose.
The announcement is part of the first step of the method: plan it, develop the workflows, deploy them. Is it OK to let employees figure out AI themselves? sets out what the company owes each person who uses AI. This piece is the moment you say so out loud, and the words to say it with.
Announce the plan once it names a first team.
The right time to announce the AI plan is the day the plan names a first team, a first workflow and the person who owns it. An announcement before that has nothing concrete in it, and people fill the gap with guesses.
Three things should be true before you speak:
- The plan exists on one page.It lists your teams, the roles in them, the work each team repeats and what gets built first.
- The first team’s lead has said yes.The lead owns the first workflow by name and stands next to you when you announce it.
- The idea channel is set up.One place, one person who reads it, and a set day each week when that person answers.
The four parts of the announcement.
A good AI announcement has four parts, always in this order, and each part answers a question employees already have.
- What is decided.The company has a plan for AI, team by team. Name which AI assistant the company uses, on whose account, and the first team and workflow being developed now. Say who owns the plan.
- What each team is asked to do.Each team lead lists the work the team repeats every week and month, and picks the pieces AI should prepare. Give the date the lists are due. The first team tests its workflow on real cases and logs every miss.
- What stays the same.A person decides; a workflow prepares. The person who signs off on a piece of work today still signs off on it. Each team keeps its standards, and the work each person is responsible for stays theirs. People keep using the assistant to learn and to draft.
- Where to bring ideas.One place to send them, the name of the person who reads them, and the day each week that person answers. Every idea gets an answer: on the plan, later, or no with a reason.
Leave out the tools you considered, the vendors you met and the reasons you waited. Employees want the decision and their part in it. If your company is writing rules for AI use at the same time, Does a small company need an AI policy? covers that page; keep the announcement about the plan.
Who says it, and who says it again?
The person who runs the company makes the AI announcement, at a meeting everyone attends, and each team lead says it again to their own team within the same week. The CEO or owner saying it tells people the plan is a company decision, not a side project of the most enthusiastic person in the building. The team lead saying it again turns it into the team’s own work: which of our pieces of work, which of us tests it, what changes on our desks.
The owner of the plan answers questions after both meetings. When the owner of the plan and the person who runs the company are the same person, say so. How to get people to actually use AI at work covers what happens after the announcement, when the first workflow reaches people’s desks.
A script to copy.
Copy this script, fill in the brackets and read it as written. It works spoken at a meeting and sent as a note the same day.
- Where we have been.“For [the past while], many of you have been trying [assistant] in your own work. That was the right way to start, and thank you for it. Today we move from experimenting to a plan.”
- What is decided.“We have a plan for AI, team by team. We use [assistant], on the company’s account. [Owner of the plan] owns the plan. The first team is [team], and the first workflow is [piece of work]. [Team lead] owns that workflow.”
- What each team is asked to do.“By [date], every team lead will list the work your team repeats each week and month, with you, and pick the pieces AI should prepare. [Team] will test its workflow on real cases from [date] and log every miss.”
- What stays the same.“A person decides; the workflow prepares. Whoever signs off on a piece of work today still signs off on it. Our standards stay our standards. Keep using [assistant] to learn and to draft.”
- Where to bring ideas.“Send ideas to [place]. [Name] reads every one and answers each [day]: on the plan, later, or no with a reason.”
- What happens next.“[Team lead] will talk with each team this week. You will hear from me again on [date] with what the first team learned.”
One staffing agency makes the announcement.
Take an 80-person staffing agency with four teams: recruiting, client accounts, candidate onboarding, and payroll and billing. Recruiters had been using an AI assistant on their own for job ads and candidate emails, each in their own way.
Illustrative example.
- What is decided.The managing director announced at the Monday all-hands that the agency uses one assistant on the company account, and that the operations director owns the plan. The first team is candidate onboarding, and the first workflow checks each new placement’s paperwork against the client’s requirements and lists what is missing.
- What each team is asked to do.Each team lead lists the team’s repeating work with the team by the end of the month. Onboarding tests the paperwork check on last month’s placements before it touches a live one.
- What stays the same.The onboarding coordinator still clears every placement before the candidate starts. Recruiters keep writing their own job ads with the assistant while their team’s list is drawn up.
- Where to bring ideas.One shared channel, read by the operations director, answered every Friday.
That afternoon the onboarding lead met her team and showed them the first test case. The first Friday brought a recruiter’s idea for a workflow that drafts a weekly shortlist summary for each client. It went on the plan for recruiting, second in line. The paperwork check started from a free workflow template in the Workflows Directory, adapted to the agency’s own client requirements.
What is different in a company of under 200 people.
In a company of under 200 people, you announce the AI plan in person, to everyone at once, in a few plain sentences. A large company runs a communications campaign with phases and approvals. You have one all-hands and a handful of team leads you know by name.
- Everyone hears the same words.One meeting reaches the whole company, so nobody hears a second-hand version first.
- The ideas come to a person, not a committee.One named reader answering every week is enough, and people see the answer arrive.
- The follow-up is visible.When the first team’s workflow is in daily use, everyone sees it, and your next update shows it rather than describes it.
Keep the follow-up on the same rhythm as your leadership reporting. How to brief your leadership team on AI gives the monthly page that feeds your next company update.
Write the plan before you announce it. FullyPowered Planner is where the plan lives: you set out your teams, their roles and the work between them, choose what to build first, and your colleagues add their own teams, so the team leads’ lists land in one place. How organizations plan their use of AI covers the rest of the method.