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 an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid
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 for Problem Framing Workshop.
Facilitation
Problem Framing Workshop
Purposedifferent
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.When many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy.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.When a team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other.
Complexitydifferent
LowLowMediumLow
Timedifferent
45-90 min30-60 min3–4 h for initial assessment; preparation and deeper analysis additional60-120 min
Participantsdifferent
2-82-81 or a small team; particularly suitable for 3–4 people4-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Assumption List, Critical Assumptions, Learning PlanPower Interest Grid, Strategy per StakeholderLean 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 checksProblem Statement, Scope Boundaries, Assumption List, Next Analysis Questions
Tagsno overlap
AssumptionsRiskDecisionDiscovery
StakeholdersFacilitationAlignmentPlanning
ArchitectureQualityRiskAssessmentLean
FacilitationAlignmentDiscovery
Add more methods