For Leaders Activating AI

AI is not a rollout.
It is a movement
leaders have to activate.

Traditional change management assumes a fixed future state, a tidy plan, and resistance to be managed. AI adoption breaks every one of those assumptions. The path is still emerging, the endpoint keeps moving, and the people closest to the work — not the people closest to the deck — decide whether it lands.

Read the Framework Start Activating
⌄
Emergent paths — architecture as metaphor
The Evidence

The evidence is in. The model is wrong.

Four numbers that explain why every traditional adoption playbook is mispriced for the AI era.

78%
Now use AI at work
Up from 55% the prior year — yet most organizations report no measurable EBIT impact. Tools spread faster than the cultures that absorb them.
McKinsey, State of AI 2024
70%
Of transformations fail
Failure is rarely technical. It traces back to human readiness, leadership behavior, and the absence of meaningful employee participation.
McKinsey & BCG longitudinal studies
75%
Bring their own AI
Shadow adoption is already the norm. Workers aren't waiting for the rollout — they're hacking the future of their job in private.
Microsoft Work Trend Index 2024
25%
Tipping point for movements
Once roughly a quarter of a group commits to a new behavior, social conventions flip. Movements need critical mass, not unanimous consent.
Centola, Science 2018
The Paradigm Shift

The old model was built for predictable change. AI is not predictable change.

It is continuous reinvention. The playbook that worked for ERP rollouts will not work here.

Traditional Change Management

01Define a fixed future state
02Cascade a rollout plan top-down
03Manage resistance as a problem
04Measure adoption against the plan
05Communicate certainty leaders don't have

Movement Activation

01Set direction, leave the path emergent
02Activate the people closest to the work
03Treat fear as signal, not friction
04Measure learning velocity and reinvention
05Make honest uncertainty a leadership act
The Human Layer

The four questions every employee is already asking.

Most quietly. Some out loud. None of them appear on a Gantt chart, and all of them decide whether your AI investment compounds or evaporates.

Concern

Relevance

"Will I still matter?" The question underneath every demo. Leaders who don't name it amplify it.

Concern

Trust

In the tool, in the data, in the intent of the people deploying it. Trust is a precondition, not an output.

Concern

Capability

Skill gaps are visible in real time. People need scaffolding, not slideware, to close them in public.

Concern

Identity

If craft is automated, what is the craftsperson? The deepest work is identity work, not training.

The Five Conditions

Leaders don't roll out AI. They curate the environment.

These are the five conditions that environment requires.

01

Permission to Experiment

Sanction off-roadmap exploration. Make 'I tried this and it failed' a story the organization celebrates publicly.

02

Psychological Safety

Edmondson's decades of research is unambiguous: teams that can speak honestly outperform. Without it, AI surfaces nothing but theater.

03

Rapid Learning Loops

Weekly demos. Public prompts. Shared failures. Treat the org as one nervous system that adapts in days, not quarters.

04

Distributed Ownership

The people redesigning the work are the people doing the work. Leaders convene, fund, and remove obstacles — they do not author the workflow.

05

Identity Work, Out Loud

Hold space for the harder question — what does it mean to be good at my job now? Coaching, not communications, is the unlock.

The Activation Playbook

Nine moves. Start Monday.

No frameworks worth printing on a mug. Just the smallest set of concrete moves that begin to shift the system.

This Week

→Ask your team: what would you automate tomorrow if no one stopped you?
→Share one prompt you used that genuinely changed your output.
→Kill one mandatory training in favor of a 30-minute live demo.

This Quarter

→Fund 10 internal experiments with no required ROI — only required learning.
→Stand up a weekly 'show your work' forum across functions.
→Rewrite one job family description with the people doing the job.

This Year

→Move adoption metrics from license usage to workflow reinvention.
→Promote the people running the movement, not just the people running the plan.
→Publish the org's evolving stance on AI — and update it every 90 days.
"The greatest danger in times of turbulence is not the turbulence — it is to act with yesterday's logic."
— Peter Drucker
Take the Next Step

Stop managing. Start activating.

If this manifesto reframed something for you, share it with the leader who needs to read it next. Movements only move when someone passes the torch.

Get the Activation Playbook