# The enablement plan

By Tommy Magee

Type: Framework
Canonical: https://tommymagee.com/resources/enablement-plan

How to level up your subject matter experts: go wide and shallow, give people room to build, grow champions, and add a council as building takes off.

**Use this when:** You’re a larger organization trying to get hundreds of people using AI, not just a few enthusiasts.

## Why it exists

Your technical people can’t deliver all of AI’s productivity gains on their own. The biggest gains come from subject matter experts who know the work and learn to apply AI to it. But a one-off workshop doesn’t change how anyone works. People leave excited, then go back to their day job with no time, no goal, and nobody to build with.

## The framework

1. **Go wide and shallow: Can everyone get off the ground?** Have an AI expert build the curriculum in levels, like college courses, from 100 to 400. Start with the 100s and early 200s: ways of thinking, how to use AI, the jargon, and basic skills. Reach as many people as you can.
2. **Find and pair champions: Who is ready to go further?** Your first champions show up fast. Some already use AI well in their personal lives and find the 100-level courses too basic. Put people in pods with a champion. It works as train the trainer and as a creative peer exercise.
3. **Give people space to build: Do people have the time and a goal?** Make room on the calendar and in people’s heads. Set challenges around outcomes, not a weekly slot: “You have a month to find a problem, show me how you’ll solve it, and how AI helped.” Don’t dump Legos on the table and ask for a cake. Ask for something with a tangible result.
4. **Form an AI business council: Who decides what gets built?** As courses get more technical and people build more, tools multiply. Many overlap, and some contradict each other. That’s an acceptable price for adoption. The council manages it: prioritizing, guiding what should and shouldn’t be built, sorting outputs by complexity, and deciding how teams may need to reorganize around new skills.

## The curriculum

- **100, Introduction:** How to approach AI: ways of thinking, the jargon, first uses.
- **200, Personal productivity:** Using AI to improve your own work and your team’s.
- **300, Applied AI:** Automation, advanced applications, and running parts of the business with AI.
- **400, Agent development:** Building agents, and tuning and evaluating agent harnesses.

## How to use it

1. Get an AI expert to own the curriculum, and lay it out in levels from 100 to 400.
2. Start wide and shallow with 100-level courses. Watch for the people who are already past them.
3. Make those people champions, and pair everyone else with them in pods.
4. Give pods dedicated time and an outcome to deliver, such as a month to find a problem and show how AI helped solve it.
5. Add more technical courses as people mature, and form an AI business council once building takes off.
6. Keep it visible for months to raise awareness and adoption: regular communication, recognition, demos, case studies, and show-and-tells.

## A typical first six months

- Month 1: pick an owner for the curriculum, run the first 100-level sessions, and watch for people who are already past them.
- Month 3: champions are named and pods are formed. Each pod has time on the calendar and an outcome to deliver.
- Month 6: early tools are in use, show-and-tells are regular, and the council has met to sort what was built.
- This is a typical shape to adjust, not a record of what any one organization did.

## Challenges worth setting

- You have a month to find one task your team repeats every week, show how AI helped, and show what you stopped doing.
- Pick a report people assemble by hand and get it produced without anyone retyping the data.
- Find a question your team keeps asking the same expert and build something that answers it, with the expert checking.
- These are examples. Good challenges name a tangible result and a deadline, not a topic.

## In practice

At Rivian I trained hundreds of people, most of them personally, and created AI councils and a champions program alongside the training. Champions got mentoring, building kits, and a tool registry that made ownership visible. The training got people started, and it also showed us who was ready to build.

## Where it breaks down

This takes months and a lot of communication, not a launch event. Expect tool sprawl. It’s a sign of adoption, not failure, but only if the council manages it rather than becoming a gate that shuts building down. And training without objectives produces enthusiasm without results.

## Try it with AI

```
Help me design an AI enablement plan for an organization of [size] people.

Work through four parts:
1. Curriculum: what belongs in our 100 (introduction), 200 (personal productivity), 300 (automation and applied AI), and 400 (agent development) courses?
2. Champions: how will we spot people who are already past the basics, and how will we pair them with others in pods?
3. Space to build: what outcome-based challenges could pods take on, such as a month to find a problem and show how AI helped solve it?
4. Council: when should we form an AI business council, who should sit on it, and what should it decide?

Ask me one question at a time about our organization first. Then propose a phased plan for the first six months, including how we'll keep it visible through demos, recognition, and show-and-tells.
```

Topics: AI enablement, AI training, AI champions, AI councils
