You cannot deploy a culture. You lead one. The concrete moves for the human side of an AI transformation, the part that actually decides whether it holds.
The one idea
AI transformation usually stalls on the people, not the technology. A company can deploy every tool and change nothing, because deploying a tool is not the same as changing how a person works. That change is behavioral, social, and slow, and it is the whole job. You cannot buy it, install it, or announce it. You lead it, deliberately, and you lead it people-first.
This is the playbook for that work. Not the tools. The people.
The moves
Run them in this order. Each is cheap. Together they are how a culture actually moves.
Name it as a culture change, out loud. Before anything else, say the quiet part: the hard, slow work here is changing how people work, not standing up software. Naming it sets the expectation that a rollout is not a transformation, and it stops your team from mistaking motion for progress.
Start with the individual, not the org chart. Find one respected person with one real, small friction, and solve it with them, in the room. Belief travels through people, not licenses. A single credible peer who has felt what is possible does more than any all-hands slide.
Find the ambassador and give them a role. The person that first win converts is your most valuable asset. Name them, back them, and let them carry capability into their own function. A respected colleague who has done it is social proof no central team can manufacture. The Avidity case is this move at company scale.
Teach in person, in small doses. Behavior change is personal, so a memo will not do it. Someone senior sitting with a team for fifteen minutes, answering the real question to their face, changes more than a recorded module ever will. The time you spend is itself the message that this matters.
Make responsible experimentation safe. Handed a new capability, good people default to the most cautious reading and freeze, to be safe. That looks like caution and is really just slow. The freeze breaks when people understand not only the rules but the reasoning: where the real risk lives, and where it does not.
Measure adoption, not deployment. Licenses issued, tools launched, and pilots counted are vanity metrics. They measure your activity, not your company’s. The number that matters is whether behavior changed, and whether the person who would not touch the tool in week one is rethinking their work by week six.
Let the questions refine the rules. The questions people ask when you teach are a map of where your policy is unclear and where the real fear lives. Collect them, answer them, and carry them back to sharpen the policy. A rule you have to explain out loud to a skeptical room is a rule whose weak spots you find fast.
What it is not
This is not a change-management binder, and it is not a slogan. “People first” is not a value on a wall; it is a sequence of concrete, unglamorous acts that a leader does personally. It does not replace the operating model or the tools you route work through. It is the human layer those things exist to serve, the layer where a transformation is actually won or lost.
Monday morning
Pick one person, one small friction, and one week. Solve it with them. Then, when it works, ask them to help the next person, and get out of the way. Teach the next group yourself, in fifteen minutes. Do not measure how many licenses you bought. Measure whether anyone works differently than they did last month. That is the whole game, and it starts with one person.
Sources and further reading
McKinsey, Common pitfalls in transformations, on transformations stalling on the organizational and human side rather than the technology
Everett Rogers, Diffusion of Innovations (5th ed., Free Press, 2003), on why change spreads through respected peers and social proof rather than mandates, the basis for the ambassador move
The worked example: Fifteen Minutes at a Time, an enterprise AI policy taught into behavior, one fifteen-minute session at a time
## The one idea
AI transformation usually stalls on the people, not the technology. A company can deploy every tool and change nothing, because deploying a tool is not the same as changing how a person works. That change is behavioral, social, and slow, and it is the whole job. You cannot buy it, install it, or announce it. You lead it, deliberately, and you lead it people-first.
This is the playbook for that work. Not the tools. The people.
## The moves
Run them in this order. Each is cheap. Together they are how a culture actually moves.
- **Name it as a culture change, out loud.** Before anything else, say the quiet part: the hard, slow work here is changing how people work, not standing up software. Naming it sets the expectation that a rollout is not a transformation, and it stops your team from mistaking motion for progress.
- **Start with the individual, not the org chart.** Find one respected person with one real, small friction, and solve it with them, in the room. Belief travels through people, not licenses. A single credible peer who has felt what is possible does more than any all-hands slide.
- **Find the ambassador and give them a role.** The person that first win converts is your most valuable asset. Name them, back them, and let them carry capability into their own function. A respected colleague who has done it is social proof no central team can manufacture. [The Avidity case](/case-studies/fifteen-minutes-at-a-time/) is this move at company scale.
- **Teach in person, in small doses.** Behavior change is personal, so a memo will not do it. Someone senior sitting with a team for fifteen minutes, answering the real question to their face, changes more than a recorded module ever will. The time you spend is itself the message that this matters.
- **Make responsible experimentation safe.** Handed a new capability, good people default to the most cautious reading and freeze, to be safe. That looks like caution and is really just slow. The freeze breaks when people understand not only the rules but the reasoning: where the real risk lives, and where it does not.
- **Measure adoption, not deployment.** Licenses issued, tools launched, and pilots counted are vanity metrics. They measure your activity, not your company's. The number that matters is whether behavior changed, and whether the person who would not touch the tool in week one is rethinking their work by week six.
- **Let the questions refine the rules.** The questions people ask when you teach are a map of where your policy is unclear and where the real fear lives. Collect them, answer them, and carry them back to sharpen the policy. A rule you have to explain out loud to a skeptical room is a rule whose weak spots you find fast.
## What it is not
This is not a change-management binder, and it is not a slogan. "People first" is not a value on a wall; it is a sequence of concrete, unglamorous acts that a leader does personally. It does not replace the [operating model](/permission-people-programs/) or the [tools](/artifacts/) you route work through. It is the human layer those things exist to serve, the layer where a transformation is actually won or lost.
## Monday morning
Pick one person, one small friction, and one week. Solve it with them. Then, when it works, ask them to help the next person, and get out of the way. Teach the next group yourself, in fifteen minutes. Do not measure how many licenses you bought. Measure whether anyone works differently than they did last month. That is the whole game, and it starts with one person.
<div class="ti-sources">
## Sources and further reading
- McKinsey, [Common pitfalls in transformations](https://www.mckinsey.com/capabilities/transformation/our-insights/common-pitfalls-in-transformations-a-conversation-with-jon-garcia), on transformations stalling on the organizational and human side rather than the technology
- Everett Rogers, *Diffusion of Innovations* (5th ed., Free Press, 2003), on why change spreads through respected peers and social proof rather than mandates, the basis for the ambassador move
- The worked example: [Fifteen Minutes at a Time](/case-studies/fifteen-minutes-at-a-time/), an enterprise AI policy taught into behavior, one fifteen-minute session at a time
</div>