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
How Might We
Innovation
How Might We
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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
With a stuck problem carrying many implicit assumptions, the method translates observations into open, workable questions. It sharpens the problem frame without pre-thinking the solution, turning frustration or fuzziness into a search space with clear direction.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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.
Complexitysame
LowLowLowLow
Timedifferent
30–45 min30 min Setup, dann laufend1-2 h1-2 h
Participantsdifferent
1-101-3 maintaining, briefing for everyone3-103-8
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
HMW Questions, Challenge Framing, Idea PromptsRAID Log, Status Report SourceArchitecture Canvas, Goals, Constraints, Quality AttributesInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
FramingOpportunityIdeationQuestions
RiskTrackingStakeholdersGovernance
CanvasArchitectureAlignmentWorkshop
AlignmentArchitectureCanvas
Add more methods