View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Design Storyboarding |  Architecture Request for Comments |  Decision Making Argument Mapping |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
Purposedifferent | When a usage scenario needs to become understandable early, it condenses situations, context, and flow into a legible sequence. It helps check concept ideas before anything gets built. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 30-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h | 1-2 h |
Participantsdifferent | 1-8 | 3-20 Reviewer | 1-8 | 1-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Storyboard, Concept Narrative, Testable Assumptions | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Argument Map, Evidence Gaps, Decision Rationale | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | VisualizationConceptsSequencePrototype | ArchitectureDecisionAsyncGovernance | SensemakingDecisionRationale | KnowledgeConceptsMappingSensemaking |