Problem solving is the systematic process of identifying, analyzing, and resolving challenges through structured frameworks and creative thinking techniques. It spans from tactical troubleshooting to strategic decision-making and applies across business, engineering, operations, and personal contexts. The key distinction: effective problem solving addresses root causes, not symptoms, using a combination of analytical rigor, creative exploration, and validated decision criteria. Whether dissecting failures through root cause analysis or forecasting scenarios for strategic planning, mastering problem solving means choosing the right tool for the challenge at handβand knowing when to pivot between analytical depth and creative breadth.
What This Cheat Sheet Covers
This topic spans 10 focused tables and 65 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
Table 1: Root Cause Analysis Techniques
| Method | Example | Description |
|---|---|---|
Problem: Server crashed. Why? Memory exceeded. Why? Memory leak. Why? Unclosed connections. Why? No connection pooling. Why? Legacy code never updated. | β’ Iterative questioning technique that asks "why?" repeatedly (typically 5 times) to drill down from symptom to underlying cause β’ simple but effective for straightforward issues. | |
Categories: People, Process, Equipment, Materials, Environment, Management β branches showing potential causes leading to "Effect: Late deliveries" | β’ Visual diagram organizing potential causes into 6 standard categories (6M: Man, Machine, Method, Material, Measurement, Mother Nature) β’ excellent for brainstorming all possibilities before narrowing focus. | |
Bar chart shows 3 defect types cause 80% of failures; focus fixes on those 3. | β’ Identifies the vital few causes (typically 20%) responsible for the majority of effects (80%) β’ prioritizes effort on high-impact issues rather than spreading resources thin. | |
IS: Affects Product A, started Tuesday. IS NOT: Doesn't affect Product B, not Monday. | β’ Structured comparison of IS vs IS NOT dimensions (What, Where, When, Extent) to isolate distinctions and pinpoint the root cause β’ highly systematic and data-driven. |