The short answer.

You plan AI by role by listing your teams first, then the roles inside each team, named for the work: accounts payable, intake, estimator. For each role you write what it should be able to do with AI: the two or three workflows it runs, what each workflow starts from, and what the person in the role still decides. Workflows belong to the role, so whoever holds the role next starts with them, and nobody is rated or ranked by the plan.

A role plan is one part of a company’s AI plan. How organizations plan their use of AI sets out the whole method: plan it, develop the workflows, deploy them. This piece covers the roles.

Why plan by team first, then by role?

Plan by team first because a team shares its work, its records and its standards, so most decisions about AI can be settled once for the whole team. A finance team agrees which accounting exports it trusts and who approves a payment, and that holds for every role in the team.

Roles come second because a role plan only makes sense inside a team. "Intake" in a law firm and "intake" in a clinic are different work. Once the team is on the page, its roles are quick to name, and each role inherits the team’s records and standards. Start with your teams: the first five workflows each one should practise gives a first set of workflows for each common team.

How is a role different from a person or a job title?

A role is a kind of job within a team, defined by the work it repeats. A person is who holds the role this year. A job title is what is printed on a business card. The three often line up, and they are worth keeping apart in an AI plan.

  • One person often holds several roles.In a company of 40, the office manager may hold accounts payable, onboarding and supplier orders. Each of those roles gets its own workflows, and the person runs all of them.
  • One role is often held by several people.Three estimators share one role. They run the same estimating workflow, with the same inputs and the same checks, so their work comes out the same way.
  • A job title hides the work."Operations coordinator" says little about what the person does each week. "Scheduling" and "vendor invoices" say exactly what a workflow should prepare.

Name roles for the work, never for a person. A role called "Dana’s stuff" leaves with Dana. A role called "renewals" stays with the team. Names of people are welcome where they serve the work, such as the owner of a workflow.

What should each role be able to do with AI?

Each role should be able to run two or three workflows that prepare the work it repeats most often, in the AI your company already pays for. Write four things for each role.

  1. The work the role repeats.The pieces of work done the same way every week or month: coding vendor invoices, preparing a renewal notice, building an estimate from a drawing set.
  2. The workflows the role runs.Two or three to begin with, chosen from the repeating work. Each workflow is your best way of doing one piece of work, written precisely enough that ChatGPT, Claude, Copilot or Gemini prepares it the same way every time.
  3. What each workflow starts from.The export, form, email or document the person hands it. A workflow that starts from a record someone can export is easier to build and easier to check.
  4. What the person in the role still decides.Which invoice is paid, which estimate goes out, which client is accepted. The workflow prepares. The person decides, and anything that sends, pays or changes a record waits for their approval.

Two or three is enough per role. Start with the one that repeats most often, and add the next when the first is running every week.

Roles are where workflows land.

A workflow is assigned to a role, not to a person, so that a new person in the role starts with every workflow the role already runs. The know-how stays with the team when people move.

Assigning workflows to roles also shows you where AI is missing. A role with no workflow on the plan is a role whose repeating work nobody has looked at yet. A workflow that several roles run, such as a client handoff, is a handoff between teams and belongs on the plan as one. Add AI workflows to your chart of seats shows how to put workflows next to the roles on the chart you already keep.

The role plan describes work, never performance. Nobody is rated or ranked by it.

A role sheet to copy.

Copy these headings into a document, one sheet per role. Fill each sheet in with the person or people who hold the role, in one sitting.

  1. Team.The team the role sits in.
  2. Role.Named for the work, in two or three words.
  3. The work it repeats.Three to five pieces of work done the same way every week or month.
  4. The workflows it runs.Two or three, each with what it starts from and what it produces.
  5. What it decides.The approvals and judgments that stay with the person in the role.
  6. Who covers it.The person who runs the role’s workflows when the usual holder is away.

Whoever covers the role runs the same workflows, so cover stops being a scramble.

One company, role by role.

Illustrative example.

Take a 55-person property management company. Its plan starts with three teams: accounting, leasing and maintenance. Accounting has two roles, accounts payable and owner statements. Leasing has applications and renewals. Maintenance has work order intake and vendor scheduling.

The renewals role is held by two people. Its sheet lists the work it repeats: preparing renewal notices, answering tenant questions about terms, and logging signed renewals. Its first workflow prepares each renewal notice from the lease export and the renewal rules. The person in the role decides the terms offered and approves every notice before it is sent. The office manager covers the role when either holder is away.

Work order intake is held by one person who also holds vendor scheduling. Each role has its own sheet and its own first workflow: one sorts incoming requests by urgency and property, the other drafts the week’s vendor schedule from open work orders. The maintenance lead owns both workflows. When a new coordinator joins maintenance, they start with both, already written down.

What is different in a company of under 200 people.

Most published advice on planning AI by role is written for large enterprises, with job architectures, competency frameworks and hundreds of job codes. A company of under 200 people plans roles differently.

  • People hold several roles.Plan the roles anyway. The person runs each role’s workflows in turn, and when the company grows and splits the work, each role moves to its new holder with its workflows attached.
  • You can name every role from memory.A role plan for a 50-person company is a few dozen sheets, and the team leads can fill them in during a single week.
  • Cover is the biggest win.In a small team one absence stops a role. A role with written workflows keeps running when its usual holder is away.

Somebody still owns the whole plan. Who should own AI in a company your size? answers who, and How to deploy AI workflows to a whole team, and keep them working covers putting each role’s workflows into daily use.

Where the role plan lives.

A first role plan can live in a document, one sheet per role. FullyPowered Planner is where the plan lives after that: you set out your teams, then their roles and the work between them, and choose what to build first. Colleagues add their own teams and roles, and everyone sees their part of the same plan. When a workflow is ready, the Workflows Directory holds free workflow templates to start from, and we build any workflow your roles need.

Decide what each role should be able to do with AI. Then give every person in the role the same start.