The short answer.
You keep an AI plan from going stale with one short meeting a month. The owner of the plan runs it, and the owner of each workflow attends. For each workflow you ask four questions: is it used, is it useful, what changed around it, and what is next. Then you ask two questions of the plan as a whole: what moves from “next” to “now”, and what did one team learn that another team should take. The meeting ends with the plan updated, the same day.
Without a monthly review, an AI plan becomes a document nobody opens, and AI use drifts back to undirected: each person with their own tricks, and nobody able to say what the seats are for. What happens when a company uses AI without a plan? describes where that drift leads. The review is the habit that keeps the plan in charge.
Who should be in the monthly AI review?
The monthly AI review needs two kinds of people: the owner of the plan, and the owner of each workflow on the plan. Nobody else is required.
- The owner of the plan.One person, by name. In a company under 200 people that is usually the head of operations, the chief of staff or the owner of the business. The plan’s owner runs the meeting, settles the order of work between teams and updates the page. Who should own AI in a company your size? covers how to choose that person.
- The owner of each workflow.The person inside the team who keeps the workflow current and decides when it changes. The workflow’s owner brings the facts: who ran it this month, what they corrected and what changed around it.
- Optional: the lead of a team that is next.When a team’s first workflow is about to start, its lead attends that month to hear what the other teams learned.
Leave out anyone who would come only to listen.
Four questions for each workflow.
Each workflow on the plan gets the same four questions, answered by its owner, in the same order every month.
- Is the workflow used?Who ran it this month, and who on the team did not. A workflow that is installed but not run is a decision waiting to be made: fix what stops people, or take it off the plan. Installed, used or useful? has the sheet that answers this question for a whole team.
- Is the workflow useful?Does the person who checks the output accept it with light edits, or rewrite it? The owner reads the exception log, where users record every case they stopped or corrected, and reports the pattern. The log records cases, never people.
- What changed around the workflow?A procedure, a system’s export, the AI platform or the people who run it. Each one can quietly break a workflow. Keep it working: a workflow in its sixth month shows how an owner catches each kind of change.
- What is next for the workflow?One of four answers: keep it as it is, adjust it and retest, extend it to another role or team, or retire it. The owner proposes; the plan’s owner agrees or sends it back.
Two questions for the plan.
After the workflows, the monthly AI review asks two questions of the plan as a whole.
- What moves from “next” to “now”?The plan lists what is being developed now, what is next and what waits. When a workflow is in steady daily use, its owner has attention to spare, and the next item on the list can start. Start one at a time per team. Attention is what runs out first.
- What did one team learn that another team should take?Name the lesson, name the team that takes it, and name the person who carries it across. How to manage AI across teams without everyone doing their own thing covers the work that crosses teams in more depth.
The meeting ends when the plan is updated: the status of each workflow, any change of owner, the new “now” and “next”, and the lessons with the teams taking them. The plan’s owner makes the changes before the end of the day, so the page everyone opens matches what was decided.
The agenda to copy.
Copy this agenda into your calendar invitation. Keep it the same every month so people arrive with their answers ready.
Monthly AI review.
- Opening, by the plan’s owner.What changed in the plan since last month, and which workflows are on today’s list.
- Each workflow, by its owner.
- Used?Who ran it this month: ______. Who did not, and why: ______.
- Useful?Accepted with light edits, or rewritten: ______. Patterns in the exception log: ______.
- What changed around it?Procedure, export, AI platform, people: ______.
- What is next?Keep, adjust and retest, extend, or retire: ______.
- The plan, by the plan’s owner.
- Now and next.What moves from “next” to “now”: ______. Its owner: ______.
- Lessons across teams.What one team learned: ______. The team that takes it: ______. Who carries it: ______.
- Close.Read back the decisions. The plan’s owner updates the plan the same day: ______ (date done).
One month’s review at a property management company.
Illustrative example.
Take a 120-person property management company with three teams on its plan: leasing, maintenance and accounts. The operations director owns the plan and runs the review on the second Tuesday of each month. Three workflow owners attend: the leasing manager, the maintenance coordinator and the accounts lead.
The leasing manager reports that the applicant summary workflow is run by every leasing agent except one new hire, who has not been shown it. The leasing manager will walk the new hire through it that week. The output is accepted with light edits, and nothing changed around the workflow.
The maintenance coordinator reports that the work order triage workflow is used, but the exception log shows the same correction several times: urgent requests from one building arrive through a new form, and the workflow misses the field that marks them urgent. The decision: adjust the workflow to read the new field and retest it on last month’s requests before the team uses the new version.
The accounts lead reports that the month-end owner statement workflow is in steady daily use. For the plan, the review moves the accounts team’s second workflow, a draft of the late-rent notice for a person to approve, from “next” to “now”. And maintenance’s lesson carries across: leasing also reads a web form, so the leasing manager checks the applicant summary against the current form this month. The operations director updates the plan that afternoon.
What is different in a company of under 200 people.
Most published advice on reviewing AI is written for large enterprises: a steering committee, a governance board, quarterly portfolio reviews. A company under 200 people needs one meeting a month and one page.
- The people who decide are already in the room.The owner of the plan can approve a change on the spot. Nothing waits for the next committee.
- Monthly is the right rhythm.A quarter is too long: in three months a procedure changes, an export changes and an assistant ships a new model. A week is too short to see a pattern in the exception log.
- Lessons travel by name.In a company of 60 or 160 people, the person who carries a lesson from one team to the next is someone everyone knows. Name that person in the review and the lesson arrives.
Keep the plan on the page.
Planning AI is three steps: plan it, develop the workflows, deploy them. A monthly AI review keeps all three current after the first workflows are in use. How organizations plan their use of AI sets out all three steps, with a one-page plan to copy.
FullyPowered Planner is where the plan lives. You set out your teams, their roles and the work between them, and choose what to build first. Each workflow owner sees their part of the same plan, so the monthly AI review updates one page everyone already opens. When a workflow needs more than an adjustment, we can help: Keep it working is our offer for the months after handover.