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
How Might We
Innovation
How Might We
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Rich Picture workspace showing the question, observations, and next decision.
Systems Thinking
Rich Picture
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
With a stuck problem carrying many implicit assumptions, the method translates observations into open, workable questions. It sharpens the problem frame without pre-thinking the solution, turning frustration or fuzziness into a search space with clear direction.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.A Rich Picture brings an unclear situation onto a shared drawing. It captures actors, tensions, information flows, and blind spots before the team jumps to solutions too early.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.
Complexitysame
LowLowLowLow
Timedifferent
30–45 min1-2 Tage30-90 min15-45 min
Participantsdifferent
1-101-42-101-3
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopAsync
Outputdifferent
HMW Questions, Challenge Framing, Idea PromptsArchitecture Document, Context View, Runtime View, Deployment ViewRich Picture, Problem Framing NotesADR File, Decision Log, Rationale
Tagsno overlap
FramingOpportunityIdeationQuestions
ArchitectureDocumentationCommunication
Systems thinkingSoft systemsFramingVisualization
ArchitectureRationaleDocumentationGovernance
Add more methods