Why Businesses & Organizations Mistake Symptoms for Problems

I once had a client ask me to help market her new bistro.

She had invested six months into the concept. The doors were open. The food was excellent. Every detail had been thoughtfully planned.

There was just one problem.

Hardly anyone came.

She wasn't even covering her lunch operating costs, and every day the bistro stayed open, she lost more money.

Like many business owners, she believed she had a marketing problem.

She didn't.

When I began looking at the business as a whole, it became clear that marketing wasn't the real issue. The restaurant was tucked away in a location with almost no natural foot traffic, and the bistro was a completely new brand. The people who already knew her wedding venue had no reason to assume there was now a lunch destination hidden inside it.

No amount of online advertising was going to create immediate demand for a place people didn't know existed.

Marketing wasn't the problem.

Visibility was.

Symptoms are convincing

Every organization has symptoms. Missed deadlines. Employee turnover. Poor communication. Frustrated customers. Invoices that aren't getting paid. Projects that never seem to move forward. Or a new bistro without customers.

Many organizations spend enormous amounts of time trying to fix these problems. They hold meetings. Rewrite procedures. Implement new software (and blame the prior one). Introduce new accountability measures.

Sometimes those efforts help. Often, they don't. Not because the people involved are incapable. Not because they aren't trying. Because they're trying to solve the symptom instead of understanding why it exists.

The difficult truth is symptoms are convincing. They demand attention. They're visible, measurable, and usually painful. When your accounts receivable is climbing or your team is frustrated, it feels obvious that that's the problem.

But symptoms rarely appear on their own. They are evidence that something deeper inside the organization isn't functioning as intended. The challenge is that when you're inside the organization every day, the symptom becomes normal. You stop asking why it exists.

Instead, you begin organizing your work around managing it. Eventually, the symptom becomes the job.

The value of distance

One of the reasons I enjoy helping businesses is that I don't enter an organization carrying yesterday's assumptions. I'm not attached to the way things have always been done. I'm not responsible for defending existing processes. That distance matters. A lot.

Distance changes the questions you can ask. Why does this process exist? What decision created this bottleneck? What assumptions are we still operating under? If we solved this symptom tomorrow, what would prevent it from coming back?

Those questions rarely produce immediate answers. They do something more valuable. They reveal the architecture of the organization.

Chains of consequences

Organizations almost never suffer from just one isolated problem. Instead, they experience chains of consequences.

A communication issue creates inconsistent execution. Inconsistent execution creates customer frustration. Customer frustration creates additional work. Additional work overwhelms employees. Overwhelmed employees begin making mistakes. Soon everyone is working harder than ever, but the organization isn't moving forward.

From inside the system, each issue feels independent. From outside the system, they're often connected. That's why solving one symptom frequently has little lasting effect.

The system simply produces another one.

The first question isn't 'How do we fix this?' It's 'What is this symptom telling us?'

Because until you understand what the organization is actually trying to tell you, every solution is just another experiment.

Making the invisible visible

Organizations don't usually need someone to tell them to work harder. Most already are. What they sometimes need is someone who isn't living inside the system every day. Someone who can make the invisible visible. Someone who can separate symptoms from causes.

Someone who can help build a plan that addresses the actual problem rather than managing its consequences.

That's the work I love.

Because making the invisible visible isn't the end of the work.

It's the moment meaningful work can finally begin.