๐Ÿ’กCritical Thinking

Problem-Solving Models

Study smarter with Fiveable

Get study guides, practice questions, and cheatsheets for all your subjects. Join 500,000+ students with a 96% pass rate.

Get Started

Why This Matters

Problem-solving isn't just about finding answers. It's about how you think through challenges systematically. In critical thinking, you're tested on your ability to recognize which approach fits which situation, understand the reasoning behind each model, and apply structured thinking to messy, real-world problems. These models represent different philosophical approaches: some prioritize empirical evidence, others emphasize human-centered design, and still others focus on continuous improvement or root cause identification.

Don't just memorize the steps of each model. Know when and why you'd choose one over another. Can you explain why the Scientific Method works for testable hypotheses but Design Thinking works better for ambiguous human problems? Can you distinguish between models that generate ideas versus those that evaluate them? That comparative thinking separates surface-level recall from genuine critical thinking mastery.


Systematic Inquiry Models

These models follow a structured, sequential process where each step builds logically on the previous one. The underlying principle is that complex problems become manageable when broken into discrete, ordered phases.

Scientific Method

The Scientific Method is designed to produce conclusions grounded in testable, repeatable evidence. It follows a specific sequence:

  1. Observation of a phenomenon or pattern
  2. Hypothesis formation (a testable explanation)
  3. Experimentation to gather data
  4. Analysis of results to confirm or reject the hypothesis

Empirical validation requires that results be reproducible. If others can't replicate your findings, the conclusion remains unverified. And assumption questioning is built into the process: every hypothesis must survive attempts to disprove it, not just confirm it. This is a key distinction. You're not looking for evidence that supports your idea; you're testing whether your idea holds up against evidence that might contradict it.

IDEAL Problem-Solving Model

IDEAL gives you a complete cycle from recognizing a problem through reflecting on your solution:

  • Identify the problem
  • Define it clearly
  • Explore possible solutions
  • Act on the best option
  • Look back at the results

The Explore phase is where multiple solutions are generated before any action is taken. This prevents premature commitment to the first idea that comes to mind. The Look back phase builds metacognitive skills: understanding how you solved the problem improves your future problem-solving ability.

PDCA (Plan-Do-Check-Act) Cycle

PDCA treats every solution as a hypothesis to be tested, not a final answer. That's what makes it a continuous improvement loop.

  • Plan: Define the problem and propose a change
  • Do: Implement the change on a small scale
  • Check: Measure actual results against expected outcomes (without data, you're just guessing)
  • Act: Standardize what worked, or adjust and cycle through again

Each cycle refines the previous one, making PDCA ideal for ongoing process optimization rather than one-time problem-solving.

Compare: Scientific Method vs. PDCA Cycle: both test hypotheses through evidence, but the Scientific Method aims for definitive conclusions while PDCA assumes continuous refinement. If asked about one-time research questions, use Scientific Method; for ongoing organizational improvement, PDCA is your example.


Root Cause Identification Models

Rather than treating symptoms, these models dig deeper to find why problems occur in the first place. The core insight is that surface-level fixes often fail because the underlying cause remains unaddressed.

Root Cause Analysis

Root Cause Analysis is a broad approach built on one key distinction: symptoms (what you see happening) versus root causes (why it's happening). A hospital noticing increased patient falls could treat the symptom by adding more staff to catch people. But a root cause analysis might reveal that a specific medication's side effects are causing dizziness, pointing to a completely different solution.

The goal is prevention-focused: eliminate recurrence entirely rather than manage ongoing problems. Systematic tracing tools like the 5 Whys and Fishbone Diagram (covered below) provide structured ways to avoid jumping to conclusions.

5 Whys Technique

This technique involves asking "why" repeatedly (typically five times) until you reach a cause that can actually be addressed. Here's how it works in practice:

  1. Problem: The project was delivered late.
  2. Why? The final review took longer than expected.
  3. Why? The draft had significant errors.
  4. Why? The team didn't follow the style guidelines.
  5. Why? The guidelines were never distributed to new members.
  6. Root cause โ†’ fix: Create an onboarding process that includes distributing guidelines.

Simplicity is the strength here. No special tools are required, making it accessible for quick analysis in any context. Note that this technique goes for depth over breadth: it drills vertically into one causal chain rather than mapping all possible factors.

Fishbone Diagram (Ishikawa Diagram)

The Fishbone Diagram takes the opposite approach: breadth over depth. It visually organizes potential causes into standard categories:

  • People (training, staffing, communication)
  • Processes (procedures, workflows)
  • Materials (supplies, data quality)
  • Equipment (tools, technology)
  • Environment (workspace, external conditions)
  • Management (policies, leadership)

This visual mapping works especially well for teams because everyone can see the full picture and contribute to different branches. It complements the 5 Whys nicely: use the Fishbone to identify which categories deserve attention, then use 5 Whys to drill into the most promising branches.

Compare: 5 Whys vs. Fishbone Diagram: both support root cause analysis, but 5 Whys goes deep on a single causal chain while Fishbone maps broadly across categories. Strong critical thinkers use them together: Fishbone first to identify where to look, then 5 Whys to investigate the most promising branches.


Creative Generation Models

These models prioritize producing ideas before evaluating them. The principle here is that premature criticism kills innovation. Separate divergent thinking (generating options) from convergent thinking (selecting the best one).

Brainstorming

Judgment-free ideation is the core rule: all ideas are captured without immediate criticism. Quantity precedes quality. Unconventional thinking is explicitly encouraged because seemingly "bad" ideas often spark genuinely innovative solutions. Someone suggesting "what if we just eliminated the whole process?" might sound absurd, but it could lead the group to realize that half the steps are unnecessary.

Brainstorming has a flexible structure. It can be free-form, or it can use guided variations like reverse brainstorming (asking "how could we make this problem worse?" to reveal hidden causes) or brainwriting (writing ideas silently before sharing, which prevents louder voices from dominating).

Design Thinking

Design Thinking is a comprehensive framework, not just a single technique. It follows five phases:

  1. Empathize: Understand users' actual needs through observation and interviews, not assumed needs
  2. Define: Frame the problem from the user's perspective
  3. Ideate: Generate a wide range of possible solutions
  4. Prototype: Quickly make ideas tangible (sketches, models, mockups)
  5. Test: Get real feedback and refine based on what you learn

The prototype-test-iterate cycle means ideas are refined based on real feedback, not theoretical debate. Design Thinking's tolerance for ambiguity makes it ideal for complex problems where the "right answer" isn't clear at the start. You discover the solution through the process itself.

Compare: Brainstorming vs. Design Thinking: both generate creative solutions, but Brainstorming is a single-session technique while Design Thinking is a comprehensive framework. Brainstorming answers "what could we do?" while Design Thinking first asks "what do users actually need?"


Evaluation and Decision Models

Once you have options, these models help you choose systematically. The key insight is that good decisions require explicit criteria. Otherwise, bias and gut reactions dominate.

Six Thinking Hats

Six Thinking Hats uses a parallel thinking structure where everyone adopts the same perspective at the same time, then switches together. The six hats are:

  • White Hat: Facts and data only. What do we know? What data is missing?
  • Red Hat: Emotions and intuition. How does this feel? What's your gut reaction?
  • Black Hat: Caution and risks. What could go wrong? Where are the weaknesses?
  • Yellow Hat: Benefits and optimism. What are the advantages? Why could this work?
  • Green Hat: Creativity and alternatives. What other options exist? What's a new angle?
  • Blue Hat: Process management. Where are we in the discussion? What's the next step?

Conflict reduction happens naturally because you're not arguing positions. Everyone explores the same perspective together before moving on. This also ensures comprehensive coverage: emotional, logical, creative, and critical viewpoints all get airtime before decisions are made.

Decision Matrix

A Decision Matrix forces you to define what matters before comparing options, which reduces post-hoc rationalization (convincing yourself your favorite was the best choice all along).

Here's how to build one:

  1. List your options as rows
  2. List your evaluation criteria as columns
  3. Assign a weight to each criterion based on importance
  4. Score each option against each criterion
  5. Multiply scores by weights and compare totals

The visual layout makes trade-offs clear: you can see when one option excels in some areas but falls short in others. Bias reduction comes from the structure itself. You can't ignore inconvenient criteria when they're built into the matrix.

Compare: Six Thinking Hats vs. Decision Matrix: both structure evaluation, but Six Thinking Hats organizes perspectives (how to think) while Decision Matrix organizes criteria (what to measure). Use Six Thinking Hats for group discussion and Decision Matrix for final selection among defined options.


Quick Reference Table

ConceptBest Examples
Sequential/Systematic ProcessScientific Method, IDEAL Model, PDCA Cycle
Root Cause IdentificationRoot Cause Analysis, 5 Whys, Fishbone Diagram
Creative Idea GenerationBrainstorming, Design Thinking
Structured EvaluationSix Thinking Hats, Decision Matrix
Continuous ImprovementPDCA Cycle, Design Thinking
Visual/Collaborative ToolsFishbone Diagram, Six Thinking Hats, Decision Matrix
Human-Centered ApproachesDesign Thinking, Six Thinking Hats
Quick/Accessible Techniques5 Whys, Brainstorming

Self-Check Questions

  1. Which two models both emphasize iterative cycles but differ in their primary purpose: one for process improvement and one for human-centered innovation?

  2. You've identified that customer complaints are increasing, but you're not sure why. Which two tools would you combine to first map all possible causes and then drill into the most likely one?

  3. Compare and contrast the Scientific Method and Design Thinking: What types of problems is each best suited for, and why would empirical validation work for one but not the other?

  4. A team keeps arguing about which solution to implement, with different members championing their favorites. Which model would help them evaluate options more objectively, and which would help them explore perspectives without conflict?

  5. If an essay prompt asks you to "describe a systematic approach to solving a problem you've never encountered before," which model provides the most complete framework from problem identification through post-implementation reflection?