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
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
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.When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible.When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
60-120 min1-3 h5-20 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
3-104-103-201 or a small team; particularly suitable for 3–4 people
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Futures Wheel, Consequence Chains, Strategic SignalsCurrent-state map, Future-state map, Bottleneck listEffort Heatmap, Risk Signals, Discussion TargetsLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks
Tagsno overlap
ForesightSystems thinkingSignals
LeanFlowWasteDelivery
EstimationEffortRisk
ArchitectureQualityRiskAssessmentLean
Add more methods