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.

Selected:Risk MatrixKnowledge MappingRequest for CommentsLASR (Lightweight Approach for Software Reviews)
Criterion
Paper illustration of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
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)
Purposedifferent
When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.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.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
30-60 min1-3 h1-3 Wochen vom Draft bis zur Entscheidung3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
3-103-123-20 Reviewer1 or a small team; particularly suitable for 3–4 people
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
Risk Matrix, Top Risk ListKnowledge Map, Critical Knowledge Areas, Transfer PlanRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsLean 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 checks
Tagsno overlap
RiskDecisionPrioritizationAssessment
KnowledgeMappingRisk
ArchitectureDecisionAsyncGovernance
ArchitectureQualityRiskAssessmentLean
Add more methods