Get the crew working.
Your company bought the AI tools, and most people still use them now and then. This module turns licences into daily habits, with a 30-day plan led by managers and built on real tasks.
- Production
- The adoption gap
- Director
- You
- Crew
- AI
- Take
- 01
- Scene
- 04
- Part
- II
By the end of this module you will be able to:
- Diagnose the five reasons people stop using AI, and the fix for each.
- Contrast a typical launch with the steps that build a habit.
- Run a 30-day adoption plan for one team.
- Check the signs that a rollout is working, and know when to stop and fix.
This module follows the guide section by section. Keep it open as a one-page reference while you work.
Why people stop using AI
Most AI rollouts start with licences and a launch email. A few people take off, and everyone else tries it twice and goes back to the old way. The tools work. What is missing is a reason, a routine and a person to ask.
In a survey of 2,400 executives and employees, 79% of organisations reported challenges with AI adoption. Gartner found 86% of managers struggle to drive AI adoption in their teams, and only 7% of organisations guide staff on how to use the time AI saves.
WRITER and Workplace Intelligence, April 2026; Gartner HR survey, March 2026| Reason | What happens | Fix |
|---|---|---|
| No clear taskPurpose | People are told to use AI without a job for it to do. | Name three tasks per role where AI saves time this month. |
| Weak first resultsBrief | Short prompts return generic drafts, and people decide AI is not useful. | Teach the brief: goal, reader, facts, limits and an example. |
| No company knowledgeContext | The tool knows the world but not your products, clients or style. | Give it approved company material to work from. |
| Unclear rulesRules | People do not know what data is allowed, so they hold back or use tools on the side. | Publish one page of plain rules for every user. |
| Managers not leadingManagers | When managers do not use it, teams read AI as optional. | Managers show one real result in each team meeting. |
Notice that four of the five fixes are about people, routines and rules. Only one involves the tool's content, and Module 5 covers it in full.
Launch versus adoption
A launch is an event. Adoption is a habit. The left column is how most rollouts are run. The right column is what builds the habit.
| A typical launch | What builds the habit |
|---|---|
| Licences announced to everyone | One team and three real tasks first |
| A one-hour tool demo | Short sessions on the team's own work |
| Tips shared by email | A shared library of briefs that work |
| Logins counted | Tasks done with AI counted each week |
| Rules left to IT | One page of plain rules for every user |
Adoption is a people job. It moves when managers pick real tasks, show a good result in the team's own work and make AI part of the normal week.
The 30-day plan
One team, one month. Small enough to run alongside normal work.
- Week 0 · PickChoose one team and three tasks that repeat every week.
- Week 1 · BriefWrite a model brief for each task and test it together.
- Week 2 · SaveStore the briefs that work where the whole team can find them.
- Week 3 · ShowEach person shares one result in the team meeting.
- Week 4 · CountCount tasks done with AI, time saved and where the time went.
Here is the plan run by a marketing team of four, starting with social posts.
- Pick
- Social posts, event emails and one-page sales sheets.
- Brief
- One brief per task, with audience, facts and tone.
- Save
- Briefs kept in a shared folder with a strong sample of each.
- Show
- Two people showed drafts that needed only light edits.
- Review
- The manager approved every post before it went out.
The Week 1 brief is the director's brief from Module 1. The plan is how a whole team learns it.
Five habits of teams that keep using AI
Count the ones your team has. 0 to 1: start the 30-day plan. 2 to 3: add the missing habit next month. 4 to 5: share your approach with another team.
- Same tasks, every week. Repetition turns a trial into a routine.Try it: "These are our three AI tasks this week."
- Shared briefs. Good briefs are reused, not rewritten.Try it: save your best brief for the team.
- Managers go first. People copy what their manager does.Try it: show one AI result at the next meeting.
- People approve. A person signs off anything that goes out.Try it: name who checks each type of output.
- Time goes somewhere. Saved time is planned, not lost.Try it: agree what the saved hour is for.
Signs your rollout is working
Check these at the end of the first month.
- People use it every week.
- Briefs are shared.
- Managers show results.
- Rules are clear.
Keep going when
- People bring new tasks. Let them test one each week.
- Edits get lighter. The briefs are working.
- Questions change. From "how" to "what else".
- Another team asks. Show them the 30-day plan.
Stop and fix when
- Data rules are unclear. Pause and publish them first.
- Results go unchecked. Add a named reviewer.
- Only one person uses it. Pair them with others.
AI drafts, people decide.
Lead from the front.
The fifth reason adoption stalls is managers not leading. Teams read what their manager does, not what the launch email says. If you want a team to use AI, use it first, in front of them, on real work.
Leading from the front also means being in the room when it is hard. Sit with the person whose first draft came back generic and rewrite the brief together. That half hour does more than a training deck.
- Bring one of your own AI results to the next team meeting, including what you changed.
- Run Week 1 of the plan yourself before you ask anyone else to.
- Ask "what did AI save you this week, and what did you do with the time?"
Training that stays close to the work
I present at company AI sessions and run training on each system I build. I stay close to people as they learn, so new tools become part of the day. The training centres on one idea: direct AI the way a director runs a production, with a clear vision, a full brief and a final review. These eight guides grew out of that work.
- Format
- Live sessions, how-to videos and the Director's Chair guides
- Approach
- Real tasks, shared briefs and a named reviewer
Plan your 30 days
Fill in the plan for one team. Keep it small enough to run alongside normal work.
Check your understanding.
Module 4 in four lines.
- The tools work. What is missing is a reason, a routine and a person to ask.
- Start with one team and three tasks that repeat every week.
- Managers go first. Teams copy what they see.
- Count tasks done and where the saved time went, not logins.
Choose your team and three tasks today. Week 0 takes one conversation.
Further reading on my site
Pass the knowledge check to complete this module.