ChatGPT
Claude
Google AI
Copilot
The Monday meeting opens on pipeline. Sales reads a number that excludes a record type the team stopped selling. Finance reads an extract that still includes it. The gap is large enough to fill the half hour. Someone asks for the spreadsheet they trusted last quarter. The page on the wall has forty reports linked from it. Tableau has drawn both pipelines, with filters quiet enough that both look official. A new cloud arrived last month with its own pipeline, and nobody removed a number to make room. The executive has learned to ignore the page. The page has become furniture.
An executive page works when someone can disagree with a number and point at a sentence. Five numbers. One definition each. The same definition in sales, service, finance extracts, and whatever data platform sits beside them. Forty reports on one screen ask the reader to be the analyst. They will not. They will ask for a spreadsheet.
Five numbers, written down
Pick the five this organisation will ask about without a briefing. For many firms that is pipeline, revenue booked, cases open past the promise, renewal due, and cash collected. If the business runs on a different five, use those. The count is the constraint, and it is the constraint because a thirty-minute meeting cannot adjudicate a library. A sixth number is not a small addition. It is a request to drop one of the five, said out loud, with the owner of the dropped number in the room.
For each number, one sentence: the object, the field, the filter, and the date grain. "Pipeline is open opportunities in these record types, amount field, close date this quarter, owned by these roles." If two people can still calculate it two ways, it is not ready for the page. The usual second way is hiding in the date. Close date this quarter is not created date this quarter, and it is not invoice date. Write which. The second hiding place is the filter: which record types, which currencies, whether a lost opportunity from last week is in or out, whether a renewal is an opportunity or a contract. Each of those is a clause in the sentence, or it is a future argument.
Name an owner for each sentence. One person, not a committee. When the business changes the rule, that person changes the sentence and every report that implements it, in the same week. A definition that lives in someone's head will drift the first time a region asks for an exception and gets a private report. The private report is the mechanism. It feels helpful. It means the executive number and the regional number are no longer the same fact, and the next meeting will be spent subtracting them.
Read the sentence to the person who will be challenged on the number. If they cannot repeat it without the dashboard open, the sentence is too clever, or it is not the number they actually defend. Change the sentence until they can. A sentence only an analyst can say will be abandoned the first time the analyst is not in the room, which is most rooms.
The same sentence in every cloud
Sales pipeline that excludes a record type, and a finance extract that includes it, is two numbers and a standing meeting. Pick the sentence. Implement it everywhere the figure appears, including the extract, the slide, and the number an agent will repeat if someone asks. Extra cuts for operators live in a folder, labelled as cuts, not as the executive number. A cut can be useful. A cut that is pinned beside the executive number, without the word "cut" on it, is a second definition.
Currency and ownership belong in the sentence too. A pipeline summed in one currency with a rate from last month, and a finance total summed in ledger currency, will differ on a quiet day. Say which. A number "owned by these roles" that silently includes a role added for a project will jump, and the jump will be blamed on the business. The sentence is how you notice the role was added. Review it when roles change, not only when the chart looks wrong.
The qualified stage, if pipeline depends on it, is not a vibe. It is the field with one owner, which is the work in how marketing and sales stop overwriting each other. If this page says pipeline and that field still has two writers, the executive number will flip on the hour, and no chart type will make it sit still.
The chart comes after the sentence
Salesforce says you can "Expand the capabilities of Data 360 using Tableau or Tableau Next." That is a place the chart can sit. The chart does not invent the definition, and a second chart with a quieter filter is how the five become a library. Put the sentence under the number, in plain words, on the page the executive sees. A tooltip nobody opens is not the sentence. If the sentence does not fit under the number, the sentence is doing too much, or you are hiding a second definition in the visual.
Data 360 is also described this way: "Ingest, harmonize, unify, and analyze streaming and batch data with Data 360." Unify the definition before you unify the feeds. A harmonised pipeline with two meanings is a faster argument, because the refresh is quicker and both sides arrive with a number that looks freshly calculated. Fresh is not agreed. Agreement is the sentence, implemented in each place the figure is shown, including the extract a board paper still builds by hand. If the board paper is not on the sentence, the board paper is the number that will win, and the dashboard is decoration.
Do not add a calculated "executive pipeline" in the data platform that averages the two definitions or picks one in a formula nobody has read aloud. That calculation becomes a third number. Name it only if it is the sentence, and then delete the other two from the executive page. Leaving all three up is how a careful person learns to export.
Forty reports is a refusal
A dashboard that links out to a library asks the executive to finish the job. They will not finish it. They will ask which report is the real one, and then they will ask for the spreadsheet, because the spreadsheet has one tab. Cap the page at the five numbers, each with its sentence under it. If someone wants a sixth, they name which of the five leaves. That conversation is the governance. Skipping it, and adding the sixth in a corner, teaches the reader that the page is negotiable.
The operator reports remain available to the people who run the process. A seller needs a cut of their own book. A service lead needs the cases by queue. Those reports live in a folder with a name that says they are operational. They are not pinned to the page the executive is supposed to trust in a thirty-minute meeting. Pinning them "so everything is one click away" is how the page becomes forty links and no decision.
When a number is challenged, the response is the sentence and the records that make it, not a new chart. If the challenge is right, the owner changes the sentence everywhere in the same week, and says what changed. If the challenge is a request for a different cut, it goes to the operator folder. It does not get a tile.
| Number | The sentence has to name | A second number sneaks in when |
|---|---|---|
| Pipeline | Object, amount field, record types, close-date grain, roles | An extract includes a record type the sentence excludes |
| Revenue booked | Which object counts as booked, and on which date | Invoice date and close date are both in use |
| Cases past the promise | What the promise is, and when the clock starts | One cloud uses a different entitlement |
| Renewal due | Opportunity, contract, or both, and the window | A region keeps a private renewal sheet |
| Cash collected | The system that received it, and the grain | A dashboard sums a balance the ledger does not |
Use the five this business will actually ask. The table is the shape of the sentence, not a compulsory set. A firm with no field cases does not invent "cases past the promise" to fill a box.
An agent that can see both pipelines will repeat one of them, and the reply will sound sure. Point it at the five sentences, or do not let it answer the question yet. A confident sentence about the wrong filter travels further than a blank, because the blank sends people back to the definition and the reply does not. The prompt is another place the sentence has to be implemented, in the same week as the extract.
Rehearse the page once with the five owners and the spreadsheet closed. Ask each number out loud. If anyone reaches for a different file, that file is a definition you have not written down. Adopt it and change the sentence, or close the file. A rehearsal that needs the spreadsheet has already told you the page is not ready. Another chart will not change that.
How you know it is being used
The executive uses the page in the meeting and does not ask for a restated version. If they still want the spreadsheet, ask which of the five they do not believe, and fix that sentence. Do not add a sixth chart to compensate. Adding one teaches them the page is negotiable, and the spreadsheet remains the system of record. Recheck the five when a new cloud arrives. The new cloud implements the existing sentences. It does not arrive with its own pipeline, its own date grain, or its own quiet filter. If a sentence must change because the new cloud is genuinely a better source, the owner changes it everywhere in the same week, including the extract and the board paper.
Cheap, before the library is pinned: writing five sentences, naming five owners, deleting the private report that disagrees, putting the sentence under the number.
Expensive, after a year of two pipelines: every forecast conversation starts with a reconciliation, the spreadsheet is the only artefact anyone trusts, and a new cloud makes a third pipeline because nobody was willing to drop a number. The repair is still the sentence. It is just slower, because people have learned to defend their version. Start with the number the meeting actually fights about. Get that one identical in every cloud. Then the next. Five identical numbers beat forty fresh charts.
