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
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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 fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitydifferent
MediumMediumLowLow
Timedifferent
60-120 min3–4 h for initial assessment; preparation and deeper analysis additional30-60 min15-30 min
Participantsdifferent
2-81 or a small team; particularly suitable for 3–4 people2-82-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Communication Canvas, Stakeholder Messages, Architecture Communication PlanLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksFishbone Diagram, Cause Categories, Investigation BacklogRoot cause notes, Countermeasures
Tagsno overlap
ArchitectureCommunicationStakeholdersCanvas
ArchitectureQualityRiskAssessmentLean
Root causeQualityOperations
Root causeIncidentLeanProblem solving
Add more methods