The Problem Is Rarely Where It Hurts: How to Find the Root Cause of a Business Problem

For a while, I had a dull pain in my lower back. On top of that, my leg would go numb whenever I sat or stood still for too long.

I was sure the problem was my lower back muscles getting weaker, so that's what I focused on.

It turned out the problem was tension in my piriformis, a muscle deep in the hip, putting pressure on my sciatic nerve. I thought I had a pain in my back. It turns out it was a pain in my butt.

What is referred pain?

Doctors call this referred pain. You feel it in one place, but it's coming from somewhere else entirely.

It happened to me again with my foot. For years I had an itch on the bottom of my foot so deep I could scratch it for ten minutes straight. There was no rash, nothing you could see. I tried foot massages, stretching my foot and calf, and resistance exercises. Nothing made it better, and over a few years it never improved.

Then I started working with a trainer who noticed how stiff my hips had become from all the sitting I do. She believed the stiffness in my hips was sending those sensations down to my feet. So I started working on my hips with stretching, strengthening and mobility training. After about a year, the itch was gone.

If I hadn't talked to someone who understood how the whole body connects, I never would have thought to look at my hips.

The same thing happens in your business

Referred pain shows up in business systems all the time, especially when you're running several tools that all depend on each other.

Your booking rate drops by 5%, and everyone immediately assumes the booking form is broken. Clients complain about slow follow-up, and everyone blames the email tool. The numbers in a report look wrong, and someone starts rebuilding the report.

Sometimes they're right. But just as often, the real issue is hiding somewhere less obvious. A change to a page broke the tracking on a link. A tool that feeds the booking system stopped sending data. A process upstream changed and nobody told the team downstream.

When something stops working, it's easy to panic and blame the most visible part of the process. That's usually the part closest to the customer, because that's where you see the damage.

Why treating the symptom makes it worse

When you fix the symptom instead of the cause, the problem doesn't go away. It just moves, or it comes back.

Worse, you can spend real money in the process. A new booking tool, a new email platform, a rebuilt website, all to fix a problem that was never in any of those places. I've seen this pattern over and over in the tech audits I've done. Companies juggle multiple services, something goes wrong, and tracing the real root cause gets hard, so they replace whatever is closest.

Then the itch is still there, and now you're paying for a new tool on top of it.

How do you find the real cause?

Every problem leaves breadcrumbs. It leaves a trail of evidence that leads back to where it started, if you're willing to follow it instead of reacting.

Frequently asked questions