Complicated-versus-Complex Problem Test
Classify the problem before applying tools that can never solve it.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 4
- Confidence
- 97%
This test distinguishes two kinds of difficulty before choosing a response. A complicated problem may contain many parts, but enough computational power, technical knowledge, and engineering can solve it; Brooks uses a jet engine and a toaster as examples. A complex problem is often easy to state, yet its interacting living elements and uncertainty prevent a final reliable solution; love, a cat, or the outcome of a football game fit this class. The practical error is answering a complex human need with a complicated technical product. Classify the challenge first, then use tools for complicated components while reserving judgment, participation, patience, and relationship for complexity. The output is a better-fitting response rather than the false reassurance of a sophisticated but mismatched solution.
Origin
Brooks learned the distinction from his mathematician father, who used it to explain why technological answers cannot satisfy every human need.
Core principles
- 01Complicated problems yield to computation, expertise, and technical power.
- 02Complex problems can be easy to understand while remaining impossible to solve completely.
- 03Human concerns such as love cannot be reduced to technical optimization.
- 04A capable solution still fails when it belongs to the wrong problem class.
How to run it
- 1
Describe the desired outcome
State what success would look like without naming a preferred tool or solution.
Pro tip Use observable language where possible.
Watch out Starting with a tool can hide the real problem class.
- 2
Test computability
Ask whether sufficient data, expertise, and computational power could reliably produce the answer.
Watch out Many variables do not automatically make a problem complex.
- 3
Classify the challenge
Mark it complicated if it is technically solvable and complex if it remains uncertain despite being understandable.
Pro tip Split mixed challenges into complicated and complex components.
Watch out Do not label a problem complex merely because the available tools are weak.
- 4
Match the response
Use engineering and computation for complicated work; use judgment, relationship, experimentation, and acceptance for complexity.
Pro tip Let technical tools support a complex situation without claiming they resolve it.
Watch out A precise output can still be the wrong kind of answer.
In the wild
Brooks's father contrasted love, which is easy to recognize but cannot be finally solved, with a jet engine, whose enormous technical complexity can still be mastered through engineering. Brooks argued that people remain unsatisfied when they seek computational products for needs such as love.
→ The distinction directs technical power toward solvable components without mistaking it for a complete answer to a human need.
Common mistakes
Using sophistication as proof of fit
A powerful computer or elaborate process cannot solve a challenge simply because the tool is impressive.
Rejecting tools for complex work
A complex problem can still contain complicated subproblems that benefit from technical help.
Is it for you?
Best for
It is best for leaders and individuals deciding whether a challenge needs engineering, judgment, relationship work, or acceptance.
Not ideal for
It is not ideal for avoiding quantitative analysis when a problem is genuinely calculable.
From the transcript
“Complicated problems are all the things that you can solve with computational horsepower and tech.”
“Complex problems are super easy to understand, but you can never solve them.”
“Love is complex. A jet engine is complicated. A cat is complex, a toaster is complicated.”
From the episode
#692: Arthur C. Brooks — How to Be Happy, Reverse Bucket Lists, The Four False Idols, Muscular Philosophies, Practical Inoculation Against the Darkness, and More
Arthur C. Brooks