AI Adoption Playbook
Stop adding AI to work.
Start rethinking work.
The AI Adoption Playbook shows how to turn AI usage into business impact, one process at a time. Four stages, six rules and a 30-day path for the first process.
The gap
The gains are real. They just do not reach the P&L.
Most people already work faster with AI. Most companies cannot show it in their numbers.
8 in 10
survey respondents say AI has improved their individual productivity.
6%
are AI high performers: they attribute 5% or more of EBIT to AI.
What the 6% do differently
They do not have better models or bigger budgets. They redesign how the work runs.
3 in 4
of these high performers fundamentally redesigned workflows because of AI.
AI adoption is a process challenge.
Most companies treat it as a tooling problem first and a use-case problem second, and stall at both.
Source: McKinsey, The state of AI in 2026: On the road to ROI (August 2026), survey of 1,719 respondents
The process way
Make the process the unit of AI adoption.
An end-to-end process has an owner, a baseline and an outcome. AI is placed on its steps, and measured there.
The common approach
AI added to existing work
- Starts from
- Tools and a growing list of AI use cases.
- Changes
- How quickly people complete existing tasks.
- Result
- Faster work. Same business.
The process way
Work redesigned around AI
- Starts from
- One end-to-end process and its performance.
- Changes
- Which steps exist, how work flows, and who or what does it.
- Result
- AI-first processes. Measurable business impact.
You can only see opportunities if you can see the process.
The framework
One process, one loop: See, Score, Ship, Prove.
Four stages. One continuous cycle. From operational reality to measurable AI impact, with a clear outcome at every step.
- 01
See
How does the work actually run?
You leave with
An owned baseline model
- 02
Score
Where is AI worth deploying?
You leave with
A ranked opportunity map
- 03
Ship
How should the work run with AI?
You leave with
The AI-first process, live
- 04
Prove
Did it move the number?
You leave with
The value case
Six rules
Six rules behind every play.
If a decision breaks one of these, it is the wrong decision. The playbook explains each rule and where it applies.
- 1
Fund processes, not tools
- 2
Three to five, not fifty
- 3
No baseline, no pilot
- 4
Redesign, never bolt on
- 5
Design the autonomy
- 6
Prove it in the P&L, then loop
Scorecard
Seven questions. Is your loop running?
Answer honestly. Each “not yet” is the next thing to fix, and shows which part of the playbook fixes it.
Can we name the three to five processes our AI budget is tied to?
Does each have one owner with authority over design and metrics?
Is there a step-level baseline with volume, cost, time and quality?
Is every AI pilot and agent placed on a specific process step?
Was the flow redesigned before AI went in?
Is the autonomy level of each AI step decided and documented?
Can the owner state the delta against baseline in euros or hours?
The first 30 days
One process through the whole loop in 30 days.
The first cycle ends with measurable improvement, not another pilot report.
Day 1
Choose
Week 1
See
Week 2
Score
Week 3
Ship
Week 4
Prove
Inside the playbook
The framework is here. How to run it is in the playbook.
Nine pages to read in ten minutes, forward to leadership or print for a team workshop.
- p. 02
The gap
Why AI gains do not reach the P&L, and where the effort really goes.
- p. 03
The process way
A use case versus an opportunity, and the two disciplines AI adoption needs.
- p. 04
The framework
One process, one loop: what goes in and what comes out at every stage.
- p. 05
Six rules
What each rule means and which decisions it rules out.
- p. 06
The loop in practice
The plays, the output and the exit test for See, Score, Ship and Prove.
- p. 07
Who does what
Four roles, and the people track and process track side by side.
- p. 08
The first 30 days
Week by week for your first process, plus seven ways adoption stalls.
- p. 09
Scorecard
Seven questions to check your loop, and the sources behind the playbook.
Frequently asked questions
Start with one process.
Read it in ten minutes. Run it in a month.