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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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.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 Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Complexitydifferent
LowMediumHighLow
Timedifferent
1-2 h1-3 h1-4 h1-2 h
Participantsdifferent
3-101-83-83-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesArgument Map, Evidence Gaps, Decision RationaleChallenge Findings, Risk Register, Mitigation PlanInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
SensemakingDecisionRationale
RiskDecisionSensemaking
AlignmentArchitectureCanvas
Add more methods