methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus.For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.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
MediumHighMediumLow
Timedifferent
1-3 h1-4 h60-120 min1-2 Tage
Participantsdifferent
2-83-82-81-4
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Issue Map, Positions, Argument NotesChallenge Findings, Risk Register, Mitigation PlanCommunication Canvas, Stakeholder Messages, Architecture Communication PlanArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
RationaleKnowledgeDecision
RiskDecisionSensemaking
ArchitectureCommunicationStakeholdersCanvas
ArchitectureDocumentationCommunication
Add more methods