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 Spotify Model Mapping with its method-specific working model.
Team Design
Spotify Model Mapping
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Purposedifferent
When a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list.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.McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result.In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.
Complexitysame
MediumMediumMediumMedium
Timedifferent
90-180 min30-90 min2-4 h15-60 min je Zyklus
Participantsdifferent
5-153-123-121-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Spotify Model Map, Action ListPostmortem Doc, Action Items, Timeline7S Assessment, Alignment Gaps, Change ActionsSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
TeamOrganizationAlignmentDiagnosis
Site Reliability EngineeringIncidentLearningReliability
OrganizationStrategyAlignmentChange
DecisionChangeLearningStrategy
Add more methods