Unit 1: Foundations of Problem Solving, Problem Framing & Design Thinking Mindset

1. Introduction: The Need for Human-Centered Problem Solving

In traditional engineering paradigms, problem solving has historically centered on technical optimization: taking a predefined problem statement, applying linear analytical procedures, and calculating a mathematically or mechanically sound solution. However, contemporary socio-technical challenges—such as sustainable urban mobility, climate adaptation, inclusive healthcare delivery, and enterprise digital transformation—are rarely straightforward or static.

Design Thinking emerged as an agile, non-linear, human-centered innovation methodology. Rather than jumping prematurely into technical solutioneering, Design Thinking reframes engineering by anchoring the entire problem-solving lifecycle in deep human empathy, collaborative ideation, rapid tangible prototyping, and continuous iterative testing.

2. Core Philosophy and Mindsets of Design Thinking

Design Thinking is not merely a sequence of steps; it is a cognitive mindset characterized by five fundamental attitudes:

[Empathy for Users] ──> [Bias Toward Action] ──> [Embracing Ambiguity] ──> [Radical Collaboration] ──> [Iterative Refinement]

1. Human-Centered Empathy: Prioritizing the lived experiences, emotional pain points, unmet needs, and behavioral context of real human stakeholders.
2. Bias Toward Action: Favoring tangible experimentation and experiential doing over endless theoretical debate; "thinking by building."
3. Embracing Ambiguity and Failure: Treating failures as cheap, informative learning signals; cultivating psychological safety to iterate without fear.
4. Radical Collaboration: Convening cross-disciplinary teams combining engineers, social scientists, designers, domain operators, and end-users.
5. Mindfulness of Process: Consciously shifting between generative (divergent) exploration and analytical (convergent) decision-making.

3. The Five Stages of the Stanford d.school Design Thinking Framework

The d.school (Hasso Plattner Institute of Design at Stanford) articulates a five-stage non-linear model:

CODECopy Code
┌─────────────┐     ┌───────────┐     ┌──────────┐     ┌───────────┐     ┌──────────┐
│ 1. EMPATHIZE│ ──> │ 2. DEFINE │ ──> │ 3. IDEATE│ ──> │4.PROTOTYPE│ ──> │ 5. TEST  │
└─────────────┘     └───────────┘     └──────────┘     └───────────┘     └──────────┘
       ▲                  ▲                 ▲                │                 │
       │                  └─────────────────┴────────────────┴─────────────────┘
       └────────────────────────────────── Iterative Feedback Loops ───────────┘

[!NOTE]
The five stages are non-linear and iterative. Feedback gathered during testing frequently loops back to redefine the user's core problem, inspire entirely new ideation sessions, or reveal that initial empathy assumptions were flawed.

4. Cognitive Modalities: Divergent vs. Convergent Thinking

Effective problem-solving requires alternating systematically between two opposing cognitive modes:

The Double Diamond Model (UK Design Council)

The Double Diamond visualizes the problem-solving lifecycle through two successive expansion-contraction diamonds:

CODECopy Code
  PROBLEM SPACE (Discover & Define)              SOLUTION SPACE (Develop & Deliver)
        Diverge         Converge                      Diverge         Converge
           /\              \/                            /\              \/
          /  \            /  \                          /  \            /  \
         /    \          /    \                        /    \          /    \
        /      \        /      \                      /      \        /      \
       /        \      /        \                    /        \      /        \
  [General Issue]  [Discover]  [Define Problem]  [Develop Ideas]  [Deliver Solution]

1. Diamond 1: Finding the Right Problem to Solve
   • Discover (Diverge): Broad qualitative exploration into the problem space without preconceived notions.
   • Define (Converge): Synthesizing findings to identify the root challenge and frame the core problem statement.
2. Diamond 2: Finding the Right Way to Solve It
   • Develop (Diverge): Generating diverse solution architectures, prototypes, and operational models.
   • Deliver (Converge): Testing, piloting, refining, and scaling the finalized, validated solution.

5. Comprehensive Taxonomy of Problems

Not all problems are structurally equivalent. Categorizing problems accurately dictates whether linear mathematical algorithms, expert heuristics, or agile design thinking methodologies should be applied.

1. Well-Defined vs. Ill-Defined Problems

• Well-Defined Problems: Possess clear initial states, unambiguous goal conditions, and deterministic transition rules. Objective evaluation exists to verify whether a solution is mathematically correct (e.g., solving quadratic equations, traversing a shortest-path graph, playing chess).
• Ill-Defined Problems: Suffer from ambiguous initial states, shifting or unspecified success criteria, and incomplete operational information (e.g., designing an engaging educational curriculum, reducing smartphone addiction among teenagers).

2. Tame vs. Wicked Problems (Rittel & Webber, 1973)

Horst Rittel and Melvin Webber formulated the concept of Wicked Problems to distinguish social and systemic planning challenges from standard scientific engineering challenges:

3. The Cynefin Framework (Dave Snowden)

The Cynefin framework helps leaders and engineers make sense of problem complexity and adopt appropriate management practices:

CODECopy Code
           COMPLEX                       COMPLICATED
     (Domain of Emergence)            (Domain of Experts)
     Probe ─> Sense ─> Respond        Sense ─> Analyze ─> Respond
     [Emergent Practice]              [Good Practice]
     -------------------------------------------------
     Act ─> Sense ─> Respond          Sense ─> Categorize ─> Respond
     [Novel Practice]                 [Best Practice]
            CHAOTIC                          CLEAR
       (Domain of Crisis)             (Domain of Simplicity)

1. Clear / Simple (Ordered): Cause-and-effect relationships are self-evident to everyone. Standard Operating Procedures (SOPs) apply. Action: Sense $\rightarrow$ Categorize $\rightarrow$ Respond (Best Practice).
2. Complicated (Ordered): Cause-and-effect relationships exist but require specialized technical expertise and analytical investigation. Action: Sense $\rightarrow$ Analyze $\rightarrow$ Respond (Good Practice).
3. Complex (Unordered): Cause-and-effect can only be deduced in retrospect; unpredictable emergent behavior dominates. Design thinking excels here. Action: Probe $\rightarrow$ Sense $\rightarrow$ Respond (Emergent Practice).
4. Chaotic (Unordered): Immediate crisis; no discernible cause-and-effect relationship exists. Action must be taken instantly to establish stability. Action: Act $\rightarrow$ Sense $\rightarrow$ Respond (Novel Practice).

4. Technical vs. Adaptive Challenges (Heifetz & Linsky)

• Technical Challenges: The problem is clearly understood, and adequate solutions exist within current institutional knowledge, organizational structures, or technical algorithms. Experts can solve them.
• Adaptive Challenges: Require stakeholders themselves to change their values, priorities, habits, or behavioral paradigms. Solutions require social learning and cultural transformation rather than top-down technical fixes.

6. Problem Framing and Cognitive Reframing

The Danger of Premature Problem Definition

Albert Einstein famously noted: "If I had an hour to solve a problem, I'd spend 55 minutes thinking about the problem and 5 minutes thinking about solutions."

In engineering, jumping immediately to solutioneering without critical examination often results in technically flawless implementations of the wrong thing.

The Classic "Slow Elevator" Paradox

Consider an office high-rise where tenants complain: "The elevator is too slow!"

• Narrow Technical Frame: The elevator is too slow $\rightarrow$ Upgrade motor horsepower, reprogram acceleration curves, install faster pulleys. (Cost: $250,000, 3 months disruption).
• Reframed Human Experience Frame: The wait is frustrating and boring $\rightarrow$ Install full-length mirrors next to the elevator doors, place interactive display screens, provide ambient music. (Cost: $2,500).
• Outcome: Complaints drop to zero. The technical speed was never the root human problem; the perceived boredom of waiting was the true issue.

Problem Reframing Tools

1. The 5 Whys Technique (Taiichi Ohno, Toyota Production System): Asking "Why?" iteratively at least five times to peel away surface-level operational symptoms and expose underlying systemic root causes.
2. Ishikawa (Fishbone) Diagram: Systematically categorizing potential contributing factors into major buckets (People, Process, Equipment, Environment, Materials, Management).
3. Point of View (POV) Framework:
   $\mathbf{POV} = [\text{Specific User Description}] \textbf{ needs } [\text{Deep Human Need}] \textbf{ because } [\text{Surprising Emotional / Behavioral Insight}]$
4. "How Might We" (HMW) Questions: Translating the POV problem statement into open-ended springboards for ideation (e.g., "How might we make waiting for the elevator feel like a refreshing social pause?").

7. Cognitive Biases Impairing Engineering Problem Solving

Engineers are susceptible to subconscious psychological biases that distort problem framing:

8. Common Practitioner Pitfalls and Best Practices

9. Quick Revision & Exam Summary

The 5 d.school Stages

1. Empathize (Understand human experience)
2. Define (Formulate POV & HMW)
3. Ideate (Divergent concept generation)
4. Prototype (Low-fidelity tangible artifacts)
5. Test (Feedback collection and refinement)

Rittel's Wicked Problem Markers

• No definitive formulation.
• No stopping rule.
• Solutions are "better/worse", not "true/false".
• One-shot operation with irreversible consequences.

Cynefin Quadrants & Responses

• Clear: Sense $\rightarrow$ Categorize $\rightarrow$ Respond (Best Practice)
• Complicated: Sense $\rightarrow$ Analyze $\rightarrow$ Respond (Good Practice)
• Complex: Probe $\rightarrow$ Sense $\rightarrow$ Respond (Emergent Practice)
• Chaotic: Act $\rightarrow$ Sense $\rightarrow$ Respond (Novel Practice)