Problem Solving

At work, problem solving means breaking a messy problem into parts until the real cause shows, and fixing that cause so the problem doesn’t return.

Most problems at work arrive as a symptom, like a late delivery or a client who is upset. The quick fix treats what’s visible, and the same problem comes back the next week in a new form. Problem Solving looks underneath, at the step in the process that keeps producing it.

In the day-to-day, it starts with precision. A person names exactly what’s going wrong, like an order that arrives without its invoice, instead of saying the process feels off. Then they ask how far it reaches: every client, or only the ones in one region?

With experience, the person handles problems that have more than one possible fix. They compare the options by how much each would help and how much effort it takes, and choose on that basis instead of on instinct. Once a fix is in, they show with data that it worked, often in more than one area, before closing the problem.

At the highest reach of the scale, Problem Solving changes how a company works. A leader finds a fix that reaches the company’s suppliers and partners, or turns a threat, like a new regulation, into an advantage.

Where it shows up

A heating and plumbing company keeps hearing the same complaint: the technician came, and two days later had to come back. About one job in five needs a second visit. In the Monday meeting, the first idea is to retrain the technicians.

The service manager wants to know more before choosing a fix. She pulls the last month’s return visits and sorts them by type of job. Most of them are water heater repairs. Then she reads the technicians’ notes on those jobs and asks why, one step at a time. Why the second visit? The right part wasn’t in the van. Why not? Each water heater model takes a different part, and nobody knows the model until the technician gets there.

So the fix happens before the visit. When a customer books a water heater repair, the scheduler now asks for a photo of the label on the heater, and the technician arrives with the right part.

Two months later, about one job in twenty needs a second visit.

Retraining would have fixed a problem the technicians didn’t have. Problem Solving was taking the complaint apart until the real cause showed up, in the booking call, and fixing it there.

What it changes at work

A problem fixed at the surface usually finds its way back.

In May 2026, the Skills Builder Partnership, a UK organization that works on essential skills, analyzed the latest OECD Survey of Adult Skills, which tests how adults reach a goal when the way to get there isn’t obvious. Workers who scored higher on problem solving earned more. In the UK, one standard deviation higher on the test went with wages 13.9% higher, and across the countries in the analysis the gap ranged from 3.7% to 17.3%. The difference was largest for workers between 35 and 54.

The test asks people to find a way forward when no one hands them the answer, which is the heart of Problem Solving. It pays off for the company too: a problem fixed at its cause stops costing time every week, and the people who can do that become the ones everyone calls first.

What it looks like, from 0 to 20

On Skill Deck’s scale, each of the 21 levels of Problem Solving, from 0 to 20, is a Practice with a name and an example. Three of them, from one risk spotted early to the habits of a whole company:

9, Hazard Identification

Spots a risk before it turns into a problem, like a supplier that will hit its capacity limit in a month, and starts the search for a backup.

11, Interface Governance

Fixes problems that live between two teams, like a handoff from sales to operations that keeps losing details, with a shared template both sides use.

18, Cultural Fix Leadership

Finds the habit behind a stubborn problem, like slow delivery caused by fear of failing, and changes the way the company treats mistakes.

Skill Deck reads each person’s level from the meetings they already sit in, in how they talk about a problem before anyone has fixed it.

One thing to try if you want to develop this Skill

We recommend starting with Practice 7, Root Cause Diagnosis. It uses one question asked several times in a row: why?

1. Think of a small problem that keeps coming back, like a weekly meeting that never starts on time.
2. Before you try to fix it, set aside five minutes to ask why it happens.

The reminder asks people to try harder. The second fix changes the thing that made them late.

Over the next month, watch whether the meeting starts on time without anyone asking. If it does, you found the cause, and the same question will work on the next problem.