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
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Paper illustration for Learning Review.
Operations
Learning Review
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.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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.
Complexitydifferent
MediumHighMedium
Timedifferent
1-3 hHalber Tag1-3 h
Participantsdifferent
2-85-203-10
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Five Forces Analysis, Competitive Risks, Strategic OptionsSimulation Notes, Gaps List, Updated RunbooksLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
StrategyCompetitionMarket
ResilienceOperationsIncident
LearningRetrospectiveIncidentOperations
Add more methods

Often compared together

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

A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
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