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
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Paper illustration for Intervention Mapping.
Systems Thinking
Intervention Mapping
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Purposedifferent
For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain.When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
Ongoing1-5 Tage1-3 h1-3 h
Participantsdifferent
2-204-122-83-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Chat Transcript, Action Log, AutomationsLogic Model, Change Objectives, Intervention Components, Evaluation PlanContext Map, Integration Patterns, Boundary NotesContext Canvas, Glossary, Integration Notes
Tagsno overlap
CollaborationEngineeringIncident
ChangeSystems thinkingCapability
Domain-Driven DesignBoundariesStrategy
Domain-Driven DesignBoundariesModeling
Add more methods