The Value Creation ProtocolContents
Part II — The two foundational traps
Chapter 4
How to read a trap
I've referred to the traps in different ways, from different angles, like the SaaS Trap, the B2B Trap and the Measurement Trap, just to try to help people break free of the infrastructure that has been causing KPIs to make decisions instead of common sense.
Nobody chose to be in one. Each trap was built out of reasonable decisions, one after another, by people doing their jobs well. That matters for how you read the next twelve chapters. You are not looking for who got it wrong. You are looking for what the setup around you has been deciding on your behalf.
What this is
The Twelve Complexity Traps, as the methodology defines them:
Twelve named ways industrial-age thinking quietly makes an organization more complex and less human.
They come in two kinds.
Two are foundational: the B2B Trap and the SaaS Trap. "These two traps represent the systemic conditions that make all other traps possible. They must be understood first." They are Chapters 5 and 6.
Ten are core framework traps. These are specific forms the same thinking takes, in AI, in how people are brought in, in content, in delivery, in systems, in measurement, in culture and in leadership.
Every trap is paired with exactly one way out, called its Value-First alternative. The pairs don't mix.
| Trap | Value-First alternative |
|---|---|
| The B2B Trap | Value-First Customer |
| The SaaS Trap | Value-First Context |
| The AI Replacement Trap | Value-First AI |
| The Leads Trap | Value-First Humans |
| The Advertising Trap | Value-First Communication |
| The Lead Magnet Trap | Value-First Content |
| The Qualification Trap | Value-First Partner |
| The Managed Services Trap | Value-First Delivery |
| The ERP Trap | Value-First Platform |
| The Measurement Trap | Value-First Measurement |
| The Conformity Trap | Value-First Culture |
| The Authority Trap | Value-First Leadership |
The alternatives belong to a set the methodology calls the Value Realities. Their job is to be the "what to do instead" once you recognize a trap you're caught in.
The methodology uses the word Trapped for the state these chapters describe, and it treats it this way: "Trapped is a diagnostic state, never an accusation — trapped thinking made sense in its original context." And the purpose of naming a trap at all: "The point is not to shame the old way; it is to name what it is costing you so you can choose differently."
How a trap chapter uses the six parts.
- What this is. The trap's definition, exactly as the methodology states it, and the name of its Value-First alternative.
- How to tell where you are. The trap's signs. Things you can go and look at.
- What to do. The moves toward the alternative, in order.
- How you know it worked. What the person the trap was acting on says or does afterward.
- Where it goes wrong. The traps next door, and the ways the fix gets pulled back into the trap.
- Read further. Where the other books take it deeper.
How to tell where you are
Read by the signs, not by the titles. The trap whose name bothers you most may not be the one you're in. Go to the second part of each chapter and see what you can actually point at.
A sign counts when you can attach something real to it. A name. A screen. A meeting that happened this week. "We probably do that" is not a sign yet.
Expect company. It is rare for only one trap to be present, because they hold each other up. This is the methodology's own map of how:
- B2B Trap enables all other traps by establishing object-based thinking as normal
- SaaS Trap fragments the context needed to escape other traps
- Leads Trap and Qualification Trap work together to dehumanize early relationships
- Advertising Trap and Lead Magnet Trap compound to destroy trust at first contact
- Measurement Trap makes all other traps harder to see by tracking wrong things
- Conformity Trap and Authority Trap prevent organizations from evolving beyond other traps
- Managed Services Trap and ERP Trap create external dependencies that lock traps in place
- AI Replacement Trap threatens to accelerate all other traps at machine speed
Be careful with your own numbers. Read the Measurement Trap line again. If your reports say everything is fine, that isn't evidence you're clear. It may be the trap that hides the others.
What to do
Read the two foundational traps first. Chapters 5 and 6, even if you came to this book for a different one. The other ten make more sense once you've seen the two conditions they depend on.
Go through the signs with a pen. In each trap chapter, mark only the signs you can attach a real example to. Write the example in the margin.
Choose where to start. Start where it is most acute: the trap with the most real examples beside it. Pick one or two. Don't pick all of them.
Work that chapter's moves with the people who do the work. They already know where the trap bites. In many cases they've built a way to cope with it, and that is information you need.
Check with the person on the receiving end. That is the fourth part of every chapter. Do it before you call anything done.
Then read the traps next door. Use the map above. The one you just worked on was being held in place by its neighbors, and they're easier to see now.
How you know it worked
Every trap acts on somebody. A customer who gets processed. An employee who waits for approval. A client who can't operate without you. A person on the phone who has to explain themselves a third time.
So the fourth part of every trap chapter asks the same question: what does that person say or do now?
A sign going away is not the test. You can make a sign disappear by no longer looking at it. The test is the person noticing, and telling you, or showing you by what they do next.
Where it goes wrong
- Numbering the traps. They have names. A number tells you nothing about the trap, and it starts pointing at the wrong one the first time a list gets reordered.
- Renaming them. Use the exact names in the table. "The CRM Trap" and "the Integration Trap" are not traps in this methodology. The first is the B2B Trap and the second is the SaaS Trap. And there are exactly twelve. If you think you've found a thirteenth, look again. It is almost certainly one of these under a different name.
- Making it an accusation. "You're in the Authority Trap" said to a person is a way to end a conversation. Said about a setup that you're both standing in, it starts one.
- Taking on all twelve at once. That is a program, and programs are how organizations avoid changing.
- Putting the new name on the old practice. A gated form called Value-First Content is still a gate. The alternative is a different way of working, and the person on the other end can tell the difference.
- Treating the foundational two as optional. They are the basis for the other ten.
Read further
- The AI-Native Shift (Book 3), Chapter 2, "The Org Chart Is a Confession," shows the two foundational traps as a picture of an organization. Chapter 3, "The Complexity You've Normalized," walks the twelve as a diagnostic.
- A Value-First Guide to Surviving the SaaSpocalypse (Book 1) tells the two foundational traps as the story of what happened.
- The Value Era (Book 0), in its Part II, describes seven ways that replacements for money fail. That is a different list. Those seven are not these twelve.
- Value Accounting (Book 4) takes the fourth part of every chapter here, asking the person who received the value, and makes it a practice of its own.