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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
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)
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Purposedifferent
After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first.
Complexitydifferent
MediumLowMediumLow
Timedifferent
30-90 min30-60 min3–4 h for initial assessment; preparation and deeper analysis additional60–90 min
Participantsdifferent
3-122-81 or a small team; particularly suitable for 3–4 people2-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Postmortem Doc, Action Items, TimelinePower 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 checksStakeholder Map, Engagement Plan, Risk Notes
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
StakeholdersFacilitationAlignmentPlanning
ArchitectureQualityRiskAssessmentLean
StakeholdersAlignmentFacilitationChange
Add more methods