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
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
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.Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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.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
HighMediumLowLow
Timedifferent
1-4 h1-3 h1-2 h1-2 h
Participantsdifferent
3-83-123-103-8
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Challenge Findings, Risk Register, Mitigation PlanKnowledge Map, Critical Knowledge Areas, Transfer PlanArchitecture Canvas, Goals, Constraints, Quality AttributesInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
RiskDecisionSensemaking
KnowledgeMappingRisk
CanvasArchitectureAlignmentWorkshop
AlignmentArchitectureCanvas
Add more methods