The short answer.
A CEO asks each team lead ten questions about the team’s work: what repeats every week, what records it starts from, who checks it before it leaves the team, where it waits or gets redone, what the team’s best person does that others do not, and whether the lead would own the first workflow. Ask them in a one-to-one, before the leadership team meets to write the plan. Each answer fills a row of the plan, so you arrive at that meeting with the plan half written.
The one-to-one is the groundwork for the first step of the method: plan it, develop the workflows, deploy them. How to write an AI plan in one sitting runs the meeting itself. This piece covers the conversation with each lead that comes before it.
Ask one to one, before the group meets.
A team lead tells the CEO different things alone than in front of peers. In a group, a lead defends the team: the work is under control, the backlog is fine, nobody is a single point of failure. Alone, the same lead says which report gets redone every month, which customer email only one person can write, and which handoff from another team arrives late.
Those are the facts an AI plan is built on. A one-to-one also gives the lead room to say “not now” about owning a workflow without saying it in front of the other leads. You hear the real order of the teams before anyone has to commit to it in public.
Ask about the work, not about AI.
The questions a CEO asks a team lead are about the team’s week, because a lead knows the week exactly and knows AI only in passing. Ask “what do you use AI for?” and you hear about the tools people like. Ask “what does your team do the same way every Monday?” and you hear the first workflow.
Keep three rules for the conversation.
- Ask for examples, not opinions.“Show me last month’s version” settles more than “is it repetitive?”.
- Write the answers down in the lead’s words.The lead’s name for a piece of work is the name the team will use for the workflow.
- Promise nothing in the room.The lead learns the order of the teams at the planning meeting, with everyone else.
Ten questions to copy.
Copy these ten questions and ask them in this order, in every one-to-one, so the answers line up across teams. Write “Unknown” where the lead does not know, with who will find out.
- What does your team do the same way every week or month?List the pieces of work by name. Ask for five.
- What does each of those start from?The system, export, spreadsheet, inbox or form. Ask whether someone can pull it out today.
- Who checks the work before it leaves the team?One name for each piece of work, or “nobody”.
- Where does work wait, or get done twice?The step that queues up, and the step that gets redone after someone spots a mistake.
- What does your best person do that the others do not?The checks, shortcuts and judgment calls that live in one head.
- Which work comes to you from another team, and which do you send on?Name the teams and the piece of work that crosses between them.
- Who on your team already uses ChatGPT, Claude, Copilot or Gemini, and for what?The people, and the pieces of work they point it at today.
- Which work should AI stay away from?The work where the whole value is a person’s judgment in the moment, or where a mistake cannot be caught in time.
- What is in the way this quarter?A system change, a vacancy, a busy season. When it ends.
- Would you own the first workflow for your team?Owning means keeping it current, reading the record of misses and deciding when it changes. Yes, not now, or someone else on the team, by name.
How the answers become the plan.
Each of the ten answers fills a specific part of the AI plan, so the plan writes itself from the notes of the one-to-ones.
- Questions one and two give the candidate workflows for each team and tell you which start from records someone can export.
- Questions three and ten give each workflow its person who decides and its owner. A candidate with no reviewer and no owner waits.
- Questions four and five say where a workflow pays off first: the step that waits, and the know-how that sits with one person.
- Question six draws the work between teams, which is where the second team on the plan usually comes from.
- Question seven finds the people who will test the first workflow and help the rest of the team pick it up.
- Questions eight and nine say what stays off the plan and which teams go later.
Compare the teams side by side and the first team is usually obvious. Which team should go first with AI? gives the rule for choosing it. Once the teams are settled, the same answers break down by role: How to plan AI by role takes the next step.
A furniture maker asks its leads.
Take a 110-person furniture maker with six teams: design, production, purchasing, the order desk, deliveries and finance. The CEO held a one-to-one with each lead in the same week and asked the ten questions.
Illustrative example.
- The order desk.Every custom order is turned into a confirmation for the customer and a cut list for the workshop, from the order system. The order desk lead checks every confirmation. One senior coordinator knows which fabric and finish combinations the workshop cannot make, and the others ask her. The lead said yes to owning a workflow.
- Production.The weekly build schedule starts from the order system and the stock count, and the production manager redoes it every time a delivery of timber slips. The production manager is busy with a new finishing line this quarter and said “not now”.
- Purchasing.Reorders run from a spreadsheet the purchasing lead keeps by hand. The inputs need gathering into one export before a workflow can start from them.
- Design.Each new range is different. Two designers use an AI assistant every day for mood boards and product copy. The design lead wants AI kept away from the final drawings.
At the planning meeting the CEO laid the notes side by side. The order confirmation went first, owned by the order desk lead, with the senior coordinator’s rules on fabric and finish written into it. Question six had shown that the order desk’s cut list is production’s main input, so production went second, once the finishing line is in. The order desk’s first workflow started from a free workflow template in the Workflows Directory, adapted to the company’s own confirmation and tested on last month’s orders before any customer saw one.
What is different in a company of under 200 people.
In a company of under 200 people, the CEO asks every team lead personally. A large company sends a survey to hundreds of managers and reads a summary. You have six or eight leads, you know each one by name, and the whole round of one-to-ones fits inside a normal week.
- The lead does the work.The lead of a team of four often runs the repeating work alongside the team, so the answers to the first five questions come first hand.
- One person can be a team.An office manager or a single bookkeeper is a team on the plan. Give that person the same one-to-one and the same ten questions.
- The CEO is often a lead too.If you run sales or design yourself, answer the ten questions for that team in writing before you ask anyone else.
Take the ten questions into this week’s one-to-ones and bring the answers to the planning meeting. 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 each lead adds their own team. How organizations plan their use of AI covers the rest of the method.