Menu Close

Understanding Problems

What do you do when the path you were headed down is blocked? Most want to hop over the tree and ignore the problem altogether.

“A well-understood problem is half-solved,” said the brilliant Charles Kettering or John Dewey. This quote has been attributed to both thinkers, but I prefer Kettering to Dewey, so I like to go with him.

For our purposes, this calls into question how we approach any run-of-the-mill problem in our daily lives. Often, when we see an issue, we blow right past the problem itself and immediately cast about for solutions. Have you ever been in a conversation like this?

Me: “Oh man, I thought I would have more time to do this, but I’m just slammed.”

Counterpart: “It’s probably your time management. Have you thought about buying a software to help you manage your time better?”

Me: “Well, actually -“

Counterpart: “I went through this same thing a few years ago. Don’t worry, you’ll figure it out!”

This may be a supportive conversation focused on solving the problem – but it actually makes it worse. If you’re trying to elicit positive change in your business, the more understanding you have about what’s actually happening and why, the better.

The truth is, we’re all guilty of wanting the problem to just go away. We would rather find a solution – any solution – quickly than have to wade through the mire of what caused the problem in the first place. Understandable, yes. Wise, no. Does this approach lead to more pain down the road? Absolutely.

If we want to reform our ways, we might ask, “Okay. How then can I start understanding the problem?”

The best way to get better acquainted with a problem of any kind is to ask questions of it. Gather information. Do some investigation. From there, you already have a better concept of where the issue may be coming from – which means you already have a better framework for developing the best solution.

Activity: Identify a current issue, big or small. Ask the following questions:

  • How do I know there is a problem here?
  • What are the symptoms of this problem?
  • Who/what does this problem impact?

From there, do any potential solutions arise? If not, you may start asking “Why did the process fail?” of this problem to generate better understanding of the root cause.