The Number Nobody Looks At
Daniel had been COO for eleven months when I found it.
Not in a dashboard. Not in a board presentation. Not in any of the weekly reports that landed in his inbox like clockwork every Monday at 7am.
It was hiding in a spreadsheet that three people had access to and nobody opened.
The Spreadsheet
The file was called ops_reconciliation_Q3_FINAL_v2_REVISED.xlsx. The kind of filename that tells you everything about how an organization works without reading a single cell.
Inside was a column labeled "Adjustment Factor." Fourteen rows. Each one a small number — 0.03 here, 0.07 there. Innocuous. The kind of numbers that look like rounding.
They weren't rounding.
"When you find a number that nobody looks at, you've usually found the number that matters most."
Each adjustment represented a manual override. Someone, somewhere in the process, was quietly correcting a discrepancy between what the system said happened and what actually happened. Every month. For at least two years.
What It Meant
The total annual impact was $2.3 million. Not in losses — in invisible costs. Costs that were real, that the company was paying, but that never appeared on any report anyone actually read.
The money wasn't stolen. It wasn't fraud. It was something more common and more insidious: it was the cost of a broken process that everyone had learned to work around instead of fix.
Three teams were involved. Each had built their own workaround. Each workaround was someone's full-time job. None of them knew the others existed.
The Conversation
I showed Daniel the spreadsheet on a Thursday afternoon. He stared at it for a long time.
"How long has this been happening?" he asked.
"At least two years. Probably longer."
"And nobody told me?"
"Nobody knew the whole picture. Each team only saw their piece."
That's the thing about hidden costs. They don't hide because people are dishonest. They hide because organizations are complex, and complexity creates shadows. Things live in those shadows — real costs, real inefficiencies, real problems — that no single person can see.
The Fix
It took four weeks to untangle. The fix itself was almost anticlimactic: a single process change and an automated reconciliation that replaced three manual ones.
The $2.3 million didn't appear as a line item on the next quarterly report. It appeared as margin improvement. The board was pleased. Daniel was relieved.
But the real lesson wasn't about the money. It was about the spreadsheet. About the fact that the most important number in the organization was sitting in a file that nobody opened, maintained by people who didn't know they were hiding a $2.3 million problem.
That's operations intelligence. Not the dashboards. Not the KPIs. The stuff underneath. The numbers nobody looks at.