The short answer.
You write your company’s AI plan in one meeting. Invite the leader of each team, ask each one to bring the five pieces of work their team repeats, and answer six questions in order: where are we going, which teams go first, what repeats in each, which piece first and why, who owns each, and when do we review. You walk out with one page, and the first workflow starts the next morning.
How organizations plan their use of AI sets out what a plan contains and the three steps that follow it: plan it, develop the workflows, deploy them. This piece is the working session that produces the plan: one disciplined meeting that turns years of experimenting into directed use.
Who needs to be in the room.
The room for an AI planning meeting holds the person who will own the plan and the leader of each team the plan covers first. Leave out anyone selling a tool.
- The owner of the plan, who chairs.The owner, the CEO, the managing partner or the head of operations: the person who will keep the page current and settle the order of work between teams. Who should own AI in a company your size? helps you choose.
- The leader of each team that starts first.Three to six team leaders. Each can say yes on the team’s behalf.
- A note-taker who is not the chair.One person writes the page as the room answers, so the page is finished when the meeting ends.
- Whoever runs your AI accounts, if that is someone else.The person who administers your ChatGPT, Claude, Copilot or Gemini seats confirms which assistant the plan uses.
What each leader brings.
Each team leader brings five pieces of work the team does the same way every week or month, with four facts about each. Each leader checks the list with the people who do the work first. Build your AI plan with the people who do the work shows how to ask them.
- What the work is called.In the team’s own words: “the Monday job schedule”, “the quote from site-visit notes”.
- How often it happens.Daily, weekly or monthly. Unknown is an allowed answer; a guess is not.
- What it starts from.The notes, records, emails or exports someone opens to begin the work.
- Who does it and who checks it.The role that does the work and the role that reviews it before it leaves the team.
The six questions, in order.
The six questions of an AI planning meeting are asked in a fixed order, and the note-taker writes each answer on the page before the room moves on.
- Where are we going?The chair proposes one sentence: what your teams will be able to do with AI that they cannot do today. The room edits it until every leader can repeat it. Write the sentence at the top of the page.
- Which teams go first?Pick three to six teams. Write down the teams that start and, on a separate line, the teams that wait. A team waits because it is mid-change or its work rarely repeats, never because its leader is quiet.
- What repeats in each team?Each leader reads out the five pieces of work. The leader keeps, swaps or drops items as the room asks. Write the agreed five under each team.
- Which piece goes first, and why?One piece per team. Choose the work that happens often, starts from records someone can export and already has a reviewer. Write the reason beside the choice in one line, so the next review can test it. Choose your first AI wins has the scorecard.
- Who owns each one?One person per first workflow, by name, sitting in the team that uses it. The owner keeps the workflow current and decides when it changes. Write the name, and the role that approves each output.
- When do we review?A fixed day each month, in everyone’s calendar before the meeting ends. Write the date. How to run a monthly AI review covers the agenda for that meeting.
If a question stalls, the chair decides, and the note-taker writes “decided by the chair” beside it. The monthly review reopens anything that turns out wrong.
The meeting agenda to copy.
Copy this agenda into your invitation.
- Before the meeting.Chair: a draft of the one-sentence direction. Each team leader: five pieces of repeating work, each with its name, how often, what it starts from, who does it and who checks it. Accounts administrator: which assistant the company has approved.
- Where are we going.Produces: one sentence, agreed.
- Which teams go first.Produces: the teams that start, and the teams that wait.
- What repeats in each team.Produces: five pieces of work per starting team.
- Which piece first, and why.Produces: one first workflow per team, with a one-line reason.
- Who owns each.Produces: one owner by name per workflow, and the role that approves its output.
- When we review.Produces: a monthly date, booked.
- Close.Note-taker reads the page aloud. Each leader confirms their team’s lines. Chair names what each owner does next morning.
One meeting in practice.
Illustrative example.
Take a 55-person landscaping company. The owner chairs. Around the table sit the leaders of sales and design, maintenance crews, installation and the office, with the office manager taking notes because she also runs the company’s AI accounts.
The direction the room agrees: every customer gets a clear quote and a reliable schedule, and every crew starts the day knowing exactly what the job needs. Sales and design, maintenance and the office go first. Installation waits, because its leader is changing how jobs reach crews.
Sales and design picks the quote prepared from site-visit notes and photos, because it happens several times a week and the sales lead already reviews every quote. The sales lead owns it and approves every price. Maintenance picks the Monday crew schedule, owned by the maintenance manager, who decides every change to a route. The office picks follow-ups on overdue invoices, owned by the office manager, who approves each message before it goes. Review falls on the first Tuesday of each month.
What happens the next morning.
The morning after the AI planning meeting, the plan’s owner sends the page to everyone who was in the room, and each workflow owner starts on the first workflow. Four things happen that day.
- The page goes out unchanged.The owner of the plan sends the page as the room left it. Edits wait for the monthly review.
- Each owner gathers real cases.Ten recent examples of the first piece of work, with the finished result for each, so the workflow can be tested against work where the right answer is already known. We have a plan. How do we build the first AI workflow? takes it from there.
- Each leader shows the team.The team sees its five pieces of work, the one chosen first and who owns it, and says what is missing.
- The review is in the calendar.Every person in the room has the monthly date.
Why one meeting is enough under 200 people.
A company of under 200 people writes its AI plan in one meeting because everyone who decides fits at one table. Most published advice assumes a large enterprise with a steering committee and months of discovery.
- The leaders know the work first-hand.A team leader in a 50-person company can name the five pieces of repeating work without a survey.
- The person who decides is in the room.The owner or CEO settles the order on the spot, so nothing waits for sign-off.
- The assistants are already bought.No platform decision comes first. The meeting decides what the seats you already pay for are for, which is where 10X the ROI of your existing AI comes from.
Once more teams join and colleagues add their own work, the page outgrows a document. FullyPowered Planner is where the plan lives: you set out your teams, their roles and the work between them, and choose what to build first. Your colleagues add their own teams. Start your plan before the meeting and the note-taker fills it in as the room answers.