View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Software Architecture Canvas |  Product Discovery Context Canvas |  Innovation Brainstorming |  Innovation Design Charrette |
|---|---|---|---|---|
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 an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | When a team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. | In a tightly timed design process with many participants, the method pools several lines of thinking in a short time. It brings parallel design energy without letting the discussion tip into endless coordination. This quickly produces solid directions for architecture or space. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 1-2 h | 45-90 min | 30-60 min | Halber Tag bis mehrere Tage |
Participantsdifferent | 3-10 | 3-10 | 4-12 | 10-50 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Architecture Canvas, Goals, Constraints, Quality Attributes | Context canvas, Open questions, Shared context notes | Idea pool, Theme clusters, Shortlist | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction |
Tagsno overlap | CanvasArchitectureAlignmentWorkshop | ContextFramingRequirementsCanvas | BrainstormingIdeationCreativityWorkshopDivergence | BrainstormingWorkshopCollaborationIdeation |