View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling Concept Mapping | ![]() Agile Three Amigos | ![]() Operations A3 Problem Solving | ![]() Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-2 h | 15-30 min | 45-90 min | 30-60 min |
Participantsdifferent | 1-8 | 3 | 2-5 | 3-7 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Clarified Story, Test Examples, Open Questions | A3 Report, Action Plan, Root Cause Analysis | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | CollaborationBehavior-Driven DevelopmentQualityRefinement | LeanProblem solvingCoachingOperations | Behavior-Driven DevelopmentRequirementsExamplesRefinement |



