View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Runbook | ![]() Facilitation Consensus Workshop | ![]() Architecture Architecture Communication Canvas | ![]() Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 20-60 min | 1-3 h | 60-120 min | 1-2 Tage |
Participantsdifferent | 1-4 | 5-30 | 2-8 | 1-4 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Runbook, Checklist, Escalation Path | Consensus Clusters, Theme Titles, Priority Areas | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | OperationsReliabilityDocumentation | FacilitationConsensusWorkshopAlignment | ArchitectureCommunicationStakeholdersCanvas | ArchitectureDocumentationCommunication |



