A Problem Solving Framework That Starts at the Cause

The problem

Think of the thing that keeps coming back. The same argument with the same person every few weeks, in slightly different words. The money that is somehow gone by the 20th no matter what you earn. The room in the house that ends up a mess within a fortnight of every clear-out. You have solved each of these before — that is the strange part. You fixed it, it worked, and then it came back, which is the clearest possible sign that what you fixed was not the thing causing it.

The short answer

A problem solving framework separates finding the cause from finding the fix, because most people jump straight to a fix and end up solving the wrong problem faster. The problem solving steps below start by tracing the symptom backward, then check the leading fix against the real incentives in the system before spending resources on it. Problem solving methods that skip the cause-tracing step tend to produce a longer list of patches, not fewer problems.

The framework, step by step

Describe the symptom precisely
Write down exactly what's going wrong, when it started, and who it's affecting. 'Sales are down' isn't precise; 'renewals dropped for accounts signed after the pricing change' is.
Trace it back to a cause
Ask why, five times, each answer more specific than the last, until you hit something you can actually act on. A five whys pass usually ends at a process or an incentive, not a person.
Do this step now — Five Whys →
Check who benefits from the problem staying
Before you fix anything, map the incentives of everyone touching the process. A fix that ignores an incentive map gets quietly worked around within a month.
Do this step now — Who's Paid For This? →
Build the fix from fundamentals
Don't copy the last fix that half-worked. Run a first-principles breakdown of what actually has to be true for the problem to be solved, then build the fix from that instead of from habit.
Do this step now — Down to the Bricks →
Ship the fix and watch the cause
Apply the narrowest change that addresses the root cause, then watch the original symptom, not just the fix. If the symptom comes back, the cause wasn't what you thought it was.

What it looks like

Take a team whose deploys keep breaking the same billing integration every few weeks. The team's first instinct is to add another manual check before each deploy, which is a symptom fix. Running five whys instead traces the failure to a shared test environment that's rarely updated, which traces further back to no one owning that environment. An incentive map shows the two teams sharing the environment are each measured on their own release speed, so neither has a reason to maintain shared infrastructure. The real fix is assigning ownership of the test environment to one team's roadmap, not adding another manual check to a process that already has too many.

Questions people ask

What are the steps in a problem solving framework?

A typical structured problem solving process runs: describe the symptom precisely, trace it back to a cause, check the incentives involved, build a fix from that cause, then confirm the symptom is actually gone. Skipping the cause-tracing step is the most common way this breaks down.

What is the difference between problem solving and decision making?

Problem solving starts from something broken and works backward to a cause; decision making starts from a choice between options already on the table. The two often meet in the middle, once problem solving produces a short list of fixes to decide between.

Why do problem solving methods fail on recurring problems?

Recurring problems usually get treated as one-off incidents, so each one gets its own quick patch instead of a shared cause. A five whys pass or a root-cause analysis is what stops the pattern, because it names the cause once instead of rediscovering it every time.

How do I know if I've found the real cause or just a deeper symptom?

If fixing it would also prevent two or three other problems you've seen, it's probably close to the real cause. If the fix only prevents the one thing you're currently annoyed about, keep tracing.

Decision MakingWhat is decision making, really? The definition, the stages every choice passes through, ... Critical Thinking FrameworkA five-step critical thinking framework for testing claims and pitches: state them plainl... Root analysisRoot cause analysis means tracing a problem past its symptoms to the cause that, once fix... IncentivesThe incentives mental model: behavior follows reward structures, not stated intentions. H...

Reading it isn't the same as being able to do it

Short daily drills on real decisions · free to start, no signup to try

Try a drill — no signup →