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 of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
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)
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Purposedifferent
Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.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 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.Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
1-2 h3–4 h for initial assessment; preparation and deeper analysis additional1-4 h1-3 h
Participantsdifferent
1-81 or a small team; particularly suitable for 3–4 people3-83-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Concept Map, Relationship Labels, Knowledge GapsLean 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 checksChallenge Findings, Risk Register, Mitigation PlanKnowledge Map, Critical Knowledge Areas, Transfer Plan
Tagsno overlap
KnowledgeConceptsMappingSensemaking
ArchitectureQualityRiskAssessmentLean
RiskDecisionSensemaking
KnowledgeMappingRisk
Add more methods