The short answer.

Each week the owner of the AI plan does four things, in a fixed order: looks at the workflows in daily use, unblocks the workflow in development, hears one team, and updates the plan. The order matters, because the first three find out what is true and the fourth writes it down. A week where the owner of the plan only edits the page leaves the page looking current while the work behind it drifts.

The weekly routine sits inside the first step of the method, plan it, and keeps the other two moving: develop the workflows, deploy them. Who should own AI in a company your size? settles who holds the plan. How to run a monthly AI review covers the meeting with every workflow owner. This piece is the owner’s own week between those meetings.

Look at what is in daily use.

The owner of the AI plan starts the week by checking that every workflow marked “in use” on the plan is still run by the people in its role. Three signs show a workflow drifting out of use.

  • People run their own version.Someone has copied the workflow and edited it, so the role now runs two versions. Ask the workflow owner which one is current, and retire the other.
  • The record of misses is empty.A workflow in daily use produces misses, and the person who decides notes them. An empty record means either nobody runs the workflow or nobody writes misses down. Both need a conversation with the workflow owner.
  • The input changed.A new export from your accounting system, a renamed column in a spreadsheet, a new form on the website. A workflow that reads a changed input prepares the wrong thing until someone updates it.

The owner of the plan does not fix a drifting workflow. The owner of the plan names the problem to the workflow owner, and the workflow owner fixes it. How to deploy AI workflows to a whole team, and keep them working sets out the routine that workflow owner runs.

Unblock the workflow in development.

The second job each week is to find what is stopping the workflow in development and remove it, or name the person who will. A workflow in development stalls for ordinary reasons.

  1. An input nobody can get.The test needs last quarter’s records and nobody has run the export. Ask who can.
  2. A decision nobody has made.The workflow owner needs to know which version of a form is the real one. The owner of the plan gets the answer from whoever holds it.
  3. An owner with no room.The workflow owner is covering a vacancy or a busy season. Move the date on the plan, or move the work to the next workflow on the list.
  4. Access.The workflow is designed to read from a business system and the account to do it does not exist yet. Ask IT, or whoever handles accounts, this week.

Keep one workflow in development per team at a time. Two in one team split the workflow owner’s attention, and neither reaches daily use.

Hear one team.

The third job is to hear one team each week, in rotation, so every team is heard once a cycle. Hearing a team means one short conversation with its lead, or with the people who run its workflows, about the work and not about AI. Ask three things.

  • What repeats this month that did not last month?A new grant cycle, a new season, a new kind of customer request. New repeating work is a candidate for the plan.
  • Where does work wait?A handoff to another team, an approval, a missing record. Waiting is where the next workflow usually sits.
  • What has the team stopped doing by hand?The answer tells you the workflows in daily use are real, in the team’s own words.

What to ask each team lead about AI has the full set of questions for the first round; the weekly conversation is the short version that follows it.

Update the plan last.

The owner of the AI plan updates the plan at the end of the week, with what the first three jobs found. The weekly update changes only what moved.

  • Status.A workflow moves from development to testing, or from testing to daily use, or back.
  • Dates.A date moves, with the reason written beside it.
  • New work.Repeating work a team named goes on the list for that team, unranked until the monthly review.
  • Owners.When a person changes role, the workflow gets a new owner on the page that week.

Write the reason for every change in one line. The monthly review then reads four weeks of reasons instead of starting from memory.

A weekly checklist to copy.

Copy this checklist and run it at the same point each week. Write “Nothing moved” where nothing did; that is a finding too.

  1. Workflows in daily use.For each one: still run by its role? One version or more? Misses recorded? Any input changed? Name to tell: ______
  2. Workflow in development.Which one, in which team. What is blocking it. Who removes the block, by when: ______
  3. Team heard this week.Team: ______. New repeating work: ______. Where work waits: ______. Stopped doing by hand: ______
  4. Plan changes.Status changes, moved dates, new work, new owners, each with a one-line reason: ______
  5. For the monthly review.One thing to raise with every workflow owner in the room: ______
  6. Next week’s team.The next team in the rotation: ______

One food bank’s week.

Take a 75-person nonprofit food bank with five teams on its plan: warehouse and distribution, partner agency relations, volunteers, development, and finance. The director of operations owns the plan.

Illustrative example.

  • In daily use.Partner agency relations runs a workflow that prepares the weekly order summary for each partner pantry from the inventory export. The director of operations found that the inventory system’s export had gained a new column for donated produce, and the summaries were leaving it out. She told the workflow owner, who updated the workflow and tested it on last week’s orders.
  • In development.Development is building a workflow that drafts the quarterly report for each grant from the distribution records. It had stalled because nobody knew which version of one funder’s report template was current. The director of operations asked the development director, who settled it the same day.
  • Team heard.This week was volunteers. The volunteer coordinator said corporate groups now book weekly through the summer, and each booking needs the same confirmation, safety briefing and shift plan. That went on the plan as new repeating work for the volunteers team.
  • Plan updated.The order summary stays in daily use, with a note on the export change. The grant report’s test date stands. The group booking confirmation goes on the volunteers team’s list, for the monthly review to rank. Next week: finance.

Every workflow at the food bank runs in the assistant it already pays for, on its own account, and a person decides: the agency relations lead reads each order summary, and the development director signs every grant report.

What is different in a company of under 200 people.

In a company of under 200 people, the owner of the AI plan does the weekly routine alongside a full job, so the routine is short and fixed. A large company gives the job to a program office with status reports from every team. You walk to the workflow owner’s desk.

  • One person often owns several workflows.The same lead may own the workflow in daily use and the one in development. Check both in one conversation.
  • The rotation is short.Five or six teams means each team is heard about every month or so, which lines up with the monthly review.
  • Blockers are people, not process.The person who holds the missing answer is usually one message away. Ask this week rather than waiting for the review.

Run the week from one page. 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, so the page you update each week is the page everyone reads. How organizations plan their use of AI covers the rest of the method.