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 CATWOE Analysis.
Systems Thinking
CATWOE Analysis
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 Cynefin Workshop.
Decision Making
Cynefin Workshop
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Purposedifferent
CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way.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 problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic.For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
45-90 min3–4 h for initial assessment; preparation and deeper analysis additional60-180 min1-4 h
Participantsdifferent
3-81 or a small team; particularly suitable for 3–4 people4-203-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
CATWOE Canvas, Root Definition, Stakeholder Perspectives, ConstraintsLean 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 checksCynefin Map, Domain-specific Actions, Sensemaking NotesChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
Systems thinkingFramingStakeholders
ArchitectureQualityRiskAssessmentLean
ComplexitySensemakingDecision
RiskDecisionSensemaking
Add more methods