View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Dot Estimation | ![]() Delivery Value Stream Mapping | ![]() Architecture arc42 | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 5-20 min | 1-3 h | 1-2 Tage | 60-120 min |
Participantsdifferent | 3-20 | 4-10 | 1-4 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Effort Heatmap, Risk Signals, Discussion Targets | Current-state map, Future-state map, Bottleneck list | Architecture Document, Context View, Runtime View, Deployment View | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | EstimationEffortRisk | LeanFlowWasteDelivery | ArchitectureDocumentationCommunication | ArchitectureCommunicationStakeholdersCanvas |



