The short answer.

The first month after a company gets an AI plan replaces guessing with knowing: what is being built, by whom, in what order. The leader trades a quiet worry for a short list of decisions. The team leads trade a vague expectation for one named piece of work each. Very little work has moved onto AI by the end of the month, and that is fine; what moves is the feeling in the building, from confusing to clear.

The plan is the first of three steps: plan it, develop the workflows, deploy them. This piece is about what the first step feels like from the inside, week by week.

What the month before the plan feels like.

The month before an AI plan feels busy and unsettled at once. AI use without a plan is undirected, and undirected use has a particular texture. Experimenting was the right way to start, and after years of experimenting most leaders know the feeling well.

  • The leader carries a worry nobody else can see.The seats are paid for. Competitors talk about AI with confidence. The leader cannot say what the company is doing with it, and cannot tell whether that is a problem.
  • Every conversation about AI starts from zero.A team lead raises an idea in a meeting, everyone agrees it sounds good, and nothing is decided, because nobody knows who decides.
  • People are unsure what is allowed.Some use AI for everything and say nothing. Some avoid it because nobody told them they could. Both groups wonder whether they are doing it wrong.
  • Good finds stay hidden.Someone works out a better way to do a weekly task, and keeps it to themselves, half because nobody asked and half because they are not sure it is wanted.

The cost to the organization is real even when nobody names it: attention spent on the same undecided question every month, and repeat work that stays where it was. What happens when a company uses AI without a plan? sets out the pattern.

Week one: the questions get answers.

In week one of an AI plan, the questions that kept coming back get written answers. The leader and the team leads sit down together, each lead brings the work their team repeats, and the room decides which teams start, what each builds first and who owns it. How to write your company’s AI plan in one sitting covers that meeting.

The feeling at the end of week one is relief. The question “are we doing enough with AI?” turns into a page that says what the company is doing, team by team. FullyPowered Planner is where that page lives: your teams, their roles, the work between them, what gets built first and who owns each piece. Colleagues add their own teams, so the plan is not one person’s document.

Week two: team leads stop guessing.

In week two, each team lead knows exactly one thing their team is building, and that is enough to stop guessing. Before the plan, a team lead felt a general expectation to “do something with AI” and no permission to choose. After the plan, the lead owns one named piece of work, such as the weekly client report or the month-end close notes, with a date to look at it again.

The team notices it too. The leader tells everyone what is decided, what each team is asked to do, what stays the same and where to bring ideas. What do we tell employees about AI? has a script.

  • What the leader notices.Fewer AI conversations, and each one ends in a decision.
  • What a team lead notices.One clear job, and the authority to say “that idea goes on the list for next month”.
  • What the team notices.A name to ask, and a place where ideas go instead of disappearing.

Week three: the first workflow is being built.

In week three, the first workflow is being built, and the team can see it taking shape. The owner writes down how the work is done today, what it starts from and what good output looks like. The workflow is developed from that, either by the team or with us in a 3-Day Workflow Sprint, and where the method sits in one experienced person’s head, FullyPowered Studio captures it as a workflow.

The feeling in week three is steadier attention. The team has stopped wondering whether AI will matter to them and started looking at a real draft of their own work. A person still decides; the workflow prepares.

Week four: the first review.

In week four, the owner of the plan holds the first review, and the worry changes shape. The question is no longer “are we behind?” It is “is the first workflow ready, and what goes second?” Those are ordinary management questions.

The review covers each team’s first piece of work, what the team learned, what goes on the plan next and the date of the next review. What does the owner of the AI plan do each week? gives the rhythm after month one.

Questions to ask at the end of the first month.

A plan that is working gives a plain answer to each of these at the end of the first month.

  1. Can every team lead name what their team is building?One piece of work, in their own words.
  2. Does every piece of work have one owner, by name?A name, not a team.
  3. Do people know what is decided and what stays the same?Ask two people outside the leadership team.
  4. Is there one place where AI ideas go?And has anyone used it.
  5. Is the first workflow being tested on real work?Last month’s cases, checked by the person who reviews that work today.
  6. When is the next review?A date in the calendar.
  7. What has the leader stopped worrying about?Write it down. It is the clearest sign the plan is doing its job.

One agency’s first month.

Take a 55-person marketing agency with four teams: creative, account management, new business and finance. Before the plan, the managing director heard about AI in every leadership meeting and could not say what the agency was doing with it.

Illustrative example.

  • Week one.The managing director and the four leads wrote the plan in one meeting. Account management goes first with the weekly client report. Finance goes second with the monthly invoice run. Creative and new business wait, with a date.
  • Week two.The managing director told the whole agency what was decided. Two designers who had been using AI quietly for image briefs asked whether they could keep going. The answer was yes, and their method went on the list for creative’s first workflow.
  • Week three.The head of account management wrote down how the weekly report is built from campaign exports, starting from a free workflow template in the Workflows Directory. The account directors tested drafts against last month’s reports.
  • Week four.At the first review, the account directors asked for one change to the report’s summary section. The head of new business, who had felt left out, asked to move up. The plan said when, and why.

Nothing dramatic happened. The managing director stopped bringing the AI question into every meeting, because the page answered it.

What is different in a company of under 200 people.

In a company of under 200 people, the first month after an AI plan is felt by everyone at once. The plan is written in one room, and the whole company hears the news in the same week.

  • The worry was personal.The leader of a smaller company often carried the AI question alone. The plan shares it with the team leads.
  • The change is visible fast.Teams sit close together, so the second team sees the first team’s workflow before its own turn comes.
  • One person may be a whole team.An office manager can own a workflow in month one as fully as any department.

The first month is where a company moves from AI use that is undirected to AI use on purpose. How organizations plan their use of AI covers the method, and FullyPowered Planner is where you set out your teams, their roles and what gets built first.