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 for Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
30-240 min1-4 Wochen60-120 min2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
1-61-62-8Designers, developers as users, and facilitation
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryExperiment results, Decision log, Learning summaryCommunication Canvas, Stakeholder Messages, Architecture Communication PlanPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
ExperimentsGrowthAnalyticsValidation
ArchitectureCommunicationStakeholdersCanvas
ArchitectureEngineeringFeedbackValidationTasks
Add more methods