Before one definition
Sales reports shipments. Finance reports invoices. Store managers report collections. All three are “right,” and the meeting cannot pass item one. The owner has to paper over it.
“One number” is not forcing finance to drop accounting standards. It is deciding which algorithm version the operations dashboard recognizes, and which reconciling table takes the difference. Written and signed, it is worth more than another wall screen.
Operations definition · signed · v3
Sales = shipped and not-voided order amount − posted returns − discounts (excludes stored-value top-ups)
Gross margin = sales − issue cost (lot weighted) − free-goods cost on the order
Inventory days = ending inventory cost ÷ (last 28 days issue cost / 28)
Outlier store = store margin more than 5pt from the regional median, or ≥ 8 SKUs below safety for 3 days
After one definition
The dashboard lights one column: operations sales. Anyone who needs invoices opens the finance view, not the weekly home screen. Difference lives on a reconciling table, not in who talks louder.
The mechanism is concrete: ten minutes before the meeting, everyone opens the same URL. WeChat screenshots are not accepted. A disagreement opens a document, not “my sheet.” If it cannot open, you cannot close the argument; see If a number cannot open a document, what is the dashboard for. Source systems can keep their own operational math, but they must map to the column on the formula board; see When every system calculates its own numbers, what breaks.
Keep the definition short. Phase one locks three to five must-watch KPIs; see Which KPIs belong on the leadership dashboard first. Lock too many and nobody signs. Lock too few and Excel returns to the meeting. The first visible efficiency is a shorter meeting; see Visible efficiency a data capability actually delivers. Chains also write roll-up rules on the same board; see After stores roll up, how HQ watches outlier stores.
Definition changes go through versions. Quiet formula edits break trust faster than Excel. If numbers are still wrong, trace source, key, and time window; see The system is live and numbers are still wrong. How to trace it. When quality is poor, clean the critical codes first; see Data quality is poor. Build the dashboard first, or clean first. Why you need a dashboard before a platform, see Why an operations dashboard is not optional.
DaXi treats the formula board as development input, not a document written after go-live. No signature, no drawing. To write the number your weekly meeting fights about into a formula, go to the Data service page. Mid-size companies do not need a big platform for “one number”; see Do mid-size companies have to buy a data platform.
If bonus uses a different definition, write both side by side
If bonus math differs from the operations definition, write both. Otherwise store managers feel ambushed by the dashboard. Two sets can exist. One verbal set cannot.
Put the formula board on a clickable Definitions page inside the dashboard. Locking it on an implementer’s laptop does not help. New hires read that page in week one so the meeting does not slide backward.
Fewer arguments does not mean no objections. The allowed path is: open the formula, open the document, file a definition-change ticket. The forbidden path is throwing a private sheet on the table mid-meeting. Alerts and shop-floor screens must cite the same version, or crews and the weekly meeting will talk past each other again; see Alerts pushed to people, so exceptions rarely sit overnight. Meeting efficiency you can see, see Visible efficiency a data capability actually delivers.