The Value Era

Companion glossary

The Language of Value


Who it is for
Anyone mid-chapter who meets a Value-First word and wants it in the book’s exact words, and the builder who wants the vocabulary in one place.
Length
9,134 words, about 40 minutes

This glossary is a companion to The Value Era and the four books beside it. It collects the Value-First words the five books use and gives each one in exact words, never paraphrased, so a word means the same thing wherever you meet it. A link after each definition takes you to the chapter that teaches it.

Every entry carries one of three labels. An approved term is a word our methodology defines and has approved, and it is given in those approved words. Value, the first principle marks the one word that is recognized rather than approved. The book's own word is a word one of the five books defines for itself, and it is given in that chapter's own words.

Where our methodology names a word that an entry replaces, the entry adds a line that begins Say this instead of.

A

Adopter

An approved term

"I realize your value"

Genuine value realization and validation. Using new capabilities and proving success. Optimizing usage and deepening integration.

Taught in The Value Creation Protocol, Chapter 3, "The Value Path".

The Advertising Trap

An approved term

A Core Framework Complexity Trap. Fighting for attention through interruption rather than earning it through value delivery.

Taught in The Value Creation Protocol, Chapter 9, "The Advertising Trap → Value-First Communication".

Advocate

An approved term

"I tell others about you"

Natural sharing within authentic influence spheres. Telling peers about success, beginning internally before extending externally. Organic referral generation.

Taught in The Value Creation Protocol, Chapter 3, "The Value Path".

The AI Replacement Trap

An approved term

A Core Framework Complexity Trap. Believing AI's primary purpose is to replace human workers rather than enhance their capabilities.

Taught in The Value Creation Protocol, Chapter 7, "The AI Replacement Trap → Value-First AI".

AI-Human Partnership over Replacement

An approved term

AI should multiply human capability, not replace it. Technology's highest purpose is to handle mechanical coordination while enhancing uniquely human capabilities like creativity, judgment, and connection.

Taught in The Value Creation Protocol, Chapter 2, "The Five Core Beliefs".

The AI-Native Shift

An approved term

The shift a company makes when AI stops being a tool it adds and becomes the substrate it operates on. A methodology, not a program. It moves through four phases — Mindset → Architecture → Activate → Scale — and what a company leaves with is a working system plus the capability to run and evolve it without us: an architecture your team can extend without calling us. Done-with-you, never done-for-you.

Say this instead of "an AI strategy engagement / digital transformation": you walk away with a working system and the ability to run it yourself, not a recommendations document.

Taught in A Value-First Guide to Surviving the SaaSpocalypse, Chapter 17, "The AI-Native Shift", and walked through the whole of The AI-Native Shift.

Audience

An approved term

"I am learning"

People in the earliest moments of possibility recognition. Casual exploration without pressure to commit. Building general awareness through content consumption.

Say this instead of "lead" or "prospect": the person is still learning, exploring without pressure to commit.

Taught in The Value Creation Protocol, Chapter 3, "The Value Path".

The Authority Trap

An approved term

A Core Framework Complexity Trap. Centralizing control in ways that prevent the distributed intelligence organizations need.

Taught in The Value Creation Protocol, Chapter 16, "The Authority Trap → Value-First Leadership".

B

The B2B Trap

An approved term

A Foundational Complexity Trap. Treating humans as database objects to be processed through stages rather than relationships to be understood.

Taught in The Value Creation Protocol, Chapter 5, "The B2B Trap → Value-First Customer".

Back Into Money

The book's own word

The measure, wherever it is real, ends up as a way of doing business.

It can't turn back into money. If its natural resting place is a price or a pile of points, it was a price all along.

One of the seven ways to fail, named in The Value Era, Chapter 5, "Back into money, gamed on arrival" and set as a test in Chapter 6, "Nobody to use it, nobody to carry it".

Buyer

An approved term

"I am buying"

Actively making purchasing decisions. Building internal conviction and coordinating stakeholders. Navigating organizational dynamics and making the business case.

Say this instead of "SQL": they are making the decision and building the case inside their org — "I am buying".

Taught in The Value Creation Protocol, Chapter 3, "The Value Path".

C

CARE (Confluence, Activation, Relationship, Emergence)

An approved term

CARE is Confluence, Activation, Relationship, Emergence: a practice of "care, intention and the value people experience". The four anchors overlap. They are "questions one can return to, not sequential gates, required fields or CRM stages", and "there is no set order".

  • Confluence: Distinct streams meeting and flowing together. Its question: What is coming together?
  • Activation: Shared understanding becoming something we can do. Its question: What are we trying to make possible?
  • Relationship: What grows as we keep showing up. Its question: Who is this work for?
  • Emergence: What becomes possible together without being fully specified beforehand. Its question: What is becoming possible?

Two records, linked, never substituted. CARE holds intention in a CARE record, kept apart from the record of value, the Value Entry: "These are distinct records of intention and value, not two copies of the same assertion." The question asked across the two is Return on Intention: "Did the value that emerged serve the care behind the work?"

Taught in Value Accounting, Chapter 2, "Say what it's for".

CARE Record (the Record of Intention)

An approved term

A CARE record is the record of intention. A tangible account of intention, in proximity to our records of value: who and what we care about, what we hope to make possible. The value we expect someone to receive is a different thing, and it lives on the Value Entry. Its sections are CARE's four anchors.

Two records, linked, never substituted. "These are distinct records of intention and value, not two copies of the same assertion." Reading across the two records is Return on Intention.

Taught in Value Accounting, Chapter 2, "Say what it's for".

Champion

An approved term

"I am a raving fan"

Industry leadership and methodology co-creation. Building communities of practice and advancing entire methodologies. Strategic partnership and mutual value multiplication.

Taught in The Value Creation Protocol, Chapter 3, "The Value Path".

A clearer view

The book's own word

"I see clearly now."

You understand something you couldn't make out before.

One of the six kinds, taught in The Value Era, Chapter 15, "In its own kind".

Configuration Over Customization

An approved term

The third of VCP's five load-bearing claims. VCP favors configuring native platform capability over customizing bespoke architecture. Custom architecture creates brittle integrations and, more fundamentally, dependency on capability you don't have — whether that's outside consultants, external resources, or AI you can't direct yourself. Configuration leverages platform investment and improves with the platform. This claim is platform-agnostic — it applies to any system serving as the operational substrate.

Taught in The Value Creation Protocol, Chapter 1, "The Value Creation Protocol".

Confirmed

The book's own word

The person who received it says it landed, or, for value received inside the team, the hand our rules name (Chapter 4). Never the person who did the work.

One of the five stages an entry passes through (Expected → Witnessed → Shown → Confirmed → Settled), taught in Value Accounting, "How to use this handbook" and Chapter 8, "Their word".

The Conformity Trap

An approved term

A Core Framework Complexity Trap. Enforcing standardization that suppresses the diversity organizations need to thrive.

Taught in The Value Creation Protocol, Chapter 15, "The Conformity Trap → Value-First Culture".

Context as Substrate

An approved term

The second of VCP's five load-bearing claims. Context is not an input to operations — it is the substrate on which operations run. VCP treats unified context (relationship history, preference signals, prior commitments, current state) as the operating layer that all decisions reference. Fragmented context produces fragmented operations regardless of methodology overlay.

Taught in The Value Creation Protocol, Chapter 1, "The Value Creation Protocol".

CONVEY

The book's own word

PARTNER, CONVEY and DELIVER are engagement aids. They're checklists you can hold in your head while you're in the room.

They are not building blocks of the methodology. The Value Path, the Three-Org Model, the Four Unified Views and the Twelve Complexity Traps are.

CONVEY is for the moment you have to walk people through a change.

Start with Current State: say where things stand today, clearly enough that everyone in the room would agree with it, and say why a change is needed. Then Observations: what do you see when you look past the surface numbers to the pattern underneath? New Insights: what have you learned, inside and outside the organization, that points the way? Validation and Verification: has the change been tested, and does it work in practice and not just on paper? Expectations: does each person know what will be different, what their part is and what success looks like? And Yes!: make room for people to get behind it. Celebrate the progress and the learning as they happen.

Taught in The Value Creation Protocol, Chapter 20, "PARTNER, CONVEY, DELIVER".

Counting Only Some People

The book's own word

Every measure of how people are doing starts with a decision about which people. Usually nobody announces that decision.

It can't leave people out. If it only works by deciding ahead of time who gets counted, it's measuring the count, not the people.

One of the seven ways to fail, named in The Value Era, Chapter 4, "Aggregate confusion" and set as a test in Chapter 6, "Nobody to use it, nobody to carry it".

Creation, Multiplication, Expansion

The book's own word, in its present wording

Creation, then Multiplication, then Expansion.

Any value can grow this way, and AI is one of the things that multiplies it.

  • Creation: first, it happened.
  • Multiplication: you hold the next door for somebody else, and now there are two.
  • Expansion: give it a few years, and you get a street where people do this for each other.

These aren't levels a person gets placed on, and nobody is ranked by how far their value has grown. They describe what became of one piece of value after it landed.

Not the same as Foundation, Capability, Multiplication.

Taught in The Value Era, Chapter 15, "In its own kind".

Customer Org

An approved term

Purpose: Everyone who touches the value journey—from first signal recognition through championship. No artificial splits between "getting" customers and "keeping" customers.

Key Principle: No handoffs between Value Path stages. Relationships are stewarded continuously, not transferred between functional specialists.

Say this instead of "Sales" and "Marketing".

Taught in The Value Creation Protocol, Chapter 18, "The Three-Org Model".

Customer Value Model

An approved term

Layer 2 of The Five-Layer Model. What it holds: What the data means.

The explicit model of what creates value for your customers, for whom, and why. This is the layer that answers "why does our work matter, and to whom" in operational terms — not as a slogan, but as a structure the rest of the business runs from. In an AI-Native organization, this layer is occupied by the Unified Customer View and the Unified Revenue View.

Taught in A Value-First Guide to Surviving the SaaSpocalypse, Chapter 7, "The Architecture".

Customer Value Platform (CVP)

An approved term

A Customer Value Platform (CVP) is a unified business system that enables organizations to recognize, create, deliver, and multiply customer value across all functions — replacing fragmented tool stacks with coherent operational capability. It is NOT a CRM, a marketing automation platform, a sales enablement tool, or an ERP; it IS the unified foundation where all customer-facing operations happen, the single source of truth for relationship context, the platform where AI agents access complete business intelligence, and the architecture that enables the Four Unified Views. Tools solve problems; platforms enable capabilities. HubSpot is the current best-fit CVP implementation.

Say this instead of "CRM" as the primary descriptor: too limited.

Taught in The AI-Native Shift, Chapter 8, "The Platform Question".

D

Data, Identity, Context

An approved term

Layer 1 of The Five-Layer Model. What it holds: Sources of truth, memory.

The foundational layer — the org's Data, Identity, and Context, each read at the full breadth of the layer's own name.

Taught in A Value-First Guide to Surviving the SaaSpocalypse, Chapter 7, "The Architecture".

DELIVER

The book's own word

PARTNER, CONVEY and DELIVER are engagement aids. They're checklists you can hold in your head while you're in the room.

They are not building blocks of the methodology. The Value Path, the Three-Org Model, the Four Unified Views and the Twelve Complexity Traps are.

DELIVER is for the work, while you're doing it.

Start with Deliver with Delight: bring care to the work, so the experience is one they remember well. Educate on Expectations: make sure everyone knows what will happen and when. Listen and Learn: ask for honest feedback, and give people more than one way to tell you. Identify Insights: look for the patterns in what you're hearing and seeing. Validate and Verify: check that a change really met the mark before you roll it out everywhere. Empathize to Empower: look at it from their side, then help them do more themselves. And Remind of Results: help people see what has been created, so it doesn't pass unnoticed.

Taught in The Value Creation Protocol, Chapter 20, "PARTNER, CONVEY, DELIVER".

E

Emergence over Predictability

An approved term

Value creation thrives through continuous adaptation and growth.

Taught in The Value Creation Protocol, Chapter 2, "The Five Core Beliefs".

Empowerment over Learned Helplessness

An approved term

Organizations thrive when people are empowered to create and share value naturally rather than waiting for permission or instruction.

Taught in The Value Creation Protocol, Chapter 2, "The Five Core Beliefs".

The ERP Trap

An approved term

A Core Framework Complexity Trap. Forcing business processes to conform to rigid systems rather than enabling natural operational flow.

Taught in The Value Creation Protocol, Chapter 13, "The ERP Trap → Value-First Platform".

Expected

The book's own word

Someone wrote down what one person is expected to receive, before it happens.

The first of the five stages an entry passes through (Expected → Witnessed → Shown → Confirmed → Settled), taught in Value Accounting, Chapter 2, "Say what it's for" and Chapter 3, "What earns a row".

F

Finance Org

An approved term

Purpose: Resource stewardship and value accounting—not just tracking money, but measuring value delivered.

Key Principle: Measure value delivered, not just revenue captured. This changes investment decisions, pricing models, and resource allocation.

Taught in The Value Creation Protocol, Chapter 18, "The Three-Org Model".

Five Core Beliefs

An approved term

The philosophical foundation the whole approach is built on — five "X over Y" statements naming what we embrace and what we are letting go of: Natural Value Flow over Artificial Control, Empowerment over Learned Helplessness, Wholeness over Fragmentation, AI-Human Partnership over Replacement, and Emergence over Predictability. Not abstract philosophy — the compass you return to when a decision about how to structure a team, build a system, or create value gets hard.

Taught in The Value Creation Protocol, Chapter 2, "The Five Core Beliefs".

The Five-Layer Model

An approved term

The Five-Layer Model is your operation seen as five layers, stacked — and the picture the AI-Native Shift turns on. It is shown as a two-panel figure of the same business in two states, Trapped and Transformed. The layers don't change. What holds them together does.

  • Layer 1 — data, identity, context. Your sources of truth; your organization's memory.
  • Layer 2 — what the data means. The frameworks that turn records into meaning.
  • Layer 3 — who has the context and the capability. The intelligence layer. This is where the transformation actually happens — everything below it is preparation, everything above it is consequence. It is the junction where Human Domain Expertise meets AI.
  • Layer 4 — why the work can be trusted.
  • Layer 5 — where humans meet the system.

Say this instead of "the Five-Layer Diptych" or "the Five-Layer Architecture": one model, one name.

Taught in The AI-Native Shift, Chapter 2, "The Org Chart Is a Confession".

Foundation, Capability, Multiplication

An approved term

For a Unified View. Each Unified View moves through three milestones, read from what people do with the view, never from whether something has been built.

  • Foundation: People agree what the view should show, and they can reach it.
  • Capability: People repeatedly use it to do their work.
  • Multiplication: People improve it, or help others carry it, without our continual push.

For an organization moving to the Three-Org Model.

  • Foundation: When core relationships demonstrate the new model works
  • Capability: When teams operate confidently in the new structure
  • Multiplication: When results compound and transformation becomes self-sustaining

Not the same as Creation, Multiplication, Expansion, the book's own word.

Taught in The Value Creation Protocol, Chapter 19, "The Four Unified Views" (for a view) and Chapter 18, "The Three-Org Model" (for the organization).

Four Unified Views

An approved term

What an organization gains when it stops fighting fragmentation — four business outcomes, not four features to install: the Unified Customer View (every relationship signal in one place), the Unified Revenue View (shared clarity on the whole commercial picture, from the first signal of demand through every promise made, kept and paid, to what comes next), the Unified Strategy View (strategic intelligence embedded where decisions happen), and the Unified Operations View (people resourced with capability, context and safety; each person owns their process in the shared system; AI carries the coordination; and delivery is visible to every team). Customer understanding comes first wherever possible, because every other view leans on it. No view waits for the one before it to be complete: another view can begin as soon as the supporting context it needs is usable. Conditions to achieve, not dashboards to check.

Say this instead of "dashboards / Customer 360": visibility where the work already happens, not one more screen to go look at.

Taught in The Value Creation Protocol, Chapter 19, "The Four Unified Views".

Further Along the Path

The book's own word

A person, or a whole organization, moved forward toward where they were headed.

That third name is borrowed, and I'll say from where. My company works from a pattern called the Value Path: "an 8-stage framework describing how humans naturally progress through value discovery and creation with an organization." People move along it at their own pace.

One of the three lenses, taught in The Value Era, Chapter 15, "In its own kind".

H

Hand Raiser

An approved term

"I need help"

Explicit signal of readiness for expert guidance. Has questions requiring human answers. Authentic interest after sufficient independent research.

Say this instead of "lead" or "prospect": the person has asked for help out loud — an explicit signal of readiness.

Taught in The Value Creation Protocol, Chapter 3, "The Value Path".

HDE (Human Domain Expertise)

An approved term

HDE — Human Domain Expertise — is a person's or organization's hard-won expertise captured in a durable, usable form, so it becomes an asset that AI can meet and multiply rather than know-how that lives only in someone's head.

Say this instead of "tribal knowledge": tribal knowledge is expertise trapped in people's heads, lost when they leave; HDE is that same expertise documented into an asset AI can meet, multiply, and compound.

Taught in The AI-Native Shift, Chapter 10, "The Junction".

Held Up by One Person

The book's own word

Somebody starts a thing and carries it, and when they put it down, it slows.

It has to outlast whoever started it. Me included.

One of the seven ways to fail, named and set as a test in The Value Era, Chapter 6, "Nobody to use it, nobody to carry it", and turned on the book's own definition in Chapter 17, "Who keeps the definition".

Human Context Protocol (HCP)

An approved term

HCP (Human Context Protocol) gives AI systems human context — the ability to represent and respect the interests, agency, and lived reality of the humans involved. The middle layer of the protocol stack (MCP → HCP → VCP).

Taught in The Value Creation Protocol, Chapter 1, "The Value Creation Protocol".

I

In a Person

The book's own word

"In you" is the everyday reading. The working one is about what changed between people.

In the records my company keeps, this lens is defined more narrowly, as a relationship that deepened.

One of the three lenses, taught in The Value Era, Chapter 15, "In its own kind".

In Something Made

The book's own word

Something exists now that didn't: a document, a tool, a way of doing things that stuck.

One of the three lenses, taught in The Value Era, Chapter 15, "In its own kind".

Intelligence

An approved term

Layer 3 of The Five-Layer Model. What it holds: Who has context + capability.

The layer that holds the judgment of the business — the pattern recognition, the situational reasoning, the synthesis across context that turns information into a decision.

Taught in A Value-First Guide to Surviving the SaaSpocalypse, Chapter 7, "The Architecture".

Interface

An approved term

Layer 5 of The Five-Layer Model. What it holds: Every surface where humans meet you.

Layer 5 is not only internal work tools. It is every surface where a human meets the organization — internal work surfaces (email, chat, project tools, the workspace) and outbound / audience / content surfaces (public sites, social, newsletters, how you show up to an audience).

Taught in A Value-First Guide to Surviving the SaaSpocalypse, Chapter 7, "The Architecture".

J

Just-In-Time Over Just-In-Case

An approved term

The fifth of VCP's five load-bearing claims. Operations are designed to deliver capability when needed, not to accumulate capability against hypothetical need. Just-In-Case operations produce platform sprawl, integration debt, and operational complexity without proportionate value. Just-In-Time operations require the unified context substrate to function.

Taught in The Value Creation Protocol, Chapter 1, "The Value Creation Protocol".

L

The Lead Magnet Trap

An approved term

A Core Framework Complexity Trap. Gating knowledge as bait for contact information rather than freely sharing expertise to build trust.

Taught in The Value Creation Protocol, Chapter 10, "The Lead Magnet Trap → Value-First Content".

The Leads Trap

An approved term

A Core Framework Complexity Trap. Treating humans as objects to be captured, scored, and converted rather than signals to be recognized and relationships to be developed.

Taught in The Value Creation Protocol, Chapter 8, "The Leads Trap → Value-First Humans".

M

The Managed Services Trap

An approved term

A Core Framework Complexity Trap. Building business models on client dependency rather than client capability.

Taught in The Value Creation Protocol, Chapter 12, "The Managed Services Trap → Value-First Delivery".

The Measurement Trap

An approved term

A Core Framework Complexity Trap. Optimizing for activity metrics that feel productive while missing outcomes that create value.

Taught in The Value Creation Protocol, Chapter 14, "The Measurement Trap → Value-First Measurement".

Model Context Protocol (MCP)

An approved term

MCP (Model Context Protocol) gives AI systems capability — the ability to call tools, read context, and act in external systems. The bottom layer of the protocol stack (MCP → HCP → VCP, read as capability → context → methodology).

Taught in The Value Creation Protocol, Chapter 1, "The Value Creation Protocol".

More trust

The book's own word

"We trust each other more."

Something between you and another person is stronger than it was.

One of the six kinds, taught in The Value Era, Chapter 15, "In its own kind".

Mutual Value Creation

An approved term

The first of VCP's five load-bearing claims. Value is created across stakeholders, not extracted from them. Customers, employees, operators, and the organization itself are all participants in value creation. Protocols that frame value as extracted from one party for the benefit of another encode an industrial-age default that AI-native operations should not inherit.

Taught in The Value Creation Protocol, Chapter 1, "The Value Creation Protocol".

N

Natural Value Flow over Artificial Control

An approved term

Value exists and wants to flow naturally through human systems, independent of our efforts to control it.

Say this instead of "capturing value": value is not a scarce thing you seize and hold — it is abundant when you let it move freely.

Taught in The Value Creation Protocol, Chapter 2, "The Five Core Beliefs".

A new ability

The book's own word

"I can do something new."

Something is within your reach that wasn't before.

One of the six kinds, taught in The Value Era, Chapter 15, "In its own kind".

No Fit

An approved term

Reserved for a genuine no-fit. The Interest leaves the active set — a genuine no-fit, not a failure to convert.

Say this instead of "Disqualified": Disqualified is a verdict passed on a person.

Taught in The Value Creation Protocol, Chapter 11, "The Qualification Trap → Value-First Partner".

Nobody Uses It

The book's own word

It may be the hardest of the seven to look at, because nothing went wrong. The work was excellent. It was published, praised and cited. It never became the thing anyone had to answer to.

Somebody has to actually use it. Not publish it. Use it, for a decision that matters to them.

One of the seven ways to fail, named and set as a test in The Value Era, Chapter 6, "Nobody to use it, nobody to carry it".

O

Operations Org

An approved term

Purpose: AI-powered coordination and enablement that makes the Customer Org effective at creating value.

Key Principle: Operations should be invisible to clients. They experience seamless coordination; they don't see the machinery behind it.

Say this instead of "support" or "back-office".

Taught in The Value Creation Protocol, Chapter 18, "The Three-Org Model".

The Orchestrator

An approved term

The Orchestrator is the role — the function — of running an organization's operating model: coordinating the whole system so value flows, without becoming a bottleneck. It is governance, not gatekeeping (the L4 principle) — the Orchestrator keeps the system coherent and does not sit in the middle of every decision.

Say this instead of "gatekeeper / bottleneck": a gatekeeper sits in the middle and every decision waits on them; the Orchestrator keeps the whole system coherent so value flows without waiting on any one person.

Taught in The AI-Native Shift, Chapter 16, "Handing Over the Keys".

P

PARTNER

The book's own word

PARTNER, CONVEY and DELIVER are engagement aids. They're checklists you can hold in your head while you're in the room.

They are not building blocks of the methodology. The Value Path, the Three-Org Model, the Four Unified Views and the Twelve Complexity Traps are.

PARTNER is for the relationship itself, when it's forming and for as long as it lasts.

Start with Positioning: can you say plainly who you serve and what really changes for them, in words they would use? Then Accessibility: is it easy for them to reach what you offer, what you know and the help they need, or is something in the way? Relationship: are you building for the long run with this person, or for this one transaction? Transparency: are you open about how you work and what you know, and do you share it freely? New Insights: what did you learn from them this month, and did it change anything you do? Expectations: do they know what will happen next and when, and is it something you can actually deliver? Promise less than you can do, and then do more. Last, Remind: have you helped them see why the two of you are working together, lately, in a way that's about them?

Taught in The Value Creation Protocol, Chapter 20, "PARTNER, CONVEY, DELIVER".

Path OF Value

An approved term

Value Path stages 5–8 (Value Creator, Adopter, Advocate, Champion): the creation-and-multiplication phase. The person becomes the agent of value — they create and multiply it. Adopter is the most critical and under-tracked stage.

Taught in The Value Creation Protocol, Chapter 3, "The Value Path".

Path TO Value

An approved term

Value Path stages 1–4 (Audience, Researcher, Hand Raiser, Buyer): the discovery-and-evaluation phase. The person is the receiver of value — value comes to them. Value here is anticipated, not yet realized.

Taught in The Value Creation Protocol, Chapter 3, "The Value Path".

Playing the Number

The book's own word

The moment a count can be aimed at, somebody aims at it.

It can't be something you win by chasing. If aiming at it makes it go up without anything real changing, it will be played.

One of the seven ways to fail, named in The Value Era, Chapter 5, "Back into money, gamed on arrival" and set as a test in Chapter 6, "Nobody to use it, nobody to carry it".

Q

The Qualification Trap

An approved term

A Core Framework Complexity Trap. Using artificial gates and scoring to filter relationships rather than enabling mutual discovery.

Taught in The Value Creation Protocol, Chapter 11, "The Qualification Trap → Value-First Partner".

R

Realize Value First

An approved term

The operating principle that value should land — be witnessed, shown, and confirmed by the person it served — before the money follows. Money is one Value Wake that value leaves behind, not the trigger for it. In practice: a client sees and confirms the value they received before an invoice ever gestures at it. It is what keeps "we create value" from being a slogan — there is a real, confirmed record behind it.

Say this instead of leading with "revenue / billing": value comes first and is confirmed by the person it served; money is one Value Wake it leaves behind, never the starting point.

Taught in Value Accounting, Chapter 10, "Money beside the book".

Relationships Over Transactions

An approved term

The fourth of VCP's five load-bearing claims. Relationships are the unit of value creation; transactions are events within relationships. Protocols that optimize for transactional outcomes at the expense of relationship integrity produce short-term lift and long-term degradation. VCP-aligned operations optimize for relationship trajectory, with transactions as instruments.

Taught in The Value Creation Protocol, Chapter 1, "The Value Creation Protocol".

Researcher

An approved term

"I am researching"

Active investigation and evidence gathering. Building comprehensive understanding through focused exploration. Comparing approaches and gathering evidence for decisions.

Say this instead of "lead" or "prospect": the person is actively investigating and comparing, gathering their own evidence.

Taught in The Value Creation Protocol, Chapter 3, "The Value Path".

Return on Intention

An approved term

Return on Intention is a question: "Did the value that emerged serve the care behind the work?" Care and intention are held in the CARE record; evidenced value is held in the Value Entry.

Which way it reads. Back, from what happened: "Read back from what actually emerged to the care behind the work; this can reveal unexpected value as well as an unmet expectation."

Resources and money. "Time, effort and tokens describe resources spent; they do not, by themselves, establish what mattered or changed." "Financial return can be part of the account without becoming its whole meaning."

Taught in Value Accounting, Chapter 12, "Read it backward", and asked in Chapter 13, "From KPIs to KVIs".

S

The SaaS Trap

An approved term

A Foundational Complexity Trap. Software fragmentation creating operational chaos where each rational tool purchase compounds organizational complexity.

Taught in The Value Creation Protocol, Chapter 6, "The SaaS Trap → Value-First Context".

Same Word, Different Things

The book's own word

It has to mean one thing. If two honest people look at the same moment and can't settle whether it counts, it isn't a definition yet.

One of the seven ways to fail, named in The Value Era, Chapter 4, "Aggregate confusion" and set as a test in Chapter 6, "Nobody to use it, nobody to carry it".

Settled

The book's own word

The month it belongs to has been closed. Money never decides it.

One of the five stages an entry passes through (Expected → Witnessed → Shown → Confirmed → Settled), taught in Value Accounting, "How to use this handbook" and Chapter 11, "Close the month".

Seven ways to fail

The book's own word

We've now watched a lot of serious people try to put something in money's place, and we know how it went. So before anybody hands you a definition of value, mine included, you're entitled to hold it up against what you've just seen.

Seven ways to fail. That's the bar.

The seven: Same Word, Different Things; Counting Only Some People; Back Into Money; Playing the Number; Nobody Uses It; Too Costly to Check; Held Up by One Person.

These seven are not the Twelve Complexity Traps.

Taught in The Value Era, Chapter 4, "Aggregate confusion", Chapter 5, "Back into money, gamed on arrival" and Chapter 6, "Nobody to use it, nobody to carry it".

Shown

The book's own word

What was written has been put in front of the person it's about.

One of the five stages an entry passes through (Expected → Witnessed → Shown → Confirmed → Settled), taught in Value Accounting, "How to use this handbook" and Chapter 7, "Show it".

The six kinds

The book's own word

There are six. Each one opens with the sentence a person says when it has happened to them, because that sentence is the test.

These are kinds, never a scale. None of the six outranks another, and nobody gets a higher mark for collecting more of them.

The six: A new ability; Time back; A worry gone; More trust; A clearer view; What I came for.

Taught in The Value Era, Chapter 15, "In its own kind".

Stewardship

The book's own word

By stewardship I mean one narrow thing: who keeps the wording of the definition.

The definition is made of words, and words get revised. A word turns out to carry the wrong picture. A clause turns out to leave something out. Somebody has to decide to change it, write the change down, and say what it used to say.

Not the same as Value Steward.

Taught in The Value Era, Chapter 17, "Who keeps the definition".

T

The three lenses

The book's own word

They answer a different question from the kinds: where did the change end up?

A kind and a lens are separate questions. One moment can be a new ability that landed in something made. Don't try to line the two lists up.

The three: In a Person; In Something Made; Further Along the Path.

Taught in The Value Era, Chapter 15, "In its own kind".

Three-Org Model

An approved term

An organizational architecture that replaces the usual tangle of functional silos with three organizations, each with one clear job: the Customer Org (everyone who creates and delivers value, owning the whole relationship with no handoffs), the Operations Org (AI-powered coordination that makes the Customer Org effective), and the Finance Org (resource stewardship and value accounting — measuring value delivered, not just revenue captured). Three orgs, one mission: maximize value created and received across every relationship.

Say this instead of "Sales, Marketing, and Customer Success": one continuous relationship, not a chain of handoffs where context dies at every transition.

Taught in The Value Creation Protocol, Chapter 18, "The Three-Org Model".

Time back

The book's own word

"I got time back."

Minutes or hours are yours again, to spend as you like.

Two of them need a caution: Time back and A worry gone.

A vendor telling you how many hours its product saved you is making a claim about its own product. You saying "I got time back" is naming a kind of value you received. Same words, different speaker.

One of the six kinds, taught in The Value Era, Chapter 15, "In its own kind".

Too Costly to Check

The book's own word

When confirming that something of value happened costs more than what happened, people stop confirming.

Checking it has to be cheap. If confirming that it happened costs more than what happened, nobody will confirm.

One of the seven ways to fail, named and set as a test in The Value Era, Chapter 6, "Nobody to use it, nobody to carry it".

Transformed

An approved term

Transformed is the second of the two states of the Five-Layer Model — AI-native, and the panel labeled TRANSFORMED on the two-panel figure. It is the state of natural value flow and AI-enhanced capability.

Say this instead of "AI-Native" as a state label, or "the right side": one concept, one name, everywhere.

Taught in The AI-Native Shift, Chapter 2, "The Org Chart Is a Confession".

Trapped

An approved term

Trapped is the first of the two states of the Five-Layer Model — the industrial age's shape, and the panel labeled TRAPPED on the two-panel figure. It names the specific friction: industrial-age thinking creating real cost.

Recognition before prescription, always. Trapped is a diagnostic state, never an accusation — trapped thinking made sense in its original context. Help a person see the trapped pattern first; the pathway emerges from the recognition.

Say this instead of "Industrial Age" as a state label, or "the left side": one concept, one name, everywhere.

Taught in The AI-Native Shift, Chapter 2, "The Org Chart Is a Confession".

Trust

An approved term

Layer 4 of The Five-Layer Model. What it holds: Why the work can be trusted.

The trust layer. The substrate that lets the layers below interoperate, the humans and agents at Layer 3 work as a team, and the apps at Layer 5 inherit a trustworthy foundation instead of fragmenting. Trust here is transparency and control: who may do what is decided and written down, what must never happen is guarded, the work is checked before it acts, and anyone can see what was done, by whom, human or agent, and why.

Taught in A Value-First Guide to Surviving the SaaSpocalypse, Chapter 7, "The Architecture".

Twelve Complexity Traps

An approved term

Twelve named ways industrial-age thinking quietly makes an organization more complex and less human. Two are foundational — the B2B Trap (treating people as database objects to process through stages) and the SaaS Trap (tool sprawl that compounds chaos with every rational purchase) — and the other ten are specific patterns like the Leads Trap, the Measurement Trap, and the Managed Services Trap. Each comes with symptoms you can recognize and a Value-First alternative that leads out of it. The point is not to shame the old way; it is to name what it is costing you so you can choose differently.

Taught in The Value Creation Protocol, Chapter 4, "How to read a trap".

U

Unified Customer View

An approved term

Every relationship signal in one place.

The plain test: is everything we know to be true about this person here?

Say this instead of "Customer 360" or "Single Customer View".

Taught in The Value Creation Protocol, Chapter 19, "The Four Unified Views".

Unified Operations View

An approved term

People resourced with capability, context and safety; each person owns their process in the shared system; AI carries the coordination; and delivery is visible to every team.

Taught in The Value Creation Protocol, Chapter 19, "The Four Unified Views".

Unified Revenue View

An approved term

Shared clarity on the whole commercial picture, from the first signal of demand through every promise made, kept and paid, to what comes next.

Taught in The Value Creation Protocol, Chapter 19, "The Four Unified Views".

Unified Strategy View

An approved term

Strategic intelligence embedded where decisions happen.

Taught in The Value Creation Protocol, Chapter 19, "The Four Unified Views".

V

Value

Value, the first principle

What a person or organization can now do that they could not before. Not what they were sold, not what was produced for them, not a promise about the future — value is the real change in what someone can do, and only the person who received it can say it happened.

Value is recognized, not ratified.

Taught in The Value Era, Chapter 14, "Only the person who received it".

Value Accounting

An approved term

The discipline of accounting for the value you create the way money is accounted for: naming it, measuring it, and keeping an honest book of it. It is not traditional accounting — there is no quarterly report to shareholders and no bending the numbers to look good. Value is the first thing you count; money is one Value Wake it leaves behind, counted later.

Taught in Value Accounting, "How to use this handbook".

Value Cornerstones

An approved term

The Four Value Cornerstones for Systematic Transformation, aligned with the Four Unified Views. Each names the value at stake for one constituency, and each maps directly to one Unified View.

The Value Cornerstones are the Foundation; the Four Unified Views are what you build on them.

Taught in The Value Creation Protocol, Chapter 19, "The Four Unified Views".

Value Creation Protocol (VCP)

An approved term

The protocol identity of the Value-First methodology — the methodology expressed in a form that machine systems can parse, declare, and execute without regressing to industrial-age defaults. VCP is not a new methodology; it is the existing Value-First methodology given a place to stand alongside the protocols AI-native systems already understand.

Taught in The Value Creation Protocol, Chapter 1, "The Value Creation Protocol".

Value Creator

An approved term

"I must create value"

Active implementation with pressure to prove decision wisdom. Building new capability and navigating organizational change. Focused on demonstrating value.

Say this instead of "create value": the person who has started creating value themselves — the stage they grew into.

Taught in The Value Creation Protocol, Chapter 3, "The Value Path".

Value Entry

An approved term

One recorded moment where value actually landed for someone — witnessed, cited to when and where it happened, and confirmed by the person who received it. The atomic unit of the value ledger. Not a claim you make; a fact they confirm.

Taught in Value Accounting, Chapter 1, "Start with one view".

Value for the Community

An approved term

Framework Cornerstone (one of the Four C's). Value for the world around us.

Taught in The Value Creation Protocol, Chapter 19, "The Four Unified Views".

Value for the Company

An approved term

Framework Cornerstone (one of the Four C's). Value for our organization.

Taught in The Value Creation Protocol, Chapter 19, "The Four Unified Views".

Value for the Customer

An approved term

Framework Cornerstone (one of the Four C's). Value for those we serve.

Taught in The Value Creation Protocol, Chapter 19, "The Four Unified Views".

Value in Context

An approved term

Framework Cornerstone (one of the Four C's). Understanding how it connects.

Taught in The Value Creation Protocol, Chapter 19, "The Four Unified Views".

Value in Kind

An approved term

Value in Kind is how much value was realized, kept in its own native kind — never forced into dollars, never summed across kinds. Hours a person can now teach, a relationship that went deeper, dollars earned: each is a real amount, but legible only inside its own kind. You cannot add them into one number without lying about what happened.

Say this instead of "a single summed value total": a total pretends unlike values add up; Value in Kind records each realized amount in its own kind — reconciled, never summed.

Taught in The Value Era, Chapter 15, "In its own kind".

Value Ledger

An approved term

The honest book of value that actually reached people — read backward to see what happened, never a score to climb or a leaderboard to win. A filled-in number that does not correspond to value a real person received is worse than an empty one.

Say this instead of "attribution": the honest book of value that actually reached people, read backward to see what happened, never a score to climb.

Taught in Value Accounting, Chapter 12, "Read it backward".

Value Path

An approved term

The Value Path is an 8-stage framework describing how humans naturally progress through value discovery and creation with an organization.

It replaces artificial funnel thinking with recognition of natural human progression—honoring how people actually move through relationships rather than forcing them through manufactured stages like MQL, SQL, and SAL.

The shift from TO to OF occurs at the moment of purchase or commitment.

Say this instead of "funnel": natural progression.

Taught in The Value Creation Protocol, Chapter 3, "The Value Path".

Value Realities

An approved term

The fourteen Value Realities — the natural patterns that work with the way value moves, and the Value-First "what to do instead" when an organization is caught in the industrial-age Complexity Traps. Twelve of them directly counter a specific trap; two (Company, Community) address broader needs. Chosen a few at a time, never imposed all at once. (Its paired framework is the Twelve Complexity Traps — the patterns the Realities replace.)

Taught in The Value Creation Protocol, Chapter 4, "How to read a trap".

Value Realized

An approved term

Value that has actually landed for a person and been accepted by them — the only kind that counts, and the beholder's to grant, never the creator's to declare. It requires a cited prior creation: you cannot realize value that was never created, and any realization claim must point to the moment creation happened. This is why we never "recognize" value on our own calendar the way traditional accounting recognizes revenue — recognition is not ours to grant.

Say this instead of "capture value": value that actually landed for a person and was accepted by them.

Taught in Value Accounting, Chapter 8, "Their word".

Value Statement

An approved term

A person's own account, in their own words, of the value they received. The honest test of whether value was real: not our claim that we delivered it, but their statement that they got it.

Taught in Value Accounting, Chapter 4, "Two hands: who received it, who did it".

Value Steward

An approved term

A person, working with AI, who carries a whole relationship all the way through — full context, real depth, no handoffs. AI handles the breadth so the human can go deep. Not a rep managing one stage of a funnel; a steward of the entire relationship. The role is not ours alone: a practitioner grows into it, and so does a Value Champion — a client who came the whole way through the Value Path and now carries relationships of their own. The destination is the same; who arrives at it is open.

Say this instead of "account manager" or "customer success manager".

Not the same as Stewardship, the book's own word.

Taught in The Value Creation Protocol, Chapter 18, "The Three-Org Model".

Value Visibility

An approved term

Making real value legible across a relationship. Counterintuitively, showing someone the value they received is often what completes it — visibility is not the report you file afterward, it is part of how the value becomes real.

Say this instead of "engagement" as a success metric: showing a person the value they received, which is part of how it becomes real.

Taught in Value Accounting, Chapter 7, "Show it".

Value Wake

An approved term

A Value Wake is the real, lagging consequence a realized value leaves trailing behind it — in whatever kind it takes. Money is one wake; so is a capability that keeps paying off, or a relationship that deepens. Like a boat's wake, it is genuine and it trails: recorded last, never first, and never the thing you steer by.

Say this instead of "ROI as the number that counts": ROI-as-target chases the lagging money number; a Value Wake is the real trailing result of value — in any kind — read backward, never steered by.

Taught in The Value Era, Chapter 14, "Only the person who received it".

Value Witnessing

An approved term

Recording value by pointing to the moment it actually happened — witnessed, timestamped, cited — rather than asserting value without pointing to where it landed. The citation is the thing a nice-sounding claim cannot fake.

Say this instead of "attribution": the citation a nice-sounding claim cannot fake.

Taught in Value Accounting, Chapter 6, "Hear it".

Value-First

An approved term

Leading with value because it is the right thing to do: creating and giving value ahead of, and independent of, any ask in return. The philosophy underneath everything here — value first, and the rest follows.

Taught in The Value Era, Chapter 3, "The company named after the word".

Value-First AI

An approved term

Core Principle: AI should multiply human capability, not replace it.

Taught in The Value Creation Protocol, Chapter 7, "The AI Replacement Trap → Value-First AI".

Value-First Communication

An approved term

Core Principle: Communication should enable authentic discovery, not capture attention through manipulation.

Taught in The Value Creation Protocol, Chapter 9, "The Advertising Trap → Value-First Communication".

Value-First Community

An approved term

Core Principle: Communities multiply value through collective intelligence and mutual enablement.

Taught in The Value Creation Protocol, Chapter 23, "The Value-First Collective".

Value-First Content

An approved term

Content whose job is to deliver real value on the spot — useful whether or not the reader ever becomes a customer — rather than to bait a contact.

Say this instead of "lead magnet / gated content": a lead magnet gives just enough to capture you; Value-First Content gives value with no hook.

Taught in The Value Creation Protocol, Chapter 10, "The Lead Magnet Trap → Value-First Content".

Value-First Context

An approved term

Core Principle: Unified context enables better decisions than fragmented point solutions — and unifying context is much more than integrating tools. Context is not an input to operations; it is the substrate on which operations run.

Taught in The Value Creation Protocol, Chapter 6, "The SaaS Trap → Value-First Context".

Value-First Culture

An approved term

Core Principle: Cognitive diversity and authentic contribution create more value than behavioral conformity.

Taught in The Value Creation Protocol, Chapter 15, "The Conformity Trap → Value-First Culture".

Value-First Customer

An approved term

Core Principle: Design around natural human value creation patterns, not internal processes.

Taught in The Value Creation Protocol, Chapter 5, "The B2B Trap → Value-First Customer".

Value-First Delivery

An approved term

Core Principle: Success means clients need you less for routine matters while engaging more for strategic evolution.

Taught in The Value Creation Protocol, Chapter 12, "The Managed Services Trap → Value-First Delivery".

Value-First Humans

An approved term

Core Principle: People are complete humans with context, history, and potential—not data points to be processed.

Taught in The Value Creation Protocol, Chapter 8, "The Leads Trap → Value-First Humans".

Value-First Leadership

An approved term

Core Principle: Leadership enables value flow; authority often blocks it.

Taught in The Value Creation Protocol, Chapter 16, "The Authority Trap → Value-First Leadership".

Value-First Measurement

An approved term

Core Principle: Measure what matters for value creation, not what's easy to count.

Taught in The Value Creation Protocol, Chapter 14, "The Measurement Trap → Value-First Measurement".

Value-First Partner

An approved term

Core Principle: Partnership emerges through mutual discovery, not one-sided qualification.

Taught in The Value Creation Protocol, Chapter 11, "The Qualification Trap → Value-First Partner".

Value-First Platform

An approved term

Core Principle: Platforms should enable human capability, not enforce system compliance.

Taught in The Value Creation Protocol, Chapter 13, "The ERP Trap → Value-First Platform".

Value-Led Growth

An approved term

Growing by creating more value for more people, rather than by extracting more from the same people. Its one question: "are we creating more value today than yesterday?" Growth as the consequence of value, never a target pursued at value's expense.

Taught in The Value Creation Protocol, Chapter 17, "Value-Led Growth".

W

What I came for

The book's own word

"I got what I came for."

The thing you set out to get done is done.

One of the six kinds, taught in The Value Era, Chapter 15, "In its own kind".

Wholeness over Fragmentation

An approved term

Value multiplies through connection rather than division.

Taught in The Value Creation Protocol, Chapter 2, "The Five Core Beliefs".

Witnessed

The book's own word

Somebody saw the value land and wrote it down.

One of the five stages an entry passes through (Expected → Witnessed → Shown → Confirmed → Settled), taught in Value Accounting, "How to use this handbook".

A worry gone

The book's own word

"One less thing to worry about."

A risk you were carrying has been lifted off you.

Two of them need a caution: Time back and A worry gone.

A vendor telling you how many hours its product saved you is making a claim about its own product. You saying "I got time back" is naming a kind of value you received. Same words, different speaker.

One of the six kinds, taught in The Value Era, Chapter 15, "In its own kind".

Stop 1 of 21: A

Back to The Value Era