Your 90-Day AI Fluency Plan
Turn the course into a concrete 90-day plan: get visibility, build shared practice, pilot one workflow, and set up the habits that keep your team's AI use improving.
Three Phases
You don’t need to do everything at once. A 90-day plan in three phases moves a team from scattered to shared practice without overwhelming anyone.
- 1 Days 1–30: See
Snapshot, existing rules, workflow maps
- 2 Days 31–60: Share
Policy, shared instructions, review tiers, pilot starts
- 3 Days 61–90: Scale
Review pilot, train team, set the review rhythm
Days 1 to 30: See
- Run the AI use snapshot (Lesson 1.1) and share the summary with the team.
- Gather existing organizational policies, legal requirements, and contracts (Lesson 3.1).
- Map two or three key workflows with AI fit, checkpoints, and skill-building steps (Lesson 1.2).
- Identify AI champions.
- Address urgent risks right away. If confidential data is going into unapproved tools, fix that now rather than waiting for the policy.
Days 31 to 60: Share
- Draft, review, and roll out the one-page team AI policy (Lesson 3.1).
- Build the first shared instructions and definitions of done (Lesson 2.1).
- Set review tiers for your team’s AI-assisted work (Lesson 2.2).
- Run a fairness check on any AI use that touches decisions about people (Lesson 3.2).
- Start one pilot, with baseline measures (Lesson 4.1).
Days 61 to 90: Scale
- Review the pilot against its measures, and decide: scale, adjust, or stop.
- Run team training using real workflows and the four competencies.
- Hold a blameless review of any AI incidents or near-misses.
- Set a standing rhythm: quarterly review of policy and shared instructions, and a regular agenda slot for AI wins and problems.
- Choose the next workflow to pilot.
Keep It Going
After 90 days, AI fluency becomes part of how the team operates:
- Regular check-ins: a few minutes in team meetings for what’s working, what isn’t, and what changed.
- Living resources: shared instructions and the policy updated on schedule, with named owners.
- Skill development: new team members trained on the team’s practices, and junior staff given real opportunities to build the expertise that review depends on.
- Your own modeling: keep using AI visibly and well, including showing what you checked and when you chose not to use it.
Common mistake: writing a thorough 90-day plan, sharing it once, and then letting day-to-day work take over.
Put the plan’s milestones in your calendar and your team’s meeting agenda. Give each item an owner and a date. A short plan that actually happens beats a perfect one that doesn’t.
- Using the three phases, write your team’s plan. For each item, add an owner and a target date.
- Adjust it to your situation: skip what you’ve already done, and add anything specific to your team or industry.
- Identify the single biggest risk to the plan (time, buy-in, unclear rules, tools) and one way to reduce it.
- Ask an AI assistant (approved tool, no confidential details) to critique it:
Here's my 90-day plan to build AI fluency on a team of [size] in [field]. As an experienced change-management coach, point out what's unrealistic for the timeframe, what's missing, and which item I should do first if I can only do one. - Revise, then share the plan with your team and ask for their input.
1. What should happen in the first 30 days of the plan?
You can't set good direction without seeing current use and constraints. Urgent risks shouldn't wait for the policy.
2. You discover in week one that a team member regularly pastes client data into a personal AI account. What should you do?
Urgent data risks need immediate action, handled constructively. The full policy can follow.
3. What keeps team AI fluency improving after the first 90 days?
Fluency is maintained through regular practice and review, not a single launch.
Up Next
The course challenge tests your judgment on realistic team scenarios and asks you to finalize your plan.