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.
Facilitation Decision method
Dot Estimation
Dot estimation uses dots to make effort and risk visible quickly and mark topics that need substantial discussion.
Dot estimation makes individual assessments visible at once, showing where experience converges and where perceptions diverge. The following discussion clarifies differences and produces a useful relative size for planning.
Where does each person independently place an item on the same relative size lane, and which dot spread reveals different models of the work?
- Participants
- 3-20
- Time
- 20–45 minutes for 8–20 comparable items.
The practice is repeated across comparable work items.

Frame
Dotting basis
Agree item set, meaning of size, Done, and reference anchors.
Dot
Dot pattern
Each person independently places exactly one dot per item on a hidden or simultaneously revealed lane.
Read
Dispersion finding
Describe clusters, edge dots, and broad spread without averaging or immediately taking a majority.
Clarify
Clarified scope
Edge perspectives explain scope, risks, and existing components; update item or assumption.
Close
Dot estimate
Re-dot, record a supportable size, and turn residual spread into a split or spike.
Add new evidence at review and version estimates with the prior state.
A good fit when
Wenn Größe oder Aufwand nur grob geschätzt werden können, verdichtet Dot Estimation Erfahrungswissen zu einer schnellen Spanne. Die Methode bringt Vergleichbarkeit in unscharfe Einschätzungen, ohne auf Scheingenauigkeit zu setzen.
Ideal for
- Workshop triage
- Early effort review
- Risk marking
Not good for
- Capacity planning
- Contractual estimation
- Complex technical analysis
Outputs

Dot estimate
Dot distributions per item with relative location, spread, clarified assumptions, final size class, and split/spike actions.
Dot Estimation · working structure
Fictional example
Fictional values show the actual method fields.
| Item | Scope | Anchors | Dots R1 | Spread | Clarification | Dots R2 | Outcome |
|---|---|---|---|---|---|---|---|
| Save cardAdd evidence and rationale. | Build, test, security, rollout | S=validation; L=new payment method | S, M, M, M, L | Broad around M | Guest/migration out; security stays | M, M, M, M, M | M |
| Provider migrationAdd evidence and rationale. | Auth, migration, fallback, certification | L=new payment method | L, XL, XL, XL, XL | High at XL | Several outcomes | No new round | XL → split |
1. Scope
- Save card
- Build, test, security, rollout
- Provider migration
- Auth, migration, fallback, certification
2. Anchors
- Save card
- S=validation; L=new payment method
- Provider migration
- L=new payment method
3. Dots R1
- Save card
- S, M, M, M, L
- Provider migration
- L, XL, XL, XL, XL
4. Spread
- Save card
- Broad around M
- Provider migration
- High at XL
5. Clarification
- Save card
- Guest/migration out; security stays
- Provider migration
- Several outcomes
6. Dots R2
- Save card
- M, M, M, M, M
- Provider migration
- No new round
7. Outcome
- Save card
- M
- Provider migration
- XL → split
All values are fictional.
First step
Set comparable items, included work, and a relative S/M/L/XL or 1–13 lane; agree on exactly one dot per person and item.
Deep dive
Several people mark their estimate directly and visibly, so it becomes immediately apparent where experience is similar and where perception diverges strongly. The dialogue that follows clarifies the causes of the differences and delivers a usable order of magnitude for the next round of planning.
Dot Estimation is an estimation variant of Dot Voting. Instead of expressing preference or priority, participants mark effort, risk, or uncertainty. Clusters show which items are likely larger, harder, or in need of clarification. The result is not a precise estimate but a quick heatmap signal for discussion, slicing, or further analysis.
Define clearly what the dots stand for: effort, risk, or uncertainty. Limit the number of dots so real prioritization happens. Then discuss clusters and outliers instead of reading the counts mechanically as effort.
The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Dot Estimation: WorksheetSet subject, data, roles, flow, and review.markdown
dot-estimation-working-template.md
Set subject, data, roles, flow, and review.
Dot Estimation: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Practice run Time: 20–45 minutes for 8–20 comparable items.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Refined items, shared Definition of Done, relative size lane, one person-coloured dot per item, and clarification log
- Roles: Delivery team dots · product owner clarifies · facilitator reads dispersion
- Advance information: Set comparable items, included work, and a relative S/M/L/XL or 1–13 lane; agree on exactly one dot per person and item.
- Overall time needed: 20–45 minutes for 8–20 comparable items.
- Setup: Prepare a workspace with Frame · Dot · Read · Clarify · Close; separate example from live data.
Prepare for the work steps
Frame: Dotting basis
- Set comparable items, included work, and a relative S/M/L/XL or 1–13 lane; agree on exactly one dot per person and item.
- Refined items, shared Definition of Done, relative size lane, one person-coloured dot per item, and clarification log
Dot: Dot pattern
- Dotting basis
Read: Dispersion finding
- Dot pattern
Clarify: Clarified scope
- Dispersion finding
Close: Dot estimate
- Clarified scope
Dot Estimation · working structure
| Item | Scope | Anchors | Dots R1 | Spread | Clarification | Dots R2 | Outcome |
|---|---|---|---|---|---|---|---|
| Save card | |||||||
| Provider migration |
- Save card: Add evidence and rationale.
- Provider migration: Add evidence and rationale.
The blank worksheet contains prompts only.
Reference · original teaching example
Frame: Dotting basis
Expected artifact: Dotting basis
Agree item set, meaning of size, Done, and reference anchors.
Entry:
...
- Is everyone estimating the same scope on one scale?
Dot: Dot pattern
Expected artifact: Dot pattern
Each person independently places exactly one dot per item on a hidden or simultaneously revealed lane.
Entry:
...
- Were dots independent and voices equally weighted?
Read: Dispersion finding
Expected artifact: Dispersion finding
Describe clusters, edge dots, and broad spread without averaging or immediately taking a majority.
Entry:
...
- Is disagreement preserved as information?
Clarify: Clarified scope
Expected artifact: Clarified scope
Edge perspectives explain scope, risks, and existing components; update item or assumption.
Entry:
...
- Does clarification explain why work models differed?
Close: Dot estimate
Expected artifact: Dot estimate
Re-dot, record a supportable size, and turn residual spread into a split or spike.
Entry:
...
- Is outcome relative, justified, and assigned a next step?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/dot-estimation/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.

Instead of Dot Estimation, choose Planning Poker when individual items should be estimated together and assumptions discussed directly.

Instead of Dot Estimation, choose Decision Matrix when you need more than quick size dots and criteria, weighting, and justification should stay visible.

Moves ideas from silent reflection through pair exchange into the group and condenses patterns.

Sorts problems, reframes the top issue, and derives experiments that quickly turn frustration into movement.

Prioritizes topics by voting and timeboxed discussion, so many points turn into clear action items.

Moves backlog, sprint work, and team flow toward a concrete result through "prepare buckets and scale", "place reference items", and "flag large or unclear items".
Constraints and origin
Profile
- Method form
- Decision method
- Participants
- 3-20
- Time
- 5-20 min
- Maturity
- Emerging
- Origin
- Agile Community

