View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Six Thinking HatsSoftware Architecture CanvasAlignment MappingArchitecture Communication Canvas
| Criterion |  Facilitation Six Thinking Hats |  Architecture Software Architecture Canvas |  Facilitation Alignment Mapping |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | When a topic gets stuck too quickly in the same thinking mode, Six Thinking Hats deliberately separates the perspectives. This means facts, risks, creativity, and emotional signals get worked through one after another instead of mixed together. | 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 45-90 min | 1-2 h | 1-2 h | 60-120 min |
Participantsdifferent | 4-12 | 3-10 | 4-12 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Perspective Notes, Decision Inputs, Action Items | Architecture Canvas, Goals, Constraints, Quality Attributes | Alignment Map, Open Issues, Decision Questions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | FacilitationOptionsDecision | CanvasArchitectureAlignmentWorkshop | AlignmentStakeholdersStrategyFacilitation | ArchitectureCommunicationStakeholdersCanvas |