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
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result.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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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.
Complexitydifferent
MediumLowLowMedium
Timedifferent
2-4 h1-2 h60-90 min1-2 h
Participantsdifferent
3-123-104-124-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
7S Assessment, Alignment Gaps, Change ActionsArchitecture Canvas, Goals, Constraints, Quality AttributesAnnotated Diagram, Prioritized Risk List, Action BacklogAlignment Map, Open Issues, Decision Questions
Tagsno overlap
OrganizationStrategyAlignmentChange
CanvasArchitectureAlignmentWorkshop
RiskArchitectureWorkshopValidation
AlignmentStakeholdersStrategyFacilitation
Add more methods