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 for Communication Plan
Delivery
Communication Plan
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)
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
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 people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost.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.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.
Complexitydifferent
LowLowMediumLow
Timedifferent
45-90 min45-90 min3–4 h for initial assessment; preparation and deeper analysis additional20–45 min
Participantsdifferent
2-82-61 or a small team; particularly suitable for 3–4 peopleSmall cross-functional group
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Assumption List, Critical Assumptions, Learning PlanCommunication Plan, Channel Matrix, Message CadenceLean 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 checksRisk list, Mitigation plan, Assumption log
Tagsno overlap
AssumptionsRiskDecisionDiscovery
CommunicationStakeholdersDeliveryPlanning
ArchitectureQualityRiskAssessmentLean
RiskDecisionFailurePlanning
Add more methods