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
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of a two-by-two Ansoff Matrix with four growth directions
Business Strategy
Ansoff Matrix
Paper illustration of a six-field PESTLE grid
Business Strategy
PESTLE Analysis
Purposedifferent
GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.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.The Ansoff Matrix organizes growth options by market and product relation. It helps weigh expansion, diversification, and adaptation cleanly against each other.PESTLE Analysis makes political, economic, social, technological, legal, and environmental influences visible. The environment of an initiative is thereby read systematically instead of through isolated trends.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-3 hAs needed45-90 min1-3 h
Participantsdifferent
2-84-152-82-10
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Gap Matrix, Action Plan, Risk NotesIncident Log, Action Tracker, Stakeholder UpdatesAnsoff Matrix, Growth Options, Risk NotesPESTLE Map, External Risks, Strategic Questions
Tagsno overlap
StrategyAnalysisPlanning
IncidentOperationsReliability
GrowthStrategyMarketPortfolio
StrategyMarketAnalysis
Add more methods