The short answer.
When you run the company and feel behind on AI, start with one decision, not a hundred. This week, write a one-page plan that names your teams, the first piece of repeat work each team moves onto AI and the person who owns it. This month, build one workflow with one team. This quarter, put that workflow into daily use and choose the next one from the page.
That is the whole method: plan it, develop the workflows, deploy them. You do not need to catch up on everything you have read about AI. You need a page, a first team and an owner.
Feeling behind is common, and experimenting was the right start.
Feeling behind on AI is common among owners of companies under 200 people, and the feeling comes from the gap between what you hear and what you see. You hear that companies are handing whole pieces of work to AI. You see your own people using ChatGPT, Claude, Copilot or Gemini for an email here and a summary there, and you cannot say what the company is getting.
That gap is not a failure on your part. Experimenting was the right way to start: your people learned what an assistant does well and where it slips, and some of them found methods that work on real jobs. After years of experimenting, the next step is different in kind. It is a decision about direction, and only the person who runs the company can make it.
The feeling of being behind is heavy because it has no edges. Behind on what, compared to whom, by how much? A plan gives it edges. Once the page says which three teams start and what each builds first, you are no longer behind on AI. You are on step two of your own plan.
What having no plan costs the company.
Having no plan costs the company clarity, and your people feel that cost before you do. AI use without a plan is undirected, and from the inside undirected use feels confusing and, on a bad week, chaotic.
- People are unsure what is allowed.Some wait for permission that never comes. Others go ahead quietly on personal accounts, and nobody feels comfortable saying so.
- Team leads wait for a direction.Each lead knows AI matters and does not know whether to spend their team’s time on it. So the time goes nowhere.
- Every new tool arrives as a question for you.Each pitch, each article and each colleague’s suggestion lands on your desk, because there is no page to check it against.
- Good finds stay with one person.Someone works out a method that saves the team real effort, and it never leaves their desk.
What happens when a company uses AI without a plan? sets out the cost in the work itself. The cost in people is the confusion above, and a plan settles most of it on the day it is written.
This week: decide on one page.
This week, write a one-page AI plan with your team leads. The page names three to six teams, the lead of each, five pieces of work each team repeats, the one piece each moves onto AI first and the person who owns it.
The plan is the answer to feeling behind, so give it a home. FullyPowered Planner is where the plan lives: you set out your teams, their roles and the work between them, choose what gets built first and name who owns it, and your leads add their own teams. How to write your company’s AI plan in one sitting walks through the meeting that produces the page.
One change belongs in the first week too: anyone using a personal AI account for company work moves onto the company account. Saying so out loud ends the quiet uncertainty about what is allowed.
This month: build one workflow with one team.
This month, one team builds one workflow: its best way of doing one piece of repeat work, written precisely enough that your company’s own AI assistant prepares it the same way every time, and tested on last month’s cases. Choose the team whose work repeats most and whose lead will own the result by name.
- Start from what already works.If someone on the team has a method, that method is the first draft. FullyPowered Studio captures know-how like that as a workflow.
- Start from a template where there is no method.The Workflows Directory holds free workflow templates as samples to adapt.
- Name the person who decides.A workflow prepares; a person checks and decides before anything leaves the team.
We have a plan. How do we build the first AI workflow? covers the writing and testing. If you want the first one built with you, the 3-Day Workflow Sprint does exactly that.
This quarter: put it to work and choose the next.
This quarter, the first workflow goes into daily use across its team, and you choose the next piece of work from the page. Deployed means the whole team runs it in your company’s own ChatGPT, Claude, Copilot or Gemini, its owner keeps it current, and it is on the page with a date.
Then look at the page once a month with whoever owns it. Each review answers three questions: is the first workflow in use, which team goes next, and what has changed. That is a company on a plan, and the feeling of being behind has nowhere left to sit.
A first page to copy.
Copy these headings into a document and fill them in with your leads this week.
- Where we are going.One sentence on what AI should do for the company this year.
- Owner of the page.One person, by name.
- Teams.Three to six, each with its lead.
- Work that repeats.Five pieces per team, weekly or monthly.
- First workflow per team.One piece of work, what it starts from and what it produces.
- Owner of each workflow.One name per workflow, and the person who decides on its output.
- This month.The one team that builds first.
- This quarter.What is in daily use by the end, and the next team.
- Review.The day each month the page is looked at.
One accounting firm’s first quarter.
Illustrative example.
Take a 30-person accounting firm whose managing partner feels behind. Staff use assistants for client emails, two managers have stopped asking whether that is allowed, and every software rep who calls offers an AI feature. In the first week, she sits with the leads of tax, client accounting, advisory and client service and writes one page. Each lead names five pieces of repeat work.
Client accounting goes first, because its month repeats most: the month-end review notes for each bookkeeping client, prepared from the trial balance export. A senior bookkeeper already had a method for those notes, and that method becomes the first workflow, owned by the client accounting manager, who reviews every set of notes before it reaches a client. The firm moves everyone onto the company account that week.
By the end of the quarter, the whole client accounting team prepares its review notes the same way, and tax has chosen its first workflow from the page: the organizer follow-up list for clients whose documents are incomplete. The managing partner reviews the page on the first Monday of each month.
What is different in a company of under 200 people.
In a company of under 200 people, the owner can end the feeling of being behind in a week, because the whole plan is a few conversations away. Most published advice on AI is written for large enterprises, with steering committees and long assessments. You need neither.
- You can make the decision yourself.The direction is yours to set, and your leads are waiting for it.
- One workflow is visible to everyone.In a team of four, one piece of work prepared the same way changes the whole team’s week, and the rest of the company sees it.
Start with the page, and let the page carry the weight. FullyPowered Planner holds your teams, their roles, the work between them and what gets built first. How organizations plan their use of AI covers the rest of the method.