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 for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration for PDCA Cycle.
Operations
PDCA Cycle
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Paper illustration of Team Topologies Interaction Modes with its method-specific working model.
Team Design
Team Topologies Interaction Modes
Purposedifferent
When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode.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.When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements.
Complexitydifferent
LowLowMediumMedium
Timedifferent
45-90 min1 h bis mehrere Wochen2-4 hHalf day
Participantsdifferent
3-121-83-12Team-Leads plus Architecture
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Expectation Map, Alignment Notes, AgreementsPDCA Log, Experiment Plan, Learning Outcome, Standard Change7S Assessment, Alignment Gaps, Change ActionsInteraction Heat Map, Agreements per Pair
Tagsno overlap
AlignmentStakeholdersTeam
Continuous improvementLeanExperiments
OrganizationStrategyAlignmentChange
TeamAlignmentCollaborationOrganization
Add more methods