The Business Data You Are Not Looking At Is the Data That Will Cost You
- Maria Mor, CFE, MBA, PMP
- Jun 1
- 8 min read
You review the numbers every week. Revenue is up. Sales conversion looks reasonable. The dashboard is green. And yet something feels off, because the margin is not where it should be, and the team is working harder than the results suggest they should be.
The data you are reviewing is the data that survived. It made it back to base. During World War II, statistician Abraham Wald identified one of the most costly analytical errors in military history. Commanders were armoring bombers based on damage patterns from the planes that returned from missions. Wald pointed out what they were missing: the planes that did not return, hit in the engine and cockpit, were not in the data at all. The absence of data was itself data. The commanders were studying the wrong planes.
Every business reporting system is built the same way the commanders built their analysis: around the data that completed, the transactions that survived, the outcomes that made it back. The gap is structural, not a failure of attention.
What the Returning Planes Have in Common with Your Dashboard
Every reporting system in your business is built around transactions that completed. Invoices that got paid. Orders that shipped. Calls that converted. Tasks that got checked off. These are the planes that made it back.
What the system cannot show you is the invoice that never got sent because the handoff between sales and operations broke down at the last step. The client who did not renew because no one followed up during the gap between project close and contract renewal. The vendor payment that processed twice because the approval workflow had no secondary check. The hour your operations manager spent re-creating a document that exists somewhere in a folder no one can find.
Those are the planes that never made it back. They do not show up in your dashboard. They show up in your margin.
In music, the notes a player does not play carry as much weight as the notes they do. The silence between beats is where the rhythm lives. Skilled musicians call these the ghost notes: the quiet strikes that give the music its structure without announcing themselves. In a business, the ghost notes are the process failures that never generate a record, the breakdowns that leave no timestamp, the costs that never attach to a line item. They are felt in the results without being visible in the data.
The business data you are not looking at is rarely hidden on purpose. It is simply invisible to every tool you are using to look.
The Business Data You Are Not Looking At
Most growing businesses have strong visibility into what comes in and reasonable visibility into what goes out. The gap lives in the middle, in the execution layer where revenue gets converted, or does not.
The patterns that show up across industries follow a recognizable structure. Revenue comes in at the front office. Profit is protected in the back office. And the back office contains the largest concentration of ghost notes in any business: the processes that run informally, the approvals that happen through text messages, the onboarding steps that happen differently every time, the reporting that relies on one person's institutional memory to interpret correctly.
These are not catastrophic failures. They rarely trigger an alarm. They drain slowly, consistently, and in amounts small enough that any single instance looks like a rounding error. Across a week, a quarter, a year, they compose a structural tax on the profit margin.
In my experience across different industries, the ghost notes cluster in four recognizable places:
Handoffs between departments or roles that have no documented transfer point
Approval or review steps that are assumed to happen but have no confirmation mechanism
Recurring work that is performed differently by different people, producing inconsistent outputs
Exception handling that never made it into any process, handled ad hoc every time it appears
The owner who built these systems is rarely aware of how often the gaps activate. The team has compensated so many times that the workarounds have become the process.
Where Ghost Notes Show Up on the Income Statement
The financial consequence of invisible process failure does not appear in a single line. It distributes across the income statement in ways that make the source difficult to trace.
Gross margin absorbs the rework. When a deliverable is produced twice because the first version was based on incomplete information, or when a vendor dispute requires staff time to resolve, the cost lands in labor without a label. The margin narrows, and the most common diagnosis is that pricing needs to go up or volume needs to increase. The actual diagnosis is that the process cost is hiding in plain sight.
Operating expenses absorb the redundancy. Duplicate payments, unused software subscriptions that no one owns, vendor contracts that auto-renewed without review: these are ghost note costs. They passed through an approval process that was not designed to catch them, and they now appear as overhead without a corresponding business function.
Accounts receivable absorbs the handoff failures. When the billing process depends on a signal from the project team, and that signal is informal, collections slow. Days sales outstanding increases. Cash flow tightens. The revenue was earned. It simply did not complete its journey to the bank account on schedule.
Business process improvement work at Praxis Hub consistently finds that the most significant margin recovery does not come from cutting costs that are visible. It comes from closing the gaps that were never entered into the system at all.
Why the Gaps Stay Invisible
The structural reason business owners cannot see their own ghost notes is the same reason the military commanders could not see which planes were going down. The data available to them was the data from the system that survived. Everything that broke down and resolved informally left no record. Every workaround that became routine stopped being visible as a workaround.
Proximity is the mechanism. A business owner who has run the same operation for years has absorbed the ghost notes into their understanding of how things work here. They compensate for the gaps without recognizing the compensation as a signal. They fill in the missing handoff. They catch the exception before it becomes a problem. They are carrying a cognitive load that the business should be carrying structurally, and they have done it long enough that it no longer registers as unusual.
This is not a management failure. It is a structural limitation that applies equally to every operator who builds and runs a system from the inside. The closer you are to an operation, the more invisible its gaps become. This pattern shows up across industries without exception.
The back office profit leak is the financial expression of this dynamic. The profit that should survive the revenue cycle does not make it through, and the cause is not visible from inside the system that contains it.
Why Outside Perspective Helps
The reason Abraham Wald could see what the commanders could not was not superior intelligence. It was that he was not inside the system. He had no stake in the explanation the commanders had already settled on. He could look at the data that was absent and ask what its absence meant.
An outside operational perspective works the same way. Someone who has not built their understanding of your business from the inside has not normalized your workarounds. They have not stopped questioning the steps that happen informally. They have not absorbed the ghost notes into their baseline expectation of how things should run.
The gap is never in what the owner knows. It is always in what the owner has stopped questioning.
What the outside perspective provides is not a list of problems the owner missed through carelessness. It is a structural read of the system that cannot come from inside the system. That distinction matters because it defines where the solution has to originate.
Free Resource: 5 Steps to Streamline Your Business
If the ghost notes in your operation are showing up as margin pressure, cash flow inconsistency, or team capacity that disappears without a clear explanation, the starting point is understanding where the gaps are concentrated.
The 5 Steps to Streamline Your Business guide walks through the five structural areas where process gaps most consistently drain profit in growing businesses. It is built for business owners who already know something is off but have not been able to locate the source in their existing data.
Frequently Asked Questions
What is survivorship bias and how does it apply to business data?
Survivorship bias is the error of drawing conclusions from data that only reflects outcomes that completed successfully, while overlooking the outcomes that did not. In business, this means most reporting systems show what worked, what converted, and what got delivered. The processes that broke down, the transactions that never completed, and the costs that accumulated without a record do not appear in the same data. Decisions made from that data alone are built on an incomplete picture of what is actually happening in the operation.
What are ghost notes in a business context?
Ghost notes are the process failures, informal workarounds, and unrecorded costs that affect business performance without generating a visible record. They are the handoffs that break down between departments, the approvals that happen through unofficial channels, the exceptions that get handled ad hoc every time they appear. They do not trigger an alert. They show up in the margin as a slow, consistent drain that is difficult to trace back to a specific cause without an operational read of the system.
How does the business data you are not looking at affect profit margin?
These ghost notes tend to accumulate in three places on the income statement: gross margin absorbs rework and duplicate effort, operating expenses absorb redundant costs and unreviewed recurring charges, and accounts receivable absorbs the delays created by informal handoffs between project delivery and billing. None of these appear as a labeled cost. They appear as margin that is narrower than expected given the revenue the business is generating.
Can a business owner identify their own ghost notes by reviewing reports more carefully?
Reviewing existing reports more carefully surfaces the data those reports were designed to capture. Ghost notes, by definition, did not generate a record in those systems. The limitation is structural, not informational. A business owner who built and runs a system from the inside has absorbed its gaps into their baseline understanding of normal. The workarounds, informal steps, and unrecorded exceptions are not visible from that vantage point regardless of how carefully the available data is reviewed. An outside operational perspective is the structural requirement for identifying what the internal data cannot show.
What is the first step for a business owner who suspects hidden process gaps?
The first step is separating what the business measures from what the business actually does. Most growing businesses have strong measurement of the transactions that completed and limited visibility into the execution layer where those transactions were produced. A structured review of the handoffs, approval points, and recurring work that happens informally, before any changes are made, gives the owner a map of where the ghost notes are concentrated. The 5 Steps to Streamline Your Business guide is a starting point for that kind of structural review.
Ready to See What Your Data Is Not Showing You?
If the margin is narrower than the revenue justifies and the explanation is not in your reports, the ghost notes are the likely source.
The Back Office Brief
Get a weekly insight connecting back office operations to profit. Delivered every week, free.
Comments