ARTICLE · SELF IMPROVEMENT · 5 MIN READ

Why Your Perfect Solution Still Doesn't Work

Relationships can be complicated. Not only romantic relationships. I’m also talking: family, work, school, church. The relationships we buil

Photo by Katja Ano (https://unsplash.com/@katjaano) on Unsplash (https://unsplash.com)

Relationships can be complicated. Not only romantic relationships. I’m also talking: family, work, school, church. The relationships we build are as complex as the human beings themselves.

Yet they don’t have to be if we are international and vulnerable enough.

Most of the time, when people ask for help or are frustrated about something, they mean what they are saying…and then some.

There’s a popular story about Henry Ford that says if he had listened too closely to what people were asking for, he would have built faster horses instead of cars.

People describe problems using the limits of their current reality. That reality could be flawed, myopic or just mean but that doesn’t mean you shouldn’t listen. You absolutely should.

Listen for what is being said and what isn’t.

Beneath every request or frustration is a desired outcome. And if you miss that, you’ll solve the wrong problem. And no matter how good your solution is logically, it will miss the mark.

Good problem-solving comes down to three things.

They sound simple, but they rarely are.

First, you have to understand why.

Not the obvious why. The core of the problem.

Take the classic relationship argument about the cup left in the sink.

Man leaves his glass in a clean sink and goes to bed.

Woman wakes up and starts to “nag” about it.

On the surface, it seems ridiculous.

Why all this frustration over a cup?

The minute you slow down and start asking why, you put yourself in the other person’s shoes and then you see things differently.

She’s upset because the cup was left in the sink after she cleaned it thoroughly.

That upset her because she had spent time and energy cleaning, even though she was already tired from a long day at work.

That hurt because it felt like her efforts weren’t noticed.

And that sucked because all she really wants is to feel appreciated, supported, and cared for. And that could be as simple as washing a cup and not leaving it in the sink.

It was never about the cup. The cup was just the trigger.

This is called the five whys method. It’s a problem-solving technique formulated by Sakichi Toyoda (founder of Toyota) as a guide to understand the root cause of a problem.

Most conflicts, complaints, and requests work this way. If you respond only to the surface, you miss the real problem entirely.

Now that you understand the why, how do you actually solve it?

This part is tricky, but if you have a good grip on the root cause, you’re halfway in.

Imagine a farmer complaining that they keep losing money because middlemen control where and when their produce is sold.

What is the root cause here?

The farmers are growing more than the demand in their area. They do not have the proper storage facilities to store the excesses so they are now at the mercy of the middle men who run things their way.

Now that we understand the why, we need to factor in the context of the user and their environment. What are the core parts of their request? What are the trade offs you will have to make?

If you don’t take time to understand the real constraint from the context of the farmer, you might spend months building a sophisticated mobile app that connects farmers directly to buyers.

But what if the farmer doesn’t have reliable internet? Or electricity?

Do they even trust you and your digital systems?

Your “smart” solution becomes useless.

In that case, the right solution might be:

  • A shared physical storage facility

  • A cooperative model

  • A simple, offline-first system

  • Or even a pricing agreement within the community

Understanding how matches the solution to the actual constraint within the context of the problem.

We have a solution now. How do we share it?

We need to understand the language.

Not everyone expresses their needs in the same way.

Some complain. Some withdraw.

Some over-explain. Some say very little and expect you to read between the lines.

Even when you understand the real problem and have a good solution, it can still fail if it’s delivered in the wrong language.

In the cup-in-the-sink situation, the solution probably isn’t a detailed discussion about household rules. It might just be a simple acknowledgment. A small act. A moment of care.

“I see you.”

“I appreciate you.”

“I’ve got this.”

In work, design, or leadership, this could be translated as using familiar tools over flashy new ones. Speaking in tangible outcomes as opposed to features.

Respecting culture, emotion, and lived experiences.

Of what use is a solution if the person it’s meant for doesn’t hear it.

Solving problems takes a lot of intentionality.

Take the time to understand why someone is frustrated, how their problem can realistically be solved, and the language they use to express their needs, and you will see drastic outcomes. It’s safe to say that this applies to all forms of relationships.

If you’ve used any of these techniques I shared, tell me about your experience in the comments.

I would love to hear about your context and experiences.

Back to top ↑

Loading the full page…