View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Storytelling |  Engineering Kanban |  Architecture arc42 |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | When an insight needs to have an effect, storytelling translates dry facts into a comprehensible development. It combines context, tension, and consequence into a form that people remember and pass on more easily. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 45-120 min | Ongoing | 1-2 Tage | 1-2 h |
Participantsdifferent | 1-6 | 2-12 | 1-4 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Narrative Outline, Key Message, Story Arc | Kanban board, WIP policies, Flow metrics | Architecture Document, Context View, Runtime View, Deployment View | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | CommunicationNarrativeStakeholdersFacilitation | FlowVisual managementDelivery | ArchitectureDocumentationCommunication | AlignmentStakeholdersStrategyFacilitation |