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 Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for Bucket System.
Agile
Bucket System
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Purposedifferent
Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.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 large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates.When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.
Complexitydifferent
HighMediumMediumMedium
Timedifferent
Half day1-3 h30-90 min1-3 h
Participantsdifferent
3-122-83-123-10
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Leverage Map, Action StrategyContext Map, Integration Patterns, Boundary NotesBucketed Backlog, Relative Estimates, Split CandidatesDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
Systems thinkingChangeStrategy
Domain-Driven DesignBoundariesStrategy
EstimationBacklogRelative sizing
Domain-Driven DesignContextBoundaries
Add more methods