The short answer.
AI fits into a new leader’s first ninety days through the listening you already have to do. In your first weeks you ask each person what they do, what repeats and what gets stuck; write those answers down as the team’s work and you have the first half of an AI plan. Then find what people already do with AI on their own, pick one piece of repeat work to hand to AI with the team’s best person, and put the plan on one page before your ninety days are up.
A new leader has an advantage here: nobody expects you to defend the old way. A plan for a team is one part of a company’s plan, and How organizations plan their use of AI sets out the whole method: plan it, develop the workflows, deploy them.
Your first one-to-ones are the plan’s inputs.
The one-to-ones every new leader holds in the first weeks already collect what an AI plan needs: the work each person does, how often it happens and where it gets stuck. Write them down in one place, by team and by role, and the listening becomes a plan.
- Teams first.List the teams you now lead and who leads each one. A team shares its work, its records and its standards, so most of the plan is settled at the level of the team.
- Then roles.Inside each team, name the roles for the work, such as intake, scheduling or month-end close, never for a person.
- Then the work that repeats.For each role, the pieces of work done the same way every week or month. Repeat work is where workflows go.
- Then where work gets stuck.The handoffs between people and teams, where something waits for a missing fact or a second look.
How do I find out what the team already does with AI?
You find out what a team already does with AI by asking each person to show you, on their own screen, the last piece of work they used it for. A demonstration tells you more than a survey: which assistant, what they gave it, what came back and what they changed before it went anywhere.
Expect to find a few people using ChatGPT, Claude, Copilot or Gemini every day, most using it now and then, and each person with their own tricks. That experimenting was the right way to start, and the people doing it are your best source. What is usually missing is direction: the use is undirected, so the best tricks stay with one person and nobody can say which work AI is meant to prepare. What happens when a company uses AI without a plan? describes where that leads.
Ask without judgment, and write down each use next to the piece of work it serves. Those notes show you where AI already helps and who already knows how.
What should I change first?
Change one piece of repeat work first: the one that happens often, starts from records someone can export, already has one person who reviews it, and costs little if a draft is wrong before that person checks it. Hand it to AI as a workflow, built with the team’s best person at that work.
- Pick the work, not the tool.The team already has an assistant. The first decision is which work it prepares.
- Build it with the best person.Capture how the person who does the work best does it: what they start from, the order they work in, what they check and what good looks like. That person owns the workflow and decides on every output.
- Test it on last month’s work.Run it on cases where the right answer is already known and record every miss before the rest of the team uses it.
We have a plan. How do we build the first AI workflow? walks through the build. The free workflow templates in the Workflows Directory are samples and a starting point, and we can build any workflow with you in a 3-Day Workflow Sprint.
Questions for your first one-to-ones.
Copy these questions into your notes for each one-to-one. Every answer goes straight into the plan, under the heading in brackets.
- What does your week look like, start to finish?(The role and its work.)
- What do you do the same way every week or every month?(The work that repeats.)
- What does that work start from: an email, a form, an export, a file?(The workflow’s inputs.)
- Who checks your work before it goes out, and what do they look for?(The person who decides.)
- Where does your work wait on someone else, or someone else wait on you?(The handoffs.)
- Show me the last thing you used AI for. What did you change before using it?(What the team already does.)
- Who on the team is best at the work you do most?(Who builds the first workflow.)
- If one piece of your repeat work arrived prepared, which would you pick?(What to build first.)
Ask the leaders of each team to use the same questions with their own people. Build your AI plan with the people who do the work shows how to bring each team into the plan.
One new leader’s ninety days.
Illustrative example.
Take a 75-person property management company that has just hired a director of operations. She leads four teams: leasing, maintenance coordination, accounts and resident services. In her first month she holds a one-to-one with each team lead and with two people from each team, using the questions above, and writes the answers on one page by team and role.
The one-to-ones show her that two people in leasing already use the company’s assistant to draft replies to rental inquiries, each in their own way, and that maintenance coordination writes a work order from every resident request by hand. She picks the work order as the first workflow. The team’s most experienced coordinator owns it, approves every work order before it goes to a vendor, and tests the workflow on last month’s requests before the rest of the team uses it. The leasing replies go on the plan as the next workflow, built from what the two people already do. Before day ninety the page lists the four teams, their roles, the work that repeats in each, the first workflow and its owner, and the handoff from resident services to maintenance as the place work gets stuck. She reviews it with the owner on the first Monday of each month.
What is different in a company of under 200 people.
Most advice for new leaders is written for large companies, where the first ninety days are spent learning a structure. In a company of under 200 people you meet nearly everyone who does the work.
- You hear from the people who do the work.Your one-to-ones reach the person who writes the work order, not a layer of managers describing it.
- You can cover every team you lead.A large company pilots in one division. You can give each of your teams its first workflow on the same page.
- You start with the AI the company already pays for.No platform decision comes first. Workflows run in your company’s own ChatGPT, Claude, Copilot or Gemini, on your account, run by your people.
- Ownership is a name, not a department.Who should own AI in a company your size? sets out who owns the plan when there is no AI team.
A plan on one page by day ninety.
By day ninety a new leader’s AI plan lists the teams, their roles, the work that repeats, the first workflow with its owner, and what comes next. That page is also the clearest account of your team for the people you report to. The first 90 days of an AI adoption plan sets out the same period from the company’s side.
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. Your team leads add their own teams, so the plan you started in your one-to-ones becomes the team’s plan.