The Problem Is Never Where You Think It Is

The value is usually in the problem underneath the one you started with.

When I worked in IT support, we had a saying: the problem is never where you think it is.

Someone would call the help desk and say their computer wasn’t working. After a few questions, we’d discover that the computer was fine. Their email wasn’t working, usually because the mail server or the network was down. The caller described their problem. We had to trace it back to the cause, which was usually somewhere they couldn’t see from their desk.

That saying came back to me after a recent conversation with a founder. I spend a lot of time with founders, sometimes as a mentor and sometimes in pitch meetings.  What I usually hear is an early version of how a company explains what it does.

This founder’s product makes it easier for engineering teams to maintain code after development. He positioned it as a cost-saving tool for companies, with less engineering time spent on upkeep and fewer people looking at screens, which is true and a reasonable way to pitch it.

I looked at it from a different angle.  What happens to a company that can’t keep up with maintenance? 

Bug reports and feature requests pile up because there aren’t enough people to work through them. Customers waiting for fixes get frustrated.  Some eventually leave. 

That changed how I  saw the product’s value. It wasn’t just about developer productivity or reducing engineering costs. It was about reducing customer churn. Like those help desk calls, the problem he described was real. But it sat on top of a bigger one.

The value is usually in the problem underneath the one you started with.

Howling dogs

Founders tend to pitch the pain they believe is worth solving. Too often, it’s what I call a Howling Dog Problem. In Howling Dogs and Shiny Pennies, I told the porch story. It was about a dog who kept howling because he was sitting on a nail, but it didn’thurt enough to make him get up. Customers will complain about a problem like that for years without being willing to pay to fix it.

Code maintenance can be a howling dog. Engineering teams complain about it, but companies often don’t connect a growing backlog, or long waits for feature requests, with the customers they lose. 

Until they make that connection, maintenance looks like an engineering expense. Once they see that the backlog is driving churn, it becomes a customer retention problem. Companies will be more likely to pay to solve that. Finding the bigger issue underneath the one you started with is often where the real value lies.

One way I try to tell the difference is to ask what it costs a company to leave the problem unsolved. If the answer is mostly annoyance, it’s probably a howling dog. If it affects revenue or customers, it’s a problem worth paying to solve.

Another example

Another founder was building software for specialty medical practices to handle incoming paperwork, much of which still arrives by fax. 

His pitch was focused on speed. The product cut the time needed to process each document from about fifteen minutes to one or two.

Faster fax handling, on its own, could easily be a howling dog. Practices have complained about fax for decades. However, they still kept using it.

Behind that are problems the person running operations is already dealing with: Understaffed front offices, rising administrative costs, and referrals that get delayed while staff work through the paperwork. These challenges say more about the product’s value than the time saved on each document.

What the help desk didn’t show

I’ve been on the other side of this in IT support. 

In What’s Missing on Your Balance Sheet, I wrote that a good month meant nothing went wrong, and nobody gave you credit for it. 

Clients didn’t always connect the routine maintenance with the outages it prevented. What they were willing to pay for was preventing a production server outage, when the cost of downtime became clear to everyone in the building.

Berkson's Bits

Learn how to build rapport.

If there’s one skill that serves you well in business and in life, it’s the ability to build a connection with people. That builds trust, and then magic can happen.

Before you start talking business, or asking for whatever you need, find something you have in common. It could be a shared connection, an experience (sports, the arts, or a place you’ve both lived), or a common interest or hobby.

Somehow I always manage to find SOMETHING. 

The conversation changes when you find that common ground. You are no longer two people having a transaction. You are two people connecting.

It’s a skill. You can learn it, practice it, and get good at it.

What I'm Listening To...

This is my first duplicate what I’m listening to. The Grammy nominations just came out and Raye received 11 nominations including Album of the Year for THIS MUSIC MAY CONTAIN HOPE. I listened again and it would definitely get my vote.

Finding the problem underneath doesn’t always change the answer. Sometimes efficiency is the main value, and the straightforward pitch is the right one. 

More often, it brings out something the pitch left out. It can also point you to someone else in the customer’s organization, someone other than the person you initially planned to speak with. 

That is where I want to pick up next week.

What’s the problem underneath the one your product solves?

Looking forward to continuing the conversation...

Alan

Reply

or to participate.