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 Porter’s five competitive forces
Business Strategy
Porter Five Forces
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Purposedifferent
Porter Five Forces analyzes the forces that shape competitive pressure and profitability in a market. The view of market structure goes beyond individual competitors and reveals systemic pressure points.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.
Complexitydifferent
MediumMediumHigh
Timedifferent
1-3 hAs neededHalber Tag
Participantsdifferent
2-84-155-20
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Five Forces Analysis, Competitive Risks, Strategic OptionsIncident Log, Action Tracker, Stakeholder UpdatesSimulation Notes, Gaps List, Updated Runbooks
Tagsno overlap
StrategyCompetitionMarket
IncidentOperationsReliability
ResilienceOperationsIncident
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of a two-by-two Ansoff Matrix with four growth directions
Business Strategy
Ansoff Matrix
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration of a six-field PESTLE grid
Business Strategy
PESTLE Analysis