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
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
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)
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
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.When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.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 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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
60-120 min30-120 min3–4 h for initial assessment; preparation and deeper analysis additional45-90 min
Participantsdifferent
2-82-61 or a small team; particularly suitable for 3–4 people2-5
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Communication Canvas, Stakeholder Messages, Architecture Communication PlanObservation Notes, Improvement IdeasLean 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 checksA3 Report, Action Plan, Root Cause Analysis
Tagsno overlap
ArchitectureCommunicationStakeholdersCanvas
LeanObservationProcessOperations
ArchitectureQualityRiskAssessmentLean
LeanProblem solvingCoachingOperations
Add more methods