The short answer.

Good AI adoption after a year means you can answer four things for every team: which workflows it runs, who owns each one, when each was last reviewed, and what the team now does with the time. Every team has its first few workflows in daily use, each with an owner and a current version kept in one place; a new hire starts with them; the monthly review happens; and the plan says what is next. Each is a fact you can check by opening the plan.

That picture is the managed stage described in The stages of AI at work, set out line by line so you can hold your own company against it.

What should be true in each team?

A year into the AI plan, each team runs a handful of workflows as part of its normal week, and the team lead can show you each one. Six things are true in every team.

  • Its first workflows are in daily use.Each team runs its first two to five workflows on real work, in the company’s own ChatGPT, Claude, Copilot or Gemini, without anyone asking it to.
  • Each workflow has one owner, by name.The owner sits in the team that runs the workflow, keeps it current and decides when it changes.
  • Each workflow has a current version in one place.The team runs the same version from the same place, and a version note says what changed, when and why.
  • A person decides at every step.The workflow prepares, and the person whose work it is checks and approves. Anything that sends, pays or changes a record waits for that approval.
  • A new hire starts with the workflows.The plan lists which workflows come with each role, so someone new runs the team’s best method in their first week instead of inventing their own.
  • The team lead can say what the time goes to now.The time a workflow frees is pointed at named work, written in the plan: the follow-up nobody got to, the second check, the client call.

What should be true for the company?

A year into the AI plan, the company as a whole runs its use of AI the way it runs anything else that matters: one plan, one owner, one review, one next step.

  • One plan covers every team.The plan lists every team, its roles, the workflows each runs and the work that passes between teams.
  • One person owns the plan.One person, by name, keeps the plan current and settles the order of work between teams. In most companies under 200 people that is the head of operations, the chief of staff or the owner.
  • The monthly review happens.The owner of the plan meets the workflow owners each month, asks whether each workflow is used and useful, and updates the plan before the meeting ends. How to run a monthly AI review has the agenda.
  • The handoffs between teams are on the plan.Where one team’s output becomes another team’s input, the plan shows both teams and the one role that owns the workflow.
  • The plan says what is next.Each team has its next workflow named, with an owner and a start month, and no more than two or three are in development across the company at once.
  • The approved assistant and its rules are written down.Which assistant the company uses, and what information may go into it, fits on one page that everyone can find.

How will we know we got there?

You know your company has reached a good first year when every line above can be answered by opening a record, not by asking around. The test is simple: pick any team, then any workflow in that team, and see whether the answers are written down.

  1. Open the plan.Does the team appear, with its roles, its workflows and an owner beside each one?
  2. Open the workflow.Is there one current version, with a version note that gives the date and reason for the last change?
  3. Open the review notes.Was the workflow discussed at a monthly review in the last quarter, and what was decided?
  4. Ask the newest person in the team.Did they start with the workflow, and can they say who checks their checking?

If all four answers are on paper for a team chosen at random, the plan is managed. If one answer is “it depends who you ask”, that line is still open, and the next monthly review is where it gets closed. Whether the work is paying back is a separate measure, taken against a baseline written before the first run; How to tell whether AI is paying back covers it.

A twelve-line checklist to copy.

Copy these twelve lines and answer each yes or no for your company. Every no is an item for the next monthly review.

  1. Plan.One plan lists every team, its roles and the workflows each runs.
  2. Plan owner.One person, by name, owns the plan.
  3. Workflows in use.Every team runs its first workflows on real work each week.
  4. Workflow owners.Every workflow has one owner, by name, in the team that runs it.
  5. Current versions.Every workflow has one current version, kept in one place.
  6. Version notes.Every change has a note: date, what changed, why, who approved it.
  7. Approvals.Anything that sends, pays or changes a record waits for a person to approve it.
  8. New hires.Each role lists its workflows, and new people start with them.
  9. Monthly review.The review ran each month this quarter, and the plan changed after it.
  10. Handoffs.The work between teams is on the plan, with one owning role each.
  11. Freed time.Each team lead can name the work the freed time now goes to.
  12. Next.Each team’s next workflow is named, with an owner and a start month.

One firm, a year in.

Illustrative example.

Take a 45-person civil engineering firm with four teams: project delivery, drafting, finance and business development. A year into its plan, the operations director owns the plan and runs the review on the first Tuesday of each month. Project delivery runs a site visit report workflow and a weekly client update, both owned by a senior project engineer, who approves every report before it goes out. Drafting runs a drawing register check, owned by the drafting lead. Finance runs a month-end work-in-progress summary, owned by the finance manager, who decides every figure. Business development runs a proposal first draft, owned by the business development lead, which draws on the project delivery team’s reports, so that handoff sits on the plan under both teams. A graduate engineer who joined in the spring started with the two project delivery workflows and had the senior engineer check her checking. Each team lead has written down what the freed time goes to. The plan names drafting’s next workflow, a transmittal check, starting next month.

What is different in a company of under 200 people.

A company of under 200 people can reach the whole picture within the first year, because every team fits on one plan and the people who decide sit in one room. Most published advice assumes a program office and a platform team; a smaller company needs neither. One owner of the plan, one monthly review and one owner per workflow cover every line of the checklist. You can check the whole company by asking each team lead the four questions above in one review. How new hires learn the AI workflows their role runs shows how a new person starts.

Hold your company against the picture.

The picture of a good first year starts with a plan. How organizations plan their use of AI walks through the three steps that get you there: plan it, develop the workflows, deploy them. FullyPowered AI is a better way to do all three.

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 colleagues add their own teams. The first line of the checklist, one plan for every team, is where the other eleven start.