The Value Creation ProtocolContents
Part IV — How the organization is built
Chapter 19
The Four Unified Views
Who builds the picture of your customers before a board meeting? And where do they get it?
If the answer is one person, a few late nights and a stack of exports pasted into a deck, you already have a view of your customers. It gets rebuilt by hand every quarter, and between meetings it lives in that one person's head.
That's the first thing to know about this chapter. You aren't starting from nothing. The view usually already exists somewhere. The first thing to ask for is the spreadsheet or deck that already holds it.
What this is
The Four Unified Views are business outcomes that transform fragmented operations into unified organizational capability. They are what organizations gain when they escape the B2B Trap and SaaS Trap: not features to implement, but conditions to achieve.
A unified view is assembled across systems for the person using it. It is not a claim that one system holds all the data. The aim of every view is the context this person needs for this decision, unified from wherever it lives. A view is built on purpose, for a purpose. It is never a promise that the data is complete.
Each view lives where the people it serves already work. A report can serve a view. It is never the view.
1. The Unified Customer View: every relationship signal in one place. The plain test: is everything we know to be true about this person here? It covers every relationship that can create value, not only customers. It is for the people and organizations you work with. Its Value Cornerstone is Value for the Customer, and Customer Teams look after it. From: a view rebuilt by hand before every board meeting, or carried in one person's head. To: a standing view the people who serve the relationship trust and work in.
2. 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. What this view tracks is the promise, and the promise is often much more than the payment. Every promise is held through four statuses: booked, billed, earned and paid. They are statuses, not steps. Several can be true at once, and the view shows all four together. They are also not the whole view. Money is read as the wake of value. It is recorded after the value, and it is never the thing the view steers by. This view is for the organization doing the work, and it comes with a warning: value that stayed inside and reached no one outside is activity, not value. Its Value Cornerstone is Value for the Company, and Finance Teams look after it. From: each team holds its own number, and nobody can see how they connect ("Which number are we using?"). To: one shared picture of the whole commercial relationship.
3. The Unified Strategy View: strategic intelligence embedded where decisions happen. This is what the business knows that isn't in the customer or revenue record, its market, its strategy, how it operates and what its people know, joined to that customer and revenue reality at the moment someone has to decide. Context here is more than data. It comes in three layers: the data, the documentation and strategy, and the memory people never wrote down. One concrete way strategy reaches the record is the one Value Accounting, Chapter 2 teaches: a short note, kept beside each piece of work, of who it's for and what you hope it makes possible for them. This view is for the decision, and whoever has to make it. Its Value Cornerstone is Value in Context, and Business Leaders look after it. From: intelligence trapped in heads, side systems and decisions nobody wrote down. To: contextual intelligence where decisions happen.
4. 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. It holds responsibility and accountability together: who does the work, and who answers for the result. It also keeps how the work felt beside what the work produced. A person saying "that felt faster" is a reported experience worth keeping. It is not, by itself, measured time saved. This view is for everyone outside the transaction, the people who learn from the work without buying it. Its Value Cornerstone is Value for the Community, and Operations Teams look after it. From: linear scaling that requires proportional hiring. To: capability multiplied through human-AI partnership.
How the four relate. The Value Cornerstones are the foundation, and the views are what you build on them. A view with no Cornerstone under it is instrumentation with no accountable recipient.
Customer understanding comes first wherever possible, because every other view leans on it. But 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. The Strategy View arrives largely from the first two. Once the Customer View and the Revenue View stand side by side, most of the context a decision needs is already there.
Building and talking are different things. When you explain this to someone, start at whichever view answers the problem they have.
"Looked after" means stewardship. It is not ownership and it is not an access rule. Every team reads and adds to every view.
How to tell where you are
Signs you can check this week:
- The customer picture is rebuilt by hand before every big meeting, or one person carries it.
- Somebody in a planning meeting asks, "Which number are we using?"
- A customer has to repeat to the delivery team what they already told the person who sold to them.
- A decision gets made twice, because nobody wrote down what was decided the first time or why.
- Growth plans assume more hiring in the same proportion as more work.
- When people say they need "visibility," what they get is another screen to go and check.
- A score on a record triggers an action, and the person acting has never seen the relationship behind the score.
Write down which of the four each sign belongs to. Most of them will touch more than one, and that's expected.
What to do
- Make the leader the owner of the agreed view. It can't be handed off as a software project. The person who runs the organization owns what the view is supposed to show.
- Ask for the spreadsheet or the deck. Find the hand-built version that already exists and start from it.
- Agree before you build. The view is documented and agreed by the people who use it, before anything is built. Each team says what its own version must show. The person who administers your systems builds it. They don't decide it.
- Write down, for each view, what it holds, for whom, and how close you are today.
- Put customer understanding first wherever you can, and begin the next view when its signal shows. The signals are specific:
- The Revenue View can begin when the people and organizations in each promise are on one joined record that the people serving them trust.
- The Strategy View can begin when the person who decides can see a relationship's customer reality and its promises together, at the moment of deciding.
- The Operations View can begin when the context each person needs for their own work is reachable where they do it.
- Make it visible first. Then decide what needs automating. Design your data backward from the agreed views, never the other way round.
- Test every request against the view. Does this move the view? If not, it waits. That goes for new tools and new features too.
- Keep a score inside the view. A score can help inside the context of a relationship. It can't replace understanding the relationship. The mistakes come from acting on a score outside that context.
Expect this to speed up agreement, not delivery. An agreed view gets people pointed the same way quickly. The work to deliver it is still the work.
How you know it worked
Read it from what people do with the view, never from whether something has been built. There are three milestones.
- 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 your continual push.
Here is what that looks like for each view, at the two milestones where you can watch people use it.
| View | Capability | Multiplication |
|---|---|---|
| Customer | Someone other than the builder uses it daily. A conversation is picked up without starting over, and the customer stops repeating themselves. | People fix and extend it unprompted. New hires are onboarded through it. A team asks, "Can we do this too?" |
| Revenue | Finance, sales and delivery plan from it, and the customer gets what the booked promise said. | Delivery and finance add context unasked. Renewal conversations start from the same view. |
| Strategy | Decisions are made from it, and the record keeps what was decided, tried and learned. | A team's recorded learning changes what the next person sees. |
| Operations | People repeatedly do, with it, work they could not do before. | People improve how the work is done, and the capability travels: clients, partners and the community carry it without your continual push. |
Notice who is speaking in those cells. The customer who stops repeating themselves. The customer who gets what was promised. The team that asks for it without being told to. Those are the people who can say it worked.
"The dashboard is built" is not on the list. Each milestone is complete when its signal appears, never when a date arrives.
Where it goes wrong
The Measurement Trap. Somebody says "we need visibility" and gets a dashboard. Answer a need for visibility with reachable data, not another dashboard. An organization that asks for visibility and gets a screen full of activity has walked into the trap.
The Authority Trap. Once context comes together quickly, the bottleneck stops being information and shows up as ownership: who is allowed to decide. Fixing that by pulling decisions to the top walks into the Authority Trap. Watch the Strategy View in particular. A view with "strategy" in its name, looked after by leaders, can turn into strategy held at the top. The words "at the moment of decision" are what keep it at the front line.
The SaaS Trap. Someone buys a tool and announces that the view is done. Or someone claims that one system now holds all the data. A view is an outcome your people agreed on. It was never a purchase.
A few more that the framework names:
- Leading with the four views before the person in front of you has a problem they answer.
- Making a view wait until the one before it is finished.
- Claiming a milestone because something was built.
- Treating "looked after by" as "controlled by," and building a new silo around a view.
- Promising a timeline.
Read further
- The AI-Native Shift (Book 3), Chapter 6, "The Meaning Layer", designs the four views for a real organization. Its Chapter 8, "The Platform Question", is where the platform we run them on is named and argued for. This handbook leaves the platform there on purpose.
- A Value-First Guide to Surviving the SaaSpocalypse (Book 1) tells the story of what tool sprawl did to shared context, which is the reason these views exist.
- Value Accounting (Book 4) is the handbook for the value in a relationship that isn't dollars, which the Revenue View holds beside the money.
- The Value Era (Book 0) explains why money is read after value and never ahead of it.