Trust the Evidence, Not the Story

Not because people are dishonest. Most of the time, they aren't. But business owners are human. We remember things through pressure, urgency, fear, frustration, hope, and exhaustion. A story can feel true simply because we've repeated it enough times.

The evidence is what brings you back to reality.

Where the Story and the Evidence Diverge

I see this constantly in financial and operational work. A business owner may say, "I need more revenue," when the records show a spending issue. They may say, "This client is the problem," when the agreement was unclear from the beginning. They may say, "The books are fine," because reports exist, but the balance sheet tells another story.

The story explains how someone feels about what's happening. The evidence shows what's actually happening.

I hear this most clearly on discovery calls. Someone fills out a questionnaire, but they also want to talk it through, and that explanation almost always comes out as a story shaped by fear, urgency, frustration, hope, and how exhausted they are by the problem. Meanwhile, I'm listening for where the real pain point is. Then I go look at the books to see if the evidence agrees.

Why This Matters When You Own a Firm

When you run a business, it's easy to carry too much in your head. You remember the conversation. You remember the exception you made. You remember why you priced something a certain way. You remember the workaround you created.

Until you don't. Or until someone else remembers it differently.

That's why documentation, clean financial records, and clear systems matter. They aren't just administrative tasks. They're evidence. They help you make decisions based on what can be verified, not what feels true in the moment.

A clean profit and loss statement can show whether pricing is working. A balance sheet can show whether you can trust the numbers. A follow-up email can confirm what was actually agreed to. A documented process can reveal where work keeps breaking down.

The Tool Is Only as Good as the User

Evidence only works if the system producing it is set up correctly. A chart of accounts that isn't curated to fit the actual business won't give you accurate information, no matter how carefully you review it. Software that isn't syncing properly across payroll, the general ledger, and other connected platforms will quietly generate the wrong picture, and everything built on top of that picture inherits the error.

This is where I spend a lot of my time: not just reading the numbers, but confirming the numbers are trustworthy in the first place.

What This Looks Like in Practice

I had a recent project involving an in-house bookkeeper who didn't know how to properly use QuickBooks or the other connected platforms. Payroll wasn't syncing. The general ledger wasn't set up correctly. The credit card software wasn't syncing either. Every gap had a reasonable-sounding explanation attached to it. But when I went into each platform, the evidence told a different story. The business owner didn't have the specifics, they just had a gut sense that something was off, that they were making more and spending less than the numbers reflected. We ended up correcting three years of data so they could backfile three years of taxes and recover money that was owed to them.

Another client called me because a merchant service provider was holding six thousand dollars of their money. In their telling, the provider was entirely at fault. When I got on the phone with the business owner present and asked the right questions, the evidence pointed somewhere else: a new protocol needed to go into place on their end so their funds wouldn't keep getting flagged. Once we focused on the evidence instead of the frustration, it was resolved in about an hour and a half.

In both cases, the story wasn't a lie. It was just incomplete. The evidence filled in what the story couldn't see.

The Question I Return To

You don't need more information for the sake of having more information. You need the right evidence before making important decisions.

Before you change your pricing, look at profitability. Before you blame a client, look at the agreement and the communication history. Before you assume the business is healthy, look at the financial reports. Before you create a new service, look at capacity and systems. Before you panic, look at what's actually happening.

The question I keep coming back to is simple:

What can I verify?

That question can slow down a reactive decision. It can reveal the real issue. It can keep you from solving the wrong problem.

Pitfalls to avoid

A few general traps worth watching for as you put this into practice:

• Treating evidence-gathering as an audit for blame: The point isn't to prove who's right, it's to get an accurate picture so you can make a better decision.
• Assuming the software is giving you clean data by default: A tool only produces reliable evidence if it's set up and synced correctly. Check the foundation before you trust the output.
• Waiting until frustration forces the issue: The earlier you build the habit of checking evidence, the less often you're doing it in crisis mode.
• Confusing more data with better evidence: Volume isn't the goal. Verifiable, relevant information is.
• Letting an unclear agreement stand because the relationship feels fine: Clarity now prevents a dispute over "what was actually agreed to" later.

The story matters because it tells you how people are experiencing a situation. But the evidence matters because it tells you what's real. Better decisions usually start there.