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
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
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 illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
45-90 min60-120 min3–4 h for initial assessment; preparation and deeper analysis additional2-6 h
Participantsdifferent
2-52-81 or a small team; particularly suitable for 3–4 people3-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
A3 Report, Action Plan, Root Cause AnalysisCommunication 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 checksFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
LeanProblem solvingCoachingOperations
ArchitectureCommunicationStakeholdersCanvas
ArchitectureQualityRiskAssessmentLean
RiskQualityOperationsRoot cause
Add more methods