Your CEO wants an “AI strategy.” Your team is already using ChatGPT in private tabs. The middle — where you actually work as a manager — is stuck in the gap between two slides that don’t match the day-to-day.
One executive says “we need an AI-first culture” in a town hall. The next day your team lead asks whether it’s okay to use Claude to summarise customer calls. The policy document is six months from landing. Nobody is going to write the playbook if you don’t.
Here’s the good news: 30 days is enough to go from “vague pressure to do something with AI” to “my team has a working AI workflow with a real user.” You don’t need a consulting engagement, a vendor licence, or a six-month pilot. You need four weeks of focused work that starts with you, not with your team.
The premise: a manager can run a 30-day AI rollout
Most “AI for managers” content falls into two traps: a 30,000-foot strategy framework that never lands in your week, or a list of 47 tools you’ll never evaluate. Neither is what you actually need.
You need a sequence:
- You get personally fluent with the tools (week 1).
- You map where the real opportunities are on your team (week 2).
- You and your team ship one real AI-augmented workflow (week 3).
- You turn that one workflow into a team-wide habit with a playbook (week 4).
That’s 30 days. After week 4 you’ll have the two things most managers are missing: a working example and a way to scale it. The plan doesn’t deliver “AI strategy.” It delivers the foundation that makes future AI strategy worth writing.
The architecture is the same one AI Productivity — Level 2 is built on: personal fluency → team workflows → repeatable patterns → the jump to AI in Business — Level 4.
Week 1 — Get your own AI fluency first
This is the week most managers skip. They delegate “researching AI” to a single team member and use that person’s output to design the rollout. It almost never works. The manager who has personally used AI for real work makes different, better decisions than the manager who’s only read about it.
Three actions:
Spend five hours using AI for your own work. Not researching AI. Using it. Pick a model — ChatGPT, Claude, Gemini, whichever your company already pays for — and use it for writing, summarising, research, planning. This feels slow for the first day or two. That’s the point.
Build one personal workflow you actually keep. Pick one weekly task — meeting prep, status updates, draft emails, research digests — and rebuild it around AI. Write down the prompt you ended up with. Most managers save 10–30 minutes per week on that task by week two. That’s the wedge.
Read the foundations. You don’t need to become an engineer. You need to know what an LLM is, what a token is, what a context window is, what RAG is, what an agent is. Each term takes about five minutes. Our AI Terms Glossary is a fast walkthrough, and AI Foundations — Level 1 is the structured version if you prefer modules.
By the end of week 1 you should be able to answer two questions:
- Which AI tasks am I bad at that the tool is also bad at? (Wrong places to start.)
- Which AI tasks am I bad at that the tool is good at? (Right places to start.)
That distinction is the manager’s actual superpower.
Week 2 — Map your team’s real work
Don’t start with AI. Start with a workflow audit. One wall, about 30 minutes. You’ll get more out of it than any vendor demo.
Get a shared doc or a whiteboard. List every recurring task your team does — weekly status reports, customer responses, code reviews, research briefs, meeting notes, call prep, anything that recurs. Drop each into one of three columns:
- High-yield, low-risk. Drafts, summaries, research, anything internal and reversible. Week 3 territory.
- High-yield, higher-risk. Customer-facing, regulated, anything legal or financial. Real ROI, but needs guardrails. Month 2+.
- Low-yield or skip. Strategy work, conversations, judgment calls. Don’t optimise these in the next 90 days.
Don’t audit everything. Audit the top 10 by hours-per-week — the top 10 will consume 70–80% of the team’s weekly hours.
Three outputs from week 2:
- A ranked list of the three highest-yield, lowest-risk candidates.
- A rough time-baseline for each. “Status reports take 4 hours per person per week.” Without this number, you’ll never know if week 3 worked.
- A one-line risk-read for each. “What goes wrong if the AI gets this wrong? Who notices?” Anything where the answer is “we don’t know until a customer complains” is month 2+, not week 3.
Without the map, you’ll pick whatever the loudest person wants to pilot. With it, you’ll pick the highest expected value and lowest blast radius.
Week 3 — Ship one real workflow, end-to-end
By Friday of week 3, your team should be using AI for one specific workflow, daily, on real work, with measurement. Not piloting. Shipping.
What “ship” means:
- A named team member is using the workflow on real deliverables
- There’s a before-and-after measurement — time, quality, throughput
- Someone other than you owns the workflow, so it survives your vacation
- Prompts and steps are documented, even roughly, so a new hire can pick it up
The most common trap here is the eight-week “pilot.” Pilots drift. A bad draft that gets iterated is better than a perfect strategy that lives in a deck.
Three guardrails:
Pick the workflow where your domain knowledge is deepest. If you’re leading a support team and AI drafts customer responses, you can spot the bad draft from across the room. If you’re leading a finance team and the first workflow is in marketing copy, you can’t. Pick where your judgment is most reliable.
Limit the first workflow to one person. One person using it daily for a week produces more signal than four people trying it once each. After a week, expand. “Everyone tries it once” always ends with nobody accountable.
Write the prompt down, every time. When your person finds a prompt that works, document it. When they find one that doesn’t, document that too. This is the seed for the week 4 playbook.
Identifying opportunities, building the case, shipping, measuring — that’s what AI in Business — Level 4 covers as a complete framework. If week 3 makes you realise “we’re going to do this more than once a quarter,” Level 4 is the structured next step.
Week 4 — Roll out, write the playbook, move up
By week 4 you have one working workflow with a real user. The job in week 4 is to make it bigger than you.
Write the team’s AI playbook. Two pages max. Three sections:
- Prompts that work. The exact prompts your team’s first workflow runs on.
- Prompts that don’t work. The ones that produced bad outputs, with a one-line note on what went wrong. This list matters more than the first — it tells the team what not to assume.
- Rules of the road. What data can go into an AI tool. What can’t. What gets reviewed. What’s an instant rollback. Keep this short.
Run a 30-minute team session. Walk through the playbook. Demo the working workflow. Answer questions. Don’t onboard the team to all AI in one session — onboard them to the one workflow that works.
Identify the second workflow. Not the next one in priority — the one where someone on the team is now ready to own the rollout because they watched the first one work. That’s your week 5+ candidate.
Move from “tool use” to “team skill.” The goal isn’t a bunch of individuals using ChatGPT. It’s your team doing 10–30% more work, or better work, with AI as a normal part of operations.
If the playbook work is what excites you — turning personal AI use into team-level capability — AI Productivity — Level 2 is built around this jump, with reusable team-rollout patterns.
What NOT to do (the four traps)
Most AI rollouts at the manager level fail in predictable ways. Four to actively avoid:
Trap 1 — Treating it as an IT project. Buying licences, writing an acceptable-use policy, and circulating a vendor deck before anyone has personally used AI for real work. Order matters: experiments first, policy second. Teams that write the policy first end up with policies nobody uses.
Trap 2 — The single AI champion. Putting one person in charge of “AI for the team” and waiting for them to deliver strategy. This concentrates learning on one person and makes AI feel like their thing. Better: the champion runs the experiments, every workflow is owned by the person closest to the work.
Trap 3 — Pilots that never ship. “Let’s run a four-week pilot with a small group, measure adoption, then decide.” Pilots drift. If you must run a pilot, give it a hard end date and a named owner — otherwise it becomes permanent.
Trap 4 — Chasing model releases. Every Tuesday a new model drops. You don’t need to chase them. Pick a default model, get good at it, switch only when there’s a clear reason. The biggest gains come from workflow discipline, not the marginal difference between last week’s model and this week’s.
The 30-day manager checklist
Use this as your weekly check-in. Or send it to a peer. Or print it.
Week 1 — Fluency
- Spend at least 5 hours using AI for your own real work
- Build one personal AI workflow that saves you 30+ minutes per week
- Read the foundational resources (the glossary, or one module of Level 1)
- Be able to name which AI tasks you’re bad at that the tool is also bad at — and vice versa
Week 2 — Map
- Audit your team’s top 10 recurring tasks (one doc, 30 minutes, three columns)
- Pick the three highest-yield, lowest-risk candidates for AI
- Estimate a time-baseline for each candidate (hours per week per person)
- Document a one-line risk-read for each candidate
Week 3 — Ship
- Pick one workflow from your shortlist and build it for real
- Pick one team member who’ll own it daily for the first week
- Measure before/after (time, quality, throughput — your choice)
- Document the prompts and steps, even roughly
Week 4 — Roll out
- Write the team’s AI playbook (two pages max)
- Run a 30-minute team session to walk through it
- Pick the second workflow to ship in week 5+
- Identify the team’s AI risk rules and circulate them
Anything left unchecked at the end of 30 days is your week 5+ agenda. Most teams finish with two or three items unfinished — that’s exactly the right place to be.
What comes after the 30 days
The 30-day plan gets you to one working AI workflow and a team that’s used the playbook once. Three things matter after:
Move from individual productivity to team workflow. AI Productivity — Level 2 is built around that jump, with reusable team-workflow patterns you can adapt.
Move from team workflow to business strategy. Once your team has working AI workflows, the next question is “which business problems should AI solve next?” That’s use case identification, build vs. buy, governance, ROI measurement. AI in Business — Level 4 covers how to run that conversation without it becoming a 60-slide deck.
Move from tactics to leadership. Eventually the conversation shifts from “what’s working?” to “what’s our position?” That’s Executive AI Strategy — Level 5 territory: ownership, budget, risk appetite, talent, the operating model that turns team wins into org-wide capability.
You don’t need to plan the whole journey on day one. You need 30 days of running it.
Have questions about the workflow audit, the playbook format, or the team session? Tell us — manager-specific follow-ups are on our content roadmap.