The short answer.

An AI goal for the year names one workflow, the role and team that run it, the quarter by which it is in daily use, and the one person who owns it. Write four to eight goals in that form, one or two per quarter, and check each on the last day of its quarter by asking a yes-or-no question: does that role run that workflow on every case now? Goals that cannot be checked that way, such as “adopt AI” or a count of licences, come off the page.

Setting goals is part of planning it, the first of three steps: plan it, develop the workflows, deploy them. How to put AI in next year's plan and budget covers where AI sits in the annual plan and what goes on the budget line. This piece writes the goals themselves, line by line, so each one is a promise someone can keep.

The five parts of an AI goal.

Every AI goal has five parts, and a goal missing any one of them is a wish. Write them as one sentence: “By the end of the second quarter, the project manager role in delivery runs the weekly client status workflow on every active project, owned by the head of delivery.”

  1. The workflow.One piece of work, named for what it produces: the weekly client status report, the first draft of a proposal, the monthly invoice run. One workflow per goal.
  2. The team and the role.The team that carries the work and the role inside it that runs the workflow. A role is named for the work, so the goal survives a change of person. How to plan AI by role sets out the roles.
  3. Daily use, defined.What “in use” means for this work: every active project, every invoice, every new enquiry. The workflow prepares; the person in the role decides, every time.
  4. The quarter.The quarter by which the workflow is in daily use, not the quarter in which building starts.
  5. The owner.One person, by name, who keeps the workflow current, reads what it gets wrong and decides when it changes.

Each goal sits under the one sentence that says where the company is going with AI. Decide where your company is going with AI shows how to write it.

Why “adopt AI” and seat counts are not goals.

“Adopt AI” is not a goal, because nobody can say on a given day whether the company has done it. Seat counts and logins are not goals either: they show that people opened ChatGPT, Claude, Copilot or Gemini, not that any work now runs a better way. A company can hit a seat target and still be undirected, with a bigger bill.

Rewrite each vague goal as a workflow goal. Three common ones, rewritten:

  • “Everyone uses AI daily.”Becomes: the account manager role in client services runs the meeting follow-up workflow after every client meeting by the end of the first quarter.
  • “Roll out assistant licences to all staff.”Becomes: the seats go to the roles that run a workflow on this page, in the quarter that workflow starts.
  • “Use AI to speed up sales.”Becomes: the solutions lead role in sales runs the first-draft proposal workflow on every new proposal by the end of the third quarter.

How many goals, and in which quarter?

Set one or two AI goals per quarter, four to eight for the year, and put the most certain ones first. A first-quarter goal is a workflow from a team whose work repeats every week, whose inputs export from a system today, and whose lead has said yes to owning it. Which team should go first with AI? sets out that test.

  • First and second quarter.Named workflows, named teams, named owners. These goals are firm.
  • Third and fourth quarter.Named teams and the work they repeat, with the workflow chosen when the quarter before it ends.
  • Every month.Each goal gets one line in the monthly review: on track, at risk, or moved, and why. How to run a monthly AI review runs that meeting.

A goal that slips moves to the next quarter with its reason beside it.

A blank goals page to copy.

Copy these headings onto one page. Write the company sentence once at the top, then one block per goal, grouped by quarter. Write “Unknown” where nobody knows yet, with who will find out.

  1. Where we are going with AI this year.One sentence.
  2. Quarter.The quarter by which the workflow is in daily use.
  3. Team.Named for the work.
  4. Role.The role that runs the workflow.
  5. Workflow.Named for what it produces.
  6. Starts from.The records or files the workflow reads.
  7. Who decides.The role that checks what the workflow prepares before it goes anywhere.
  8. Daily use means.Every case the workflow covers: every project, every invoice, every enquiry.
  9. Owner.One person, by name.
  10. Status at the last monthly review.On track, at risk, or moved, with the reason.

The rule for the page: a goal stays on it only with a name in row nine and an answer in row eight.

One software consultancy sets its year.

Take a 90-person software consultancy with five teams: delivery, engineering, sales, finance and recruiting. The managing director wrote the company sentence (every client receives the same well-prepared work whoever leads the project) and filled in the goals page with each team lead.

Illustrative example.

  • First quarter, delivery.The project manager role runs the weekly client status workflow on every active project. It starts from the project tracker export and the week’s meeting notes, and the project manager edits and sends each report. Owner: the head of delivery.
  • Second quarter, finance.The billing role runs the monthly invoice preparation workflow from the timesheet system on every client account. The finance manager approves every invoice. Owner: the finance manager.
  • Second quarter, engineering.The tech lead role runs the release notes workflow from the ticket tracker on every client release. The tech lead edits and approves the notes. Owner: the head of engineering.
  • Third quarter, sales.The solutions lead role runs the first-draft proposal workflow on every new proposal, from the consultancy’s approved statements of work. The solutions lead writes the scope and the price. Owner: the sales director.
  • Fourth quarter, recruiting.The team and the work are named: the interview brief each hiring manager reads before a technical interview. The workflow is chosen at the end of the third quarter. The hiring manager decides on every candidate. Owner: the head of people.

Two goals came off the page. “Every engineer uses AI every day” had no workflow and no owner. “Licences for all 90 people by spring” became a line under each goal instead: seats go to the roles that run a workflow, in the quarter it starts.

The consultancy developed the first goal’s workflow from a free workflow template in the Workflows Directory, adapted to its own report and tested on last month’s projects before any client saw one.

What is different in a company of under 200 people.

In a company of under 200 people, the AI goals are set by the leadership team in one meeting and checked by name, because everyone on the goals page is someone the managing director sees every week. A large company cascades goals through layers. You write them once, together, with the people who will own them in the room.

  • The owner often runs the workflow too.A finance manager in a team of three is both. The goal names the role and the owner, even when they are the same person.
  • Fewer goals, all real.Four goals that each change how a team works every week beat a long list nobody tracks.
  • The goals page and the plan are one document.There is no separate AI goals deck. The goals live in the plan, beside the teams and roles they belong to.

Write your year’s goals where your plan already lives. 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. When a goal needs a workflow built, we develop it with you in a 2-Week Workflow Sprint. How organizations plan their use of AI covers the rest of the method.