The Value Creation ProtocolContents
Part V — Putting it to work
Chapter 21
Where to start
In a session on AI readiness in June 2026, I was talking about why companies struggle to put people and AI to work together, and I said this:
"And that's why companies are not ready. And no shade there because nobody's ever had to do this before."
If you've read this far and feel behind, that's the sentence I'd like you to keep. You aren't late to something everybody else has figured out. Nobody has had to do this before.
So this chapter doesn't hand you a plan with dates on it. It tells you what the path looks like, how to tell where on it you're standing, and which book to open next.
What this is
Putting this handbook to work follows an arc with four stages. Here is each one in a line.
- Mindset. Seeing clearly. This is where you name the traps you're in.
- Architecture. Designing the target state. What does "done" look like for your organization?
- Activate. Named people using AI on real problems they own.
- Scale. What each person builds becomes shared and governed, so the next person starts where the last one finished. Activate is the change for one person. Scale is the change for the organization.
That arc belongs to The AI-Native Shift. Its four Parts carry these four names, and it gives each one a full treatment. This chapter names the arc so you can find your place. It doesn't teach it again.
What you're working toward at the end is put plainly in the methodology's own promise: an architecture your team can extend without calling us. Done with you, never done for you.
Alongside the stages are three readiness milestones. The stages tell you what kind of work you're in. The milestones tell you how far the change has taken hold.
- Foundation: when core relationships demonstrate the new model works.
- Capability: when teams operate confidently in the new structure.
- Multiplication: when results compound and the change sustains itself.
These are read from trust, not from the calendar. An organization moves at the pace of real readiness. Chapter 19 has the same three milestones for each of the Four Unified Views, read from what people do with the view.
How to tell where you are
Find the description that sounds most like this month.
You're in Mindset if people have begun to ask out loud why you've always done it this way, and the spreadsheets people keep on the side to get their real work done have become something you can talk about in a meeting.
You're ready for Architecture if your team can name which of the Twelve Complexity Traps you're in, using the same words, and can say roughly what each one is costing you.
You're in Architecture if you can answer these, or you're arguing about them productively. What does "done" look like? What should each of the four views show, and for whom? What changes in how we're organized? A strong sign is a leader describing the whole picture without being asked.
You're in Activate if named people are using AI on real problems they own, with real business data, and at least one of them keeps asking for more.
You're in Scale if several people are building on their own without being told to, and the next person who starts inherits what the last person made.
If you see signs from two stages at once, trust the earlier one.
What to do
- Place yourself honestly. Use the signs above. Ask two other people in your company to do the same, separately, and compare.
- Begin with the traps. Go back through this handbook's trap chapters with your team and mark the ones you recognize. Shared words for what's wrong are the first thing you build.
- Draw what done looks like before you build anything. Chapter 19 is how you agree on the views. Chapter 18 is how you decide who holds what. Chapter 3, on the Value Path, is how you say where a customer is.
- Start where the energy already is. Find the person who is already pushing against the handoffs and the side spreadsheets. Start with them, on a real problem they own.
- Remove before you add. Take one barrier out before you put one new system in. An approval nobody needs. A step that exists because of a tool you no longer use.
- Don't skip ahead. The Mindset and Architecture work is what makes Activate possible. There are no shortcuts through it.
- Bring the people who will do the work, and someone with the authority to change things. One person sent off to learn this and report back can't change an organization alone. And without authority in the room, the work stalls afterward.
- Read your milestone from what people do. Don't put a date on it.
- Then open The AI-Native Shift at the Part that matches your stage.
How you know it worked
Each milestone has someone who can tell you it's been reached.
- Foundation. A customer in one of those first relationships tells you, without being asked, that working with you is different now. They're the ones who can say the new way works.
- Capability. Your people do the work in their own work, without the person who taught them in the room, and without waiting on anyone to start. Ask them. They'll know whether they could do it again tomorrow.
- Multiplication. Someone you didn't teach shows you something they built. Then somebody learns it from them.
There's a standard for the point where outside help steps back, and it's worth holding your partners to it. A responsible handoff requires validated, verified capability and its adoption in the actual work of the people concerned, with support they can reach. Delivering artifacts or training alone is not a handoff.
So these don't count: a stage finished on schedule, a strategy document, a training everybody attended. And being independent never means help is withdrawn. It means your people can do the work on their own and still have someone to call.
Where it goes wrong
The SaaS Trap is the first one waiting here. It's defined as fragmenting the context your people rely on, where each rational tool purchase silos the intelligence needed to serve customers. Starting your AI work by buying a tool is that trap with a new label on it. You've begun at Activate with no Mindset and no Architecture under it.
The Managed Services Trap is right behind it. It's defined as building business models on client dependency rather than client capability. From your side of the table it looks like having all of this done for you. If the people who helped you are the only ones who can change what they built, you've been handed a dependency.
The AI Replacement Trap is here too. If the first number anyone asks for is how many roles this removes, the arc has already been bent toward cutting people. It was built to multiply them.
Smaller ones to watch:
- Turning the stages into a calendar. A stage is finished when its signal appears.
- Treating what you built as final. A working system is a starting point.
- Calling it done when the people who built it are the only ones using it.
Read further
- The AI-Native Shift (Book 3) is the full treatment. Part I, Mindset, is Chapters 1 to 4. Part II, Architecture, is Chapters 5 to 8. Part III, Activate, is Chapters 9 to 12. Part IV, Scale, is Chapters 13 to 16.
- A Value-First Guide to Surviving the SaaSpocalypse (Book 1) is the story of why this became urgent when it did.
- The Value Era (Book 0) is the case for value as the thing all of this is for.
- Value Accounting (Book 4) is the handbook for recording, with the person who received it, the value each milestone points to.