Skill

Problem-Solving

Solving problems systematically, diagnosing what's actually wrong before jumping in with a fix.

Problem-Solving Find this on the mind-map

Introduction

You run into problems every single day as a leader: team conflict, a stalled project, a budget that won't stretch, a crisis nobody saw coming. Whether the problems show up isn't the variable. How you approach them is.

It's really a series of steps, and the order is where most of the value comes from.

  • Start by stating the problem in plain, observable terms, before you let anyone, including yourself, jump to a fix.
  • Separate the symptom from the cause, and keep asking "why" until the answer stops just repeating the symptom back to you.
  • Go ask the people closest to the actual work, because whoever's living the problem day to day usually knows the detail that explains it.
  • Only after all that do you pick a fix to try, and pick one small enough that you can actually test it.

Research from McKinsey found that leaders who approach problems systematically are three times more likely to implement solutions that actually work.

Why It Matters for Leaders

Most leaders skip all of this. They jump straight to a fix and "hope for the best".

The second common failure is showing up with the answer already decided. The moment you open with your solution, the conversation turns into a debate about that solution, and the actual problem never gets defined out loud, and nobody can tell afterward whether the fix even worked.

When you've built this skill:

  • Problems get named precisely enough that naming them sometimes solves them outright.
  • Your fixes are testable, so you and your team can tell a real solution apart from a rearrangement.
  • Recurring issues actually get retired instead of endlessly managed.
  • You're aiming at the real problem, not the symptoms it keeps throwing off.

As Einstein put it: if he had an hour to solve a problem, he'd spend fifty-five minutes thinking about the problem and five minutes thinking about solutions. That ratio is basically the whole skill.

Your chat with Kyoshi about Problem-Solving

What to do next

Master Problem-Solving by taking the mini-course

Frameworks related to Problem-Solving

Skills related to Problem-Solving

Creative Thinking

Creative Thinking

Finding the approach everyone else misses, by challenging assumptions, widening your options, and testing unfamiliar ideas cheaply before you commit to them.

Decision-Making

Decision-Making

Making a measured call fast, on information that's never complete, and correcting course as evidence comes in instead of defending your first answer.

Leading with AI

Leading with AI

Knowing when to trust AI-generated work, when to dig into the reasoning behind it, and how to use it without letting your own judgment go soft.

Mental Agility

Mental Agility

Matching how you lead to the situation in front of you and the person you're leading, because the approach that worked yesterday might be exactly wrong today.

Pattern Recognition

Pattern Recognition

Noticing that a handful of small, separate signals are actually one thing, and naming the trend before it's obvious to everyone else.

Political Savvy

Political Savvy

Reading the relationships, incentives, and unwritten rules that actually decide whether your idea gets adopted, not just whether it's the right one.

Prioritization

Prioritization

Picking the handful of things that actually matter and putting the team's energy there, which means saying no to almost everything else.

Productivity

Productivity

Directing your time and energy at the work that actually matters, instead of letting whatever lands first run your day.

Strategic Thinking

Strategic Thinking

Stepping back to see where things are heading, and actually letting that change what you do today.

Systems Analysis

Systems Analysis

Tracing how a decision in one part of the organization moves through the rest of it, instead of treating your team as its own island.