The Lobbi Delivery Team
Operational Systems Engineering
The slide says revenue per job is up 12 percent. The operations lead frowns and says that cannot be right. Someone pulls a spreadsheet. Twenty minutes of forensic accounting later, the room discovers the report includes change orders and the spreadsheet does not. Both numbers are correct. Neither is trusted. The decision the meeting existed for gets postponed.
If this scene plays out in your business, the temptation is to blame the tools and shop for a better dashboard. Resist it. A dashboard renders numbers; it cannot make them mean the same thing to two people. The problem underneath is that your metrics have no definitions — and undefined metrics are private languages wearing a shared vocabulary.
Where the Divergence Comes From
Every team builds its numbers for its own purposes, with its own boundary decisions baked in silently.
- Sales counts a deal as open until someone marks it lost, which nobody does promptly, so the pipeline number runs fat.
- Finance counts a customer as active if they were invoiced this quarter. Support counts anyone with a login. Marketing counts anyone on the list.
- Turnaround time starts at order receipt for operations, at deposit for accounting, and at first contact in the customer's head.
None of these choices are wrong. They are unstated. And unstated boundary decisions surface at the worst possible moment — in the meeting, in front of the decision, as a credibility fight between two people who are each holding a locally-correct number.
The damage is larger than the wasted meeting time. Once a leadership team has watched two official numbers contradict each other a few times, every future number arrives pre-doubted. People revert to gut feel and anecdote — not because they prefer them, but because at least their own anecdotes do not contradict themselves. The business effectively loses its instruments.
The Metric Dictionary
The repair is unglamorous and decisive: a metric dictionary. One page per measure that the business actually steers by, answering six questions.
| Field | The question it settles |
|---|---|
| Name | What do we call this — one name, used everywhere |
| Definition | Exactly what is counted, including start and stop boundaries |
| Exclusions | What is deliberately left out (and why) |
| Source | Which system is authoritative for this number |
| Owner | Who answers questions about it and approves changes |
| Cadence | How often it refreshes, and how late data can arrive |
Ten to fifteen metrics cover most operational businesses: the handful of volume, speed, quality, and money measures that recur in every weekly meeting. Writing the first draft takes a day. The arguments that surface while writing it — what does count as an open deal? — are not a cost of the exercise. They are the exercise. Every argument settled on the page is an argument removed from a future meeting.
Definitions Need an Owner and a Version
Two practices keep the dictionary alive instead of becoming another stale document.
- Each metric has one owner. Not a committee. The owner approves definition changes, fields the this-looks-wrong questions, and is accountable for the source staying accurate. Numbers without owners drift; numbers with owners get fixed.
- Definitions are versioned. When the boundary changes — change orders now included, a new status added to open — the change is dated and noted, and historical comparisons get flagged. Half of the metric is up arguments in any business are really an undocumented definition change moving the baseline.
Treat the dictionary the way engineers treat code: changes are deliberate, attributed, and reviewable. The discipline sounds heavy and weighs almost nothing — a changelog line per change.
The One-Number Test
You can check whether this work is needed in your business with a single test. Pick the number your leadership quotes most — open jobs, monthly revenue, average turnaround. Ask three people independently: what is the number right now, and what exactly does it include?
Three matching answers means you have working instruments — rare and excellent. Divergent answers mean every decision built on that number is standing on sand, and the most leveraged data work available to you is not a new platform, a warehouse, or a dashboard refresh. It is a page of definitions and a name beside each one.
Trustworthy numbers are not a technology outcome. They are an agreement, written down.
Dashboards make numbers visible. Definitions make them true. Every undefined metric on a report is a scheduled future argument.
Sources
Topic clusters
Ready to see where the friction is?
The Lobbi's Operations Discovery maps your workflows, identifies your highest-impact bottlenecks, and gives you a clear picture of what's possible.