View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Pretotyping |  Systems Thinking Iceberg Model |  Operations Barrier Analysis |  Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | The Iceberg Model separates visible events from patterns, structures, and mental models. This turns a single observation into a deeper understanding of why a problem keeps recurring. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 30-60 min | 2-4 h | 2-4 h |
Participantsdifferent | 1-4 | 2-10 | 2-6 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Iceberg Worksheet, Pattern Notes, Intervention Ideas | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | ValidationDemandMVP | Systems thinkingRoot causePatterns | Root causeSafetyIncident | Root causePatternsIncidentSystemic |