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 radar with five axes, two current and target profiles, and evidence cards beside each dimension.
Decision Making
Radar
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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 capabilities, maturity levels, or market positions need to be compared across several dimensions, overview is easily lost. Radar brings different characteristics into a shared picture and shows patterns faster than tables do.When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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
MediumHighLowMedium
Timedifferent
1-2 h45-90 min45-90 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
2-103-102-81 or a small team; particularly suitable for 3–4 people
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Radar Map, Capability Scores, Action AreasRanked Backlog, Cost-of-Delay AssumptionsAssumption List, Critical Assumptions, Learning PlanLean 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
AssessmentPortfolioCapability
LeanEconomicsSequencePrioritization
AssumptionsRiskDecisionDiscovery
ArchitectureQualityRiskAssessmentLean
Add more methods