View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Team Charter | ![]() Architecture Software Architecture Canvas | ![]() Innovation Design Charrette | ![]() Innovation Lotus Blossom |
|---|---|---|---|---|
Purposedifferent | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 2-4 h | 1-2 h | Halber Tag bis mehrere Tage | 45-90 min |
Participantsdifferent | 3-12 | 3-10 | 10-50 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | Architecture Canvas, Goals, Constraints, Quality Attributes | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | TeamAlignmentCollaboration | CanvasArchitectureAlignmentWorkshop | BrainstormingWorkshopCollaborationIdeation | BrainstormingIdeationCreativityDivergenceWorkshop |



