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 the Lotus Blossom working structure.
Innovation
Lotus Blossom
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.When a central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem.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 min45-90 min1-2 h1-2 h
Participantsdifferent
1-103-103-103-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
HMW Questions, Challenge Framing, Idea PromptsLotus Diagram, Idea Themes, ShortlistArchitecture Canvas, Goals, Constraints, Quality AttributesInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
FramingOpportunityIdeationQuestions
BrainstormingIdeationCreativityDivergenceWorkshop
CanvasArchitectureAlignmentWorkshop
AlignmentArchitectureCanvas
Add more methods