Problem solving Study Guide

📖 Core Concepts Problem Solving – Goal‑directed process that overcomes obstacles. Simple vs. Complex – SPS: one obstacle; CPS: multiple, interrelated obstacles. Well‑Defined vs. Ill‑Defined – Clear end‑state & solution vs. vague goal that must be defined first. Formal vs. Socio‑Emotional – Fact‑based logical reasoning vs. solutions that depend on emotions or social dynamics. Transfer – Applying a solution method learned in one context to a new problem. Barriers – Confirmation bias, mental set, functional fixedness, unnecessary constraints, irrelevant information. Representation – Visual, verbal, or mathematical reformulation that can bypass mental biases. Collective Intelligence – Group‑level problem‑solving that exceeds any single member’s capacity. --- 📌 Must Remember Stages (Psychology): Problem finding → shaping → generating solutions → evaluating → implementing/verification. Root‑Cause Analysis (TapRooT): Data → causal‑factor diagram → “Why” ladder → corrective actions → verification. Common Methods – PDCA, OODA, A3, Design Thinking, TRIZ, Scientific Method. Key Barriers – Unnecessary constraints (self‑imposed limits) and irrelevant information (distracting data). Wicked vs. Grey – Wicked: no definitive solution, changing requirements; Grey: ambiguous but somewhat bounded. Insight vs. Analysis – Insight = sudden “aha!”; analysis = systematic, step‑by‑step. --- 🔄 Key Processes Psychological Problem‑Solving Cycle Problem finding/shaping – Identify and simplify the issue. Generate alternatives – Brainstorm possible solutions. Evaluate – Compare alternatives against criteria. Implement – Apply the chosen solution. Verify – Check that the goal is achieved. TapRooT Root‑Cause Investigation Collect unbiased data. Build cause‑and‑effect (fishbone) diagram. Ask “Why?” repeatedly to trace back to root causes. Classify causes (root, contributing, immediate). Develop corrective actions (feasible, measurable, sustainable). Document and verify effectiveness. OODA Loop (Observe → Orient → Decide → Act) – Rapid decision‑making cycle for dynamic environments. PDCA Cycle (Plan → Do → Check → Act) – Continuous improvement; plan a change, execute, evaluate, then standardize or adjust. Decomposition – Break a complex problem into sub‑problems; label subgoals; solve each independently before integrating. --- 🔍 Key Comparisons Well‑Defined vs. Ill‑Defined – • Goal is explicit vs. goal must be created. • Solution path is known vs. requires problem framing. Formal vs. Socio‑Emotional – • Logical, fact‑based reasoning vs. affect‑driven, relational tactics. Insight vs. Step‑by‑Step – • Sudden restructuring of the problem vs. incremental, algorithmic progress. TapRooT vs. General Troubleshooting – • Structured “why‑ladder” & documentation vs. ad‑hoc symptom fixing. Wicked vs. Grey Problems – • No final answer, evolving criteria vs. partially defined, still tractable. --- ⚠️ Common Misunderstandings “Constraints are always real.” Unnecessary constraints are self‑imposed and should be questioned. Confusing abduction with deduction. Abduction generates hypotheses (how?), deduction tests them (why?). Assuming a problem is well‑defined because it appears simple. Often hidden goal ambiguity exists. Treating “insight” as a magic shortcut. Insight often follows deep representation change, not random luck. Believing collective intelligence guarantees a better solution. Groupthink or coordination loss can degrade outcomes. --- 🧠 Mental Models / Intuition “Problem as a Map” – Visualize start, obstacles, and goal; chart routes (subgoals) before moving. “Constraint Filter” – Ask: Is this constraint a physical law or an assumption? If the latter, try discarding it. “Why Ladder” – Each “why” moves you one level up the causal hierarchy (symptom → cause → root). “Chunk‑and‑Label” – Group related steps into a labeled chunk (subgoal) to reduce working‑memory load. --- 🚩 Exceptions & Edge Cases Transfer Failure – Knowledge may not transfer when underlying principles differ; verify analogies. Wicked Problems – No single “correct” solution; focus on satisficing and iterative refinement. Grey Problems – Ambiguity can be reduced by explicit goal‑definition workshops. High‑Pressure OODA – In very stable contexts, a slower PDCA may yield higher quality than rapid OODA. --- 📍 When to Use Which Use PDCA when the problem is well‑defined and you need continuous improvement (e.g., manufacturing defects). Use OODA for dynamic, time‑critical situations (military planning, real‑time crisis). Apply TapRooT for systemic failures where root‑cause documentation is required (safety incidents). Choose Insight techniques (lateral thinking, TRIZ) when you hit a mental set or functional fixedness. Select Collective‑Intelligence tools (crowdsourcing, communities of practice) for large‑scale, ill‑defined challenges. --- 👀 Patterns to Recognize Repeated “why?” questions → deep root‑cause analysis. Sudden blockage after a single assumption → possible unnecessary constraint. Large amount of irrelevant data → likely a distraction; filter early. Multiple interdependent sub‑problems → decomposition & subgoal labeling needed. Shift from “what is wrong?” to “what could be done differently?” → move from troubleshooting to design thinking. --- 🗂️ Exam Traps Distractor: “All problems can be solved with the OODA loop.” – OODA is for fast, uncertain environments, not every problem. Distractor: “Functional fixedness is always a barrier.” – Sometimes using the familiar tool is optimal; only a barrier when it blocks alternatives. Distractor: “Wicked problems have a correct answer.” – By definition they are open‑ended; exam will look for “iterative, satisficing” approach. Distractor: “Root cause analysis ignores contributing factors.” – Proper analysis distinguishes but documents both root and contributing causes. Distractor: “Insight can replace systematic analysis.” – Insight complements, not replaces, systematic verification. ---