The Innovators Studio with Phil McKinney podkast

How to Improve Your Problem Solving Skills

0:00
25:26
Do tyłu o 15 sekund
Do przodu o 15 sekund

Problem solving. It's one of those skills everybody says they have. But most of us were never really taught how to do it. In school we got formulas. Plug in the numbers, get the answer. Real problems don't work that way.

I'll walk you through the four skills that'll make you a better problem solver: framing the problem, finding the root cause, coming up with alternatives, and choosing and testing.

And toward the end, I'll share a case study from my own career, where problem solving was done both well and badly. The problem to solve? We launched a product that nobody over 50 would buy.

Let's get into it.

What It Is and Why It Matters

Problem solving is about figuring out what's wrong and fixing it so it stays fixed. Many times, what looks like the problem is really just a symptom. Fix the symptom, and the problem comes right back.

Every job you'll ever have comes down to this skill. Think about it. Somebody's paying you because there's a problem they need solved. And the people who get the hard assignments, the ones who move up, are the ones who can walk into a mess and figure out what's really going on and fix it.

The good news is it's a skill you can learn. Nobody's born with it. You can get better at it.

How to Improve Your Problem Solving

Skill 1: Framing the Problem

This is the one skill the majority of people skip.

Somebody walks in and says, "We've got a problem." And within about thirty seconds, the whole room is throwing out fixes. We need more people. We need new software. We need to reorganize. Nobody's stopped to agree on what the problem actually is.

Framing means slowing down long enough to get clear on what's wrong before anybody starts fixing it. It feels slow. But it's the fastest way to the right answer, because you stop wasting time fixing the wrong thing.

Here are the steps.

  1. Write down what's happening, not what you think the fix is. "We're missing deadlines" is a problem. "We need to hire" is a fix.

  2. Answer three questions.

Who is affected? What exactly is the problem? Why does it matter?

Who is affected? Be specific. The more detail the better. "Customers" is too broad. Which customers? New ones? Longtime ones? People in one part of the country?

What exactly is the problem? Describe what's happening, with numbers and dates if you can. Not "sales are down," but "sales of this one product are down 15 percent since March."

Why does it matter? What happens if you don't fix it? Lost money, lost customers, a missed launch. That helps you prioritize how much time and effort the problem deserves.

Notice none of those asks what the fix is. That's on purpose.

  1. Ask if it's really worth solving. Some problems turn out not to be problems at all. Sometimes the right answer is to live with it and spend your time on something bigger.

  2. Check your problem statement for a hidden answer. Read it back. Are you leading the team? If there's a fix buried in the definition of the problem, rewrite it.

Skill 2: Finding the Root Cause

Once you know what the problem is, you've got to figure out why it's happening. That's the root cause. The real reason, not the first reason.

The tool most people know for this is the 5 Whys. You write down the problem, ask why it happened, then ask why about that answer, and you keep going. Usually about five times.

It's a good tool, but it follows one path. So wherever you start decides where you end up.

My variation on this skill is to go wide. Before I ask the second why, I brainstorm every reasonable answer to the first one. Sales are down. Why? Could be price. Could be the product. Could be a competitor. Could be how it's being sold. Then I take the 5 Whys down each one of those.

And watch out for your data steering you. It only tells you about the people who bought. The people who walked away aren't in your spreadsheet.

Here are the steps.

  1. List every reasonable cause before you dig into any one of them. Write them all down. Don't fall in love with the first one.

  2. Ask what changed. It's one of the fastest ways to get to the real cause.

  3. Go where the problem happens. Watch the problem with your own eyes. Talk to the people closest to it. They'll usually tell you things no report or consultant ever will.

  4. Talk to the people who aren't in your data. The ones who walked away. One approach that has helped me was to talk with customers who almost bought and didn't.

  5. Use the 5 Whys on each possible cause, not just the first one.

  6. Cross off the causes the evidence rules out, and keep going until one holds up. Go down every branch, not just the one that looks most likely.

Skill 3: Generating Alternatives

Most people grab the first fix that comes to mind and run with it. Don't.

There's almost always more than one way to fix a problem. You can throw money at it. You can throw people at it. You can make the problem smaller. And sometimes, honestly, you can just decide to live with it. Each of those has a very different cost, so put them side by side before you decide.

Here are the steps.

  1. Get at least three options on the table before you pick one. If you've only got one, you haven't really looked.

  2. Make them actually different. Three versions of the same idea is still one idea.

  3. Look first for the quick, simple fix. Once you've found the real cause, many times the fix is easier than anybody expected.

  4. Make sure each option fixes the cause, not just the symptom. If the problem would come back the minute you stopped, you fixed a symptom.

Skill 4: Choosing and Testing

Choosing and testing go together. You pick the option you want to try, and then the test tells you whether you picked right.

The mistake I see a lot is that people either test forever, or they don't test at all. Neither one works. How much you test should depend on how much it costs to be wrong.

Here are the steps.

  1. Choose the option that fixes the cause for the lowest cost and risk. It usually isn't the most impressive option. That's okay.

  2. Match the test to the risk. If it's cheap and easy to undo, make the change and measure. If it's expensive, try it small first.

  3. Decide up front what success looks like. Otherwise you'll talk yourself into whatever result you get.

  4. Measure the result, not the activity. Being busy on the fix isn't the same as the problem going away.

  5. Ask whether the problem can come back. Then go fix whatever let it happen in the first place. Skip this one and you'll be solving the same problem again next year.

Case Study: The Laptop Nobody Over 50 Would Buy

So let me show you what this looks like in real life.

During my time at HP, we put a new laptop into Best Buy. Inside, it was pretty much the same machine as an earlier model that had done well. The only real change was the look on the outside. It was HP's answer to Apple's aluminum laptops, a shiny shell that looked like aluminum but cost a lot less.

And this new version was selling well below plan.

The product team jumped on it. They spent months trying to figure out why. They compared it spec by spec against the competitors on the shelf. Did somebody have more memory? A bigger hard drive? Better battery? They talked about cutting the price. They were guessing.

Now, I didn't know any of this was going on. HP was shipping 65 million PCs and laptops a year around this timeframe. One model running behind was never going to hit my desk.

At the same time, I spent most Saturdays standing off to the side at the retail outlets selling our products just to watch people shop. On this Saturday, I was in a Best Buy in Silicon Valley. The store manager recognized me, gave me a hard time about stalking his employees, and then went and rounded up all the salespeople who worked in computers and printers.

So I asked them, how are our products doing? "Oh, they're all doing great." And I said, okay, stop the BS. How are our products really doing?

One guy sort of sheepishly raises his hand. He goes, "Well, we've got this updated laptop with a new design. But nobody over 50 will buy it."

I was confused.

He walked me over, and I saw it right away. The designers had carried that shiny chrome look all the way onto the keys. Under the store lights, the glare made the letters disappear. I was in my late 40s at the time, I've worn glasses since the third grade, and I couldn't read the keys.

When I got back to the office, I reached out to the product team along with the design group. That's when I found out some people on the product team weren't even aware that the keyboard had changed. And the design change had never gone through our usability and accessibility review.

The fix was simple. HP already used a standard keyboard, black keys, white letters, on the previous generation of this laptop, and it fit this one exactly. The factory swapped it in. We pulled the chrome ones off the shelves. Sales started coming back within a few weeks, and it was back to plan within a quarter.

Then we fixed the process that caused this problem. From then on, the design and accessibility review was required, so a change like that couldn't slip through again.

So how did the four skills play out?

Framing. The team asked, "What do our competitors have that we don't?" That question already had a fix built into it, and it sent them straight to specs.

Root cause. They went deep on specs, and all their data was about people who bought. The keyboard never made their list. It wasn't even on their radar. The answer was with the people who walked away, and the salesmen were the ones who'd seen them.

Alternatives. A spec upgrade across product lines would've cost tens of millions of dollars. The real fix was a keyboard we already had.

Choosing and testing. It was cheap and easy, so we just made the change and watched sales. And then we fixed the process, so it wouldn't come back.

Where to Start

All four of the skills are important. However, if you're only able to focus on one of these four this year, make it framing the problem.

Spending the time to understand and scope the problem pays off when it comes to finding the solution later. This is the poster child for slow is fast.

In my workshops, we spend days teaching how to identify, validate and write up a problem statement. Days. Because most people spend about five minutes understanding a problem and then jump straight to a fix which turns out not to solve the problem.

Get good at framing, and honestly, the other three get a whole lot easier. And you'll be miles ahead of your peers.

Remember what I said at the start of this episode? The people who get the hard assignments, the ones who move up, are the ones who can walk into a mess and figure out what's really going on. These four skills are how you become that person.

Więcej odcinków z kanału "The Innovators Studio with Phil McKinney"