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 for Reverse Brainstorming
Innovation
Reverse Brainstorming
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
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer.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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.
Complexitysame
LowLowLowLow
Timedifferent
30-60 min1-2 h1-2 h60-90 min
Participantsdifferent
3-123-103-84-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Reverse Ideas, Risk Themes, Solution IdeasArchitecture Canvas, Goals, Constraints, Quality AttributesInception Canvas, Risks, Goal List, Open QuestionsAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
BrainstormingIdeationCreativityRisk
CanvasArchitectureAlignmentWorkshop
AlignmentArchitectureCanvas
RiskArchitectureWorkshopValidation
Add more methods