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
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 of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Purposedifferent
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.IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus.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.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional1-3 h1-4 h1-3 h
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people2-83-81-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Lean 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 checksIssue Map, Positions, Argument NotesChallenge Findings, Risk Register, Mitigation PlanArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
RationaleKnowledgeDecision
RiskDecisionSensemaking
SensemakingDecisionRationale
Add more methods