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 Cynefin Workshop.
Decision Making
Cynefin Workshop
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)
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Purposedifferent
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.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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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
MediumMediumLowHigh
Timedifferent
60-180 min3–4 h for initial assessment; preparation and deeper analysis additional1-2 Tage1-4 h
Participantsdifferent
4-201 or a small team; particularly suitable for 3–4 people1-43-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Cynefin Map, Domain-specific Actions, Sensemaking NotesLean 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 checksArchitecture Document, Context View, Runtime View, Deployment ViewChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
ComplexitySensemakingDecision
ArchitectureQualityRiskAssessmentLean
ArchitectureDocumentationCommunication
RiskDecisionSensemaking
Add more methods