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 Timeline | ![]() Delivery RAID Log | ![]() Architecture Architecture Communication Canvas | ![]() Facilitation Storytelling |
|---|---|---|---|---|
Purposedifferent | When a project, incident, or change process is only remembered in fragments, Timeline brings the sequence back into a readable form. It makes turning points, precursors, and after-effects recognizable over the course of time. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 30-90 min | 30 min Setup, dann laufend | 60-120 min | 45-120 min |
Participantsdifferent | 2-12 | 1-3 maintaining, briefing for everyone | 2-8 | 1-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Timeline, Milestones, Insight Notes | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Narrative Outline, Key Message, Story Arc |
Tagsno overlap | TimelineFacilitationSequence | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas | CommunicationNarrativeStakeholdersFacilitation |



