When the Data Says Something the Owner Does Not Want to Hear
There is a moment in almost every engagement that I have come to expect. It usually happens within the first two weeks after delivery, once the owner has started using the tool and the numbers have settled into a pattern. They look at a metric, and the number does not match what they believed to be true.
The margin on their highest-volume product is lower than they estimated. A service they considered their bread and butter is actually their least efficient revenue source once labor is allocated properly. A customer they assumed was their best account is barely profitable when the full cost of servicing them is included. The data is not showing a problem they did not know about. It is quantifying something they suspected but had never confirmed, and the confirmation is uncomfortable.
Why this moment matters
What happens next is the most important inflection point in the engagement. If the owner trusts the data and investigates the finding, the tool starts doing what it was designed to do: informing decisions with facts instead of assumptions. If the owner dismisses the data or finds reasons to doubt it, the tool begins its slide toward irrelevance.
I have seen both outcomes. The owner who sees that their flagship product has a 12% margin instead of the 25% they assumed, digs into the cost allocation, confirms the calculation, and adjusts their pricing within a month. That owner uses the dashboard every week from that point forward. The tool changed how they operate.
I have also seen the owner who sees the same kind of result, decides the formula must be wrong, asks for an adjustment that makes the number look better, and then gradually stops checking the dashboard altogether. The tool did not fail. The data did not fail. The willingness to act on uncomfortable information failed.
The instinct to reject
The instinct to reject inconvenient data is not irrational. The owner built the business on their judgment. They have made decisions by feel for years, and those decisions produced a functioning business. When a spreadsheet contradicts the judgment that built the company, the natural response is to question the spreadsheet, not the judgment.
That response is healthy in small doses. The data should be questioned. The formulas should be verified. The assumptions behind the calculations should be transparent enough that the owner can trace the logic and confirm whether the methodology matches reality. This is one of the reasons I build tools with visible calculation steps rather than opaque outputs. The owner needs to be able to see how the number was produced, because trust in the result depends on trust in the method.
But there is a line between healthy skepticism and motivated reasoning. Questioning the calculation is healthy. Adjusting the calculation until it produces a number that confirms existing beliefs is not. And the second pattern is surprisingly common, not because the owner is dishonest with themselves, but because the gap between belief and data creates genuine cognitive discomfort.
Building for this moment
I design tools with this moment in mind. The decisions I make during the build, things like showing the raw inputs alongside the calculated outputs, making every assumption editable and visible on a settings tab, and including comparison data so the owner can contextualize the result, are all designed to make the uncomfortable moment productive rather than destabilizing.
When the owner sees a margin figure they did not expect, the tool should make it easy to answer the next question: why? If the cost allocation methodology is visible, the owner can check it. If the input data is displayed alongside the output, the owner can verify that the right numbers went in. If a scenario adjustment is available, the owner can test whether a reasonable change in assumptions produces a materially different result.
That transparency is what turns disagreement with the data into investigation rather than rejection. The owner does not have to take the number on faith. They can audit it, challenge it, and arrive at their own conclusion. If the number holds up to scrutiny, the tool gains credibility. If it does not, the methodology needs refinement, which is also a productive outcome.
The credibility threshold
There is a credibility threshold that every reporting tool has to cross. Before the threshold, the owner is checking the tool's output against their own intuition. After the threshold, the owner is checking their own intuition against the tool's output. The shift is subtle but consequential, because once the tool has earned enough trust to serve as the baseline, it starts shaping decisions rather than confirming them.
That threshold is almost always crossed during an uncomfortable moment. The data contradicts an assumption. The owner investigates. The data turns out to be right. The assumption was wrong. And the next time the data contradicts an assumption, the owner investigates with less resistance, because the tool has demonstrated that its methodology is reliable.
If the first uncomfortable moment is handled well, with transparency, patience, and a willingness to walk through the logic, the tool earns the credibility it needs to be useful long-term. If it is handled poorly, the tool becomes the thing the owner opens when they have time and ignores when they are busy, which is exactly when the data matters most.
