View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Process Mapping | ![]() Innovation TRIZ | ![]() Operations Kepner-Tregoe | ![]() Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | For technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | High | High | Low |
Timedifferent | 1-3 h | 1-4 h | 2-8 h | 15-30 min |
Participantsdifferent | 3-10 | 2-8 | 2-8 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Contradiction Statement, Inventive Principles, Solution Concepts | Problem Analysis, Decision Analysis, Risk Plan | Root cause notes, Countermeasures |
Tagsno overlap | ProcessOperationsImprovement | InnovationProblem solvingContradictionsCreativity | Problem solvingRoot causeDecisionOperations | Root causeIncidentLeanProblem solving |



