The short answer.
You manage AI across teams by keeping one plan and one record. The plan shows every team, its roles and the workflows each team runs; one person owns the plan, one person owns each workflow, and the current version of every workflow lives in one shared place. Central does not mean a committee that approves everything: the centre holds the plan, the rules and the record, and the teams hold the work.
This is the planning half of How organizations plan their use of AI, applied to a company with more than one team. FullyPowered AI is a better way to manage it centrally: plan your use of AI, develop the workflows and deploy them, all from one plan.
Every team doing its own thing is the default.
Every team builds its own prompts and tools because nobody has said what the company is doing with AI. Seats of ChatGPT, Claude, Copilot or Gemini arrive, each person finds their own tricks, and each team lead solves the problems in front of them. That is what happens without a plan.
Teams doing their own thing costs you three things.
- The same work is solved five ways.Finance, sales and client service each write their own way to summarise a customer account. Five prompts, five standards, five sets of mistakes, and no one knows which is best.
- Nothing is reusable.A good prompt lives in one person’s chat history. When that person changes role or leaves, the method leaves with them, and the next person starts from nothing.
- Nobody can say what is in use.Ask which workflows the company runs, who owns them and what information goes into them, and no one can answer. Leadership knows the money is spent and cannot say what it bought.
Four things are managed centrally.
The company manages four things from the centre, and only four. Each has one owner, by name, who is usually the person who owns the plan.
- The plan.One page, or one Planner, that lists every team, the roles in each team and the workflows each team runs or will run. Teams first, then roles, named for the work and not for a person. An AI org chart should show the work between teams shows how to draw the handoffs between them.
- The approved assistant and the rules.Which assistant the company uses, on whose account, what information may go into it, and that a person decides before anything is sent, paid or changed. Two paragraphs are enough.
- The record of workflows and their owners.One entry per workflow: which team runs it, who owns it, where its current version lives and when it was last reviewed. The record is how anyone in the company can say what is in use.
- The order of what is built next.Which workflow each team develops now, which comes next and which waits. The centre settles the order so that two teams never build the same thing at once, and work that crosses teams gets built once.
Three things stay with each team.
Each team keeps control of its own work, because the team knows it best. Central management of AI stops at three lines.
- How the work is done.The team writes its own best method into the workflow: what it starts from, the steps, what good looks like. The centre does not rewrite a team’s method.
- Who checks.The team names the person who reviews each output and decides. A workflow prepares; a person in the team decides.
- When a workflow changes.The workflow’s owner, inside the team, decides when the workflow changes and approves each new version. The centre only asks that the record says so. Who owns an AI workflow after the pilot? sets out the roles around one workflow.
Nobody waits for a committee. A team that wants a new workflow asks the owner of the plan to put it in the order, and builds it when its turn comes.
The workflow record to copy.
The workflow record is one entry per workflow, with the same eight headings every time. Copy these headings into a document or spreadsheet and fill one entry for each workflow your company runs today.
- Workflow.The name of the work it prepares, such as “month-end close checklist”.
- Team.The team that runs it. If several teams run it, list each one.
- Roles that run it.The roles that use it each week, named for the work.
- Owner.One person, by name, who keeps it current.
- What it starts from.The records, exports or documents it reads.
- Who decides.The role that reviews each output and approves it.
- Status.Planned, in development, in use or retired.
- Last reviewed.The date of the owner’s last check, and where the current version lives.
An entry with a blank owner or a blank “who decides” is the first thing to fix.
The monthly review.
The owner of the plan reviews the plan and the record once a month, in under an hour, with the lead of each team. The review asks the same four questions every month.
- Is each workflow in use?Status says “in use” only if the roles listed actually run it.
- Is each workflow still current?Any entry not reviewed in three months goes back to its owner.
- Is anyone building the same thing twice?Two teams solving the same work agree on one workflow and one owner.
- What is next?The order is updated, one new workflow per team at most.
Central management stays light this way: one hour a month, one page, decisions made in the room.
One company, one plan, one record.
Illustrative example.
Take a 60-person distributor with five teams: sales, customer service, purchasing, warehouse and finance. Sales and customer service had each written their own way to answer a customer asking where an order is. The operations director owns the plan. At the first review she puts both on the record, and the two leads agree on one order-status workflow, run by both teams and owned by the head of customer service, with the customer service lead deciding each reply. Finance’s supplier statement check goes on the record as in development, owned by the controller. Purchasing asks for a reorder summary; it goes in the order as next. Everyone can now see what the company runs, who owns each workflow and what comes next.
What is different in a company of under 200 people.
Most advice on managing AI centrally is written for large enterprises: a center of excellence, a governance board, a platform team. A company of 20 or 150 people does not need any of them.
- The centre is one person.The head of operations, the chief of staff or the owner holds the plan and the record. No board.
- Every team lead is in the review.You can fit all of them in one room for one hour.
- The rules are two paragraphs.Which assistant, what may go into it, who decides.
- The whole company fits on one record.You can list every workflow in use on a single page and see the duplicates at a glance.
That is where 10X the ROI of your existing AI comes from in a smaller company: the seats you already pay for, pointed at agreed work, with no duplicated effort. Build your AI plan with the people who do the work shows how to bring each team in.
Where to keep the plan and the record.
A first plan and record fit in a document or a spreadsheet. They strain when several teams edit them, when one workflow belongs to several teams and when you want to see every role that touches one piece of work. FullyPowered Planner is where the plan lives after that: you set out your teams, their roles and the work between them, choose what to build first, and your colleagues add their own teams to the same plan.
When you are ready to develop the workflows, we build them with your teams in a 3-Day Workflow Sprint or a 2-Week Workflow Sprint, and they run in your own assistant, on your account, run by your own people. The FullyPowered Enterprise Console, for managing releases and rollout across a company, is coming soon.