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 Futures Wheel with its method-specific working model.
Systems Thinking
Futures Wheel
Visual Management workspace showing the question, observations, and next decision.
Operations
Visual Management
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Purposedifferent
The Futures Wheel helps explore the consequences of a decision, a trend, or a strategic move in a structured way. It makes visible which first, second, and third-order effects could arise from an event.With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work.When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.
Complexitydifferent
MediumLowLowMedium
Timedifferent
60-120 minOngoingUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter1-3 h
Participantsdifferent
3-101-20Scrum Team3-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Futures Wheel, Consequence Chains, Strategic SignalsVisual Board, Status Indicators, Exception CuesImprovement actions, Team agreementsProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
ForesightSystems thinkingSignals
SignalsOperationsVisual management
RetrospectiveImprovementLearning
ProcessOperationsImprovement
Add more methods