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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent
LowHighMediumLow
Timedifferent
1-2 TageHalf day2-4 h15-45 min
Participantsdifferent
1-43-123-121-3
Formatdifferent
Workshop + asyncWorkshopWorkshopAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewLeverage Map, Action Strategy7S Assessment, Alignment Gaps, Change ActionsADR File, Decision Log, Rationale
Tagsno overlap
ArchitectureDocumentationCommunication
Systems thinkingChangeStrategy
OrganizationStrategyAlignmentChange
ArchitectureRationaleDocumentationGovernance
Add more methods