The short answer.
The first team to go with AI is the team whose week repeats most, whose work starts from records someone can export from a system, and whose lead will own the first workflow by name. Keenness and urgency do not decide it. When the obvious team fails one of those tests, it waits, and the team that passes all of them goes first.
Choosing the first team is part of planning it, the first of three steps: plan it, develop the workflows, deploy them. Choose your first AI wins ranks pieces of work, and Start with your teams gives each team its first five workflows. This piece ranks the teams themselves.
Not the keenest team, and not the biggest fire.
The keenest team is the wrong first choice when its enthusiasm comes from ad hoc work. People who use ChatGPT, Claude, Copilot or Gemini every day often do work that changes shape every time: a new campaign, a new design, a new pitch. A workflow needs work that runs the same way every week, so the keenest team often has the least to turn into one.
The team with the biggest fire is the wrong first choice because a fire takes all of its lead’s attention. A first workflow needs a lead who has room to test it on real cases, log every miss and decide when it is ready. Put out the fire by ordinary means, and give that team its workflow once the week is calm.
Both still go on the plan, with a date.
Four things to compare across teams.
Four facts about any team are visible today, before anything is built. Ask each team lead the same four questions.
- How much of the team’s week repeats?Count the pieces of work the team does the same way every week or month. The more of the week repeats, the more candidates for a first workflow.
- Are the inputs in a system?A workflow starts from records: an export from your accounting system, a ticket queue, a spreadsheet the team keeps. A team whose inputs live in inboxes and people’s heads needs the records gathered first.
- Does one person review the output?A team where one named person already checks the work before it leaves the team has its decision point in place. The workflow prepares; that person decides, as they do today.
- Will the lead own the first workflow?Ask the lead directly. Owning means keeping the workflow current, reading the record of misses and deciding when it changes. A lead who says “maybe next quarter” has told you the order.
The fourth question is a gate, not a score. A team that passes the first three and has no lead willing to own the workflow does not go first. Who should own AI in a company your size? separates the owner of the plan from the owner of each workflow.
Why finance, customer service and operations often go first.
Finance, customer service and operations often go first because they pass all four tests most often. Finance runs the same close, the same invoicing and the same follow-up every month, from an accounting system that exports cleanly, and a controller already reviews every figure. Customer service answers the same kinds of question from a ticket queue, with a lead who reads the hard replies. Operations schedules and orders from records it already keeps.
That is a pattern, not a rule. A finance team in the middle of changing its accounting system has inputs in motion and a lead with no room. An operations team that runs on phone calls has nothing to export. And a team nobody thinks of first, such as account management or recruiting, often passes all four tests better than any of them. Compare the teams you have.
A team comparison sheet to copy.
Copy these headings onto one page, one column per team, for three or four teams. Fill it in with each lead. Write “Unknown” where nobody knows, with who will find out.
- Team and lead.The team’s name, named for the work, and its lead.
- Repeating work.The pieces of work the team does the same way every week or month. Mark the team: most of its week, some of it, or little of it.
- Where the inputs live.The system or file each piece of repeating work starts from. Mark: exportable today, scattered, or in people’s heads.
- Who reviews the output.One name, or “nobody yet”.
- Will the lead own the first workflow?Yes, not now, or not asked yet.
- What is in the way.A system change, a vacancy, a busy season, a fire. Note when it ends.
- Who receives this team’s work.The team that picks up what this team produces.
- The decision.First, second, or later, with the date you will look again.
The rule for the sheet: a team goes first only with a yes in row five and a name in row four. Among the teams that qualify, choose the one with the most repeating work whose inputs are exportable today.
One agency compares four teams.
Take a 65-person marketing agency with four teams: creative, new business, account management and finance. The managing director filled in the sheet with each lead.
Illustrative example.
- Creative.The keenest team. Little of its week repeats, because every brief is different. The decision: later.
- New business.The biggest fire: proposals are piling up. Each proposal differs, the material sits in old decks, and the lead is the founder, who has no room this quarter. The decision: later, once the agency’s approved proposal material is gathered in one place.
- Finance.Monthly invoicing repeats and starts from the timesheet system, and the finance manager reviews every invoice. The finance manager is moving the agency to a new accounting system this quarter and said “not now”. The decision: second.
- Account management.Every client gets a weekly report built from campaign platform exports, and the account director on each client reads it before it goes out. The head of account management said yes to owning it. The decision: first, starting with the weekly client report.
Nobody had named account management at the start. The sheet did. The weekly client report starts from the client campaign performance report, a free workflow template in the Workflows Directory, adapted to the agency’s own report and tested on last month’s reports before any client sees one.
The second team receives the first team’s work.
The second team is the one that receives the first team’s output. That team already sees the first workflow in what lands on its desk, and the handoff between the two teams is where work gets lost most often.
At the agency, account management sends finance a monthly summary of hours and scope for each client, which finance invoices from. Once the weekly client report is in daily use, that monthly summary becomes account management’s second workflow and finance’s first input, once the new accounting system is in. What comes after the first AI workflow covers choosing the next workflow inside a team; the comparison sheet’s seventh row tells you which team comes next.
What is different in a company of under 200 people.
In a company of under 200 people, you choose the first team by asking each lead in person, this week. A large company runs an assessment to find out what its teams do. You know your leads by name and can fill in the whole comparison sheet in one conversation with each.
- The lead often does the work.A finance lead of a team of three closes the month alongside the others. Ownership is easy to settle; time is the thing to check.
- One person can be a whole team.A single office manager may be operations. Treat that role as a team on the sheet; it often has the most repeating work in the building.
- The second team starts sooner.The teams sit close together, so the handoff to the second team is visible from day one.
Put your teams side by side and choose where to start. 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. How organizations plan their use of AI covers the rest of the method.