Why We Need A Language For Solving Problems

Language tends to rely a lot on context. Saying, “I love that movie!” doesn’t mean that you love it in the same way that you love your mom. Hopefully.

In that example, the only person who might make that mistake is someone just learning English. But when it comes to solving problems, there’s a real lack of precise language.

It makes it hard for us to come up with the right approach to a problem. It’s also difficult to help other people solve problems. I coach kids a lot. Here’s some typical dialogue:

“I’m stuck.”

“What do you mean?”

“I can’t solve this problem.”

There are at least a dozen different things that can mean. And then how do you respond?

“Well, try again” or “work harder.”

I am obviously trying to help but that rarely has any positive value to it.

We need language that describes the techniques (both descriptive and proscriptive), where they should be headed, what types of mental states we should we be feeling, and words that direct our attention appropriately.

It would be nice to say “where you’re at — this is the type of action you should take.” But creating that language takes some effort.

Over time, I’ve noticed certain issues tend to come up in certain parts of the journey from problem to solution. Here’s a crack at what a problem solving lexicon might look like.

The Problem-Solving Process

Every company has problems. Your company might be based specifically on solving problems.

But even if it isn’t, there’ll always be times when complex issues arise.

Solving a complex problem requires you to take certain steps, but you’ve probably noticed there isn’t one single approach that can solve every problem.

There are different strategies and processes that we go through. For instance, some problems might require you to pick a solution and work backwards. Others might present you with a handful of solutions that you begin to narrow down. Some problems don’t have obvious solutions.

Some problems aren’t even easily defined.

The Language Of Problem Solving

The issue here is that the term “problem solving” is incredibly generic. It encompasses all of those approaches I just mentioned. It’s a wide variety of thought processes.

So when someone says they’re working on solving a problem, that doesn’t really give you a good idea of what they’re doing. What exactly are they doing?

How many times have I banged my head against the wall when a truly different approach was required?

Define: Are they defining the problem right now?

Mountain: What mountain are they trying to cross? What’s the objective? Goal?

Wanderer: Broadly exploring all directions

Daydreaming: Projecting possibilities

Funnel: Narrowing to a possibility; settling on a solution

Arouse: What am I feeling about this?

Problem solving is really a mishmash of all those different elements. The goal is to direct your attention and energy at systematically. The language you use will either help you in that process, or it’ll hold you back.

What Are We Disagreeing About?

Problems, and their solutions, can easily cause disagreements. That’s healthy. A good debate about the problem at hand and its potential solutions will help open everyone’s minds. But there are different aspects to this.

“We’re talking past each other” can mean a dozen different things. I’ve made that comment in meetings and at least felt like I sounded smart but now realize it’s a dumb comment. To move forward, much more precise language is required.

Red/Blue: Are we disagreeing on a principle? Do we have the same values?

Fork in the Road: Are we headed to different places? Are our goals different?

Viewpoint: What are our perceptions?

Elephant: Are we looking at different parts of the problem?

You have to be able to articulate how you’re disagreeing before you can understand why that disagreement is happening in the first place.

You can start by asking yourself some questions:

Is this Red/Blue or a Fork in the Road? Lego or Elephant?

Defining Different Disagreements Leads to Answers

I find that the answers are pretty interesting. A lot of times we’re disagreeing because we don’t have the same objectives, not because someone’s logic is faulty. Sometimes we’re just perceiving the problem in a different way. And other times we’re looking at different sides of the problem.

There’s an old poem about six blind men who touch an elephant to understand it better. But they all touch a different part — a tusk, a leg, an ear, the belly, the trunk, and the tail. So naturally, they all think of it very differently. But it’s still an elephant. That never changed. It’s just that none of them are experiencing it in the same way as the others.

Sometimes a problem is like that elephant. Everyone has their hand on a different piece, and they don’t see that it’s really the same issue.

Precise Language

Precise language dramatically improves the process. Whether it’s to address a disagreement, or assess what the problem is in the first place, using precise language allows you to move forward, make progress. Think of it as a systematic way to ask questions, or speak about the problem correctly.

Now you help a kid or colleague alike in a clear manner. Instead of talking about solving a problem, you’re talking about the specific processes involved in solving the problem. Instead of arguing back and forth, you’re addressing what the disagreement is actually about.

When issues arise, having this type of a language saves time and energy. Each stage of problem-solving requires different activities; now you know how to proceed. You can define the problem quickly and correctly. You know where your colleagues stand. You know why you’re disagreeing with them, and how you can potentially come to an agreement. And you’ll notice the difference immediately as everyone gets on the same page.