π§ Problem Solving
Systematically decompose problems, find root causes, and generate effective solutions. This category covers 25 classic mental models, each with a full definition, real-world cases, use-case guidance, common misuses, and a direct link to apply it in MindMax.
Model Listβ
| # | Model | Core Idea | Typical Use Cases |
|---|---|---|---|
| 1 | 5 Whys | Ask "why" five times in sequence to move from symptom to root cause | Engineering post-mortems, process improvement, QA |
| 2 | MECE | Structure your analysis so categories are Mutually Exclusive and Collectively Exhaustive | Consulting frameworks, reporting structures, research |
| 3 | Root Cause Analysis | Distinguish surface symptoms from the underlying cause that must actually be fixed | Engineering failures, business problems, repeat errors |
| 4 | Issue Tree | Decompose a complex question into a tree of independent, solvable sub-problems | Strategy consulting, complex diagnoses, structured analysis |
| 5 | Rubber Duck Debugging | Articulating a problem clearly to someone else (or an object) often reveals the solution | Code debugging, creative blocks, decision clarity |
| 6 | Abstraction Laddering | Move up (why?) to reframe the problem and down (how?) to find concrete solutions | Requirements gathering, product definition, design |
| 7 | Thought Experiment | Construct an imagined scenario to probe the logic of a theory without real-world testing | Philosophy, physics intuition, ethical reasoning |
| 8 | Divide and Conquer | Split an intractable problem into smaller, independently solvable pieces | Algorithm design, project management, learning strategy |
| 9 | Constraint Relaxation | Temporarily remove constraints you assume are fixed, then reason from the freer space | Innovative design, negotiation, creative problem solving |
| 10 | Analogical Reasoning | Borrow the structure of a solved problem in one domain to solve an unsolved one in another | Cross-domain innovation, rapid learning, explanation |
| 11 | Fermi Estimation | Make reasonable quantitative estimates by decomposing into knowable sub-quantities | Market sizing, project scoping, sanity checks |
| 12 | Working Backwards | Start from the ideal end-state and work back to identify the steps required to reach it | Product development, goal setting, Amazon PR/FAQ method |
| 13 | Falsification | Actively seek evidence that could disprove your hypothesis β strong theories survive attempts to kill them | Scientific reasoning, hypothesis testing, decision-making |
| 14 | Socratic Method | Expose hidden assumptions and contradictions through systematic, probing questions | Coaching, teaching, requirement clarification |
| 15 | Counterfactual Thinking | Ask "what would have happened if X had been different?" to understand true causality | Post-mortem analysis, attribution, historical analysis |
| 16 | Black Box Thinking | Treat every failure as data and systematically analyze it to improve the next attempt | Engineering, aviation safety, organizational learning |
| 17 | Scientific Method | Observe, hypothesize, predict, experiment, analyze β the most reliable engine for truth | Research, product experimentation, strategic decisions |
| 18 | Fishbone Diagram (Ishikawa) | Visually map all possible causes of a problem across categories to find the root driver | Manufacturing QC, process analysis, team problem-solving |
| 19 | Cynefin Framework | Classify situations as Simple, Complicated, Complex, or Chaotic β each demands different response | Management, crisis response, decision frameworks |
| 20 | Problem Reframing | Deliberately change the frame around a problem to unlock solutions invisible from the original frame | Design thinking, creative problem solving, negotiation |
| 21 | Inductive vs. Deductive Reasoning | Build general principles from specific cases (inductive) or apply general rules to specific cases (deductive) | Logic, research design, argumentation |
| 22 | Proximate vs. Root Cause | Distinguish the immediate trigger of an event from the deeper systemic cause underlying it | Incident analysis, policy design, strategy |
| 23 | Minimum Viable Test | Design the smallest experiment that would give you the most critical piece of missing information | Product validation, research, hypothesis prioritization |
| 24 | Lateral Re-entry | Step away from a stuck problem, let your diffuse thinking mode work, then return fresh | Creative blocks, complex reasoning, innovation |
| 25 | Steel-Manning the Problem | Construct the strongest possible version of a problem before attempting to solve it | Strategy, debate prep, avoiding shallow solutions |
| 26 | Cognitive Load | Manage mental effort by minimizing extraneous friction and optimizing working memory | Instructional design, UX, team productivity |
| 27 | Getting Things Done (GTD) | Externalize commitments into a trusted system to clear mental space for execution | Task management, stress reduction, high-volume work |
| 28 | Second Brain | An external, digital system that captures, organizes, and retrieves knowledge β extending biological memory | Information-heavy work, creative projects, long-term learning, decision-making |
| 29 | Ludic Fallacy | The error of applying simplified game-based models to the complex, messy, and unpredictable real world | Risk assessment, strategic planning, investment decisions, policy design |
Choosing the Right Modelβ
Where in the problem-solving process are you stuck?
β
βββ Symptoms are clear but cause is unknown β 5 Whys / Root Cause Analysis / Fishbone Diagram
βββ Problem too large and undefined β Issue Tree / Divide and Conquer / MECE
βββ Analysis framework might be missing something β MECE
βββ Explanation doesn't feel right β Falsification / Socratic Method
βββ Thinking has stalled, need a reset β Rubber Duck / Lateral Re-entry
βββ Problem definition itself may be wrong β Abstraction Laddering / Reframing
βββ Brain feels overwhelmed by complexity β Cognitive Load / Getting Things Done
βββ Need a rough quantitative estimate β Fermi Estimation
βββ Know the goal but not the path β Working Backwards
βββ Need to break a constraint β Constraint Relaxation
βββ Solution exists in another domain β Analogical Reasoning
βββ Need to classify before responding β Cynefin Framework
βββ Cause is immediate vs. systemic? β Proximate vs. Root Cause
Combine with Other Categoriesβ
Problem Solving models work especially well alongside:
- βοΈ Decision Making β once you understand the system, make the decision
- π§© Cognitive Biases β check your blind spots before you act
- π― Use-Case Guides β not sure where to start? Choose by scenario instead
AI-assisted practice works better
Learning a model conceptually is only half the job. In MindMax, you can input a real problem and let AI guide you through the model step by step.