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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of a Lean Canvas with nine fields, notes, and one highlighted learning risk.
Product Strategy
Lean Canvas
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Purposedifferent
Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable.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
LowMediumMedium
Timedifferent
30 min Setup, dann laufend45-90 min60-120 min
Participantsdifferent
1-3 maintaining, briefing for everyone1-62-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + async
Outputdifferent
RAID Log, Status Report SourceLean Canvas, Core Assumptions, Experiment BacklogCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
RiskTrackingStakeholdersGovernance
StartupLeanAssumptionsBusiness model
ArchitectureCommunicationStakeholdersCanvas
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record