Wideband Delphi
Structured consensus-based estimation technique where experts independently provide estimates, then iteratively refine them through facilitated discussion until convergence. Developed in the 1970s, this method reduces individual bias while leveraging collective expertise.
Last updated: 2026-03-20 15:16
Overview
Wideband Delphi is a group-based estimation technique that combines expert judgment with structured iteration to produce accurate project estimates. Unlike traditional Delphi methods where experts never meet, Wideband Delphi includes group discussion to accelerate consensus.
Process
- Kickoff Meeting: Coordinator presents estimation task and background information to the expert group
- Individual Preparation: Experts review requirements and prepare questions independently
- Estimation Meeting: Group discusses assumptions and clarifies requirements
- Anonymous Estimation: Each expert submits estimates independently without knowing others' estimates
- Compile Results: Coordinator aggregates estimates and identifies outliers
- Discussion: Group reviews results, with outliers explaining their reasoning
- Re-estimate: Experts submit new estimates based on discussion
- Iterate: Repeat steps 5-7 until estimates converge (typically 2-4 rounds)
- Final Estimate: Group agrees on final estimate, often using median or consensus value
Key Principles
- Anonymity: Initial estimates are anonymous to prevent groupthink
- Iteration: Multiple rounds allow experts to reconsider based on group input
- Controlled Feedback: Structured discussion prevents dominant personalities from biasing results
- Expert Selection: Participants should have relevant experience and diverse perspectives
Advantages
- Reduces individual bias and anchoring effects
- Leverages collective expertise
- More accurate than single expert estimates
- Identifies hidden assumptions and risks
- Creates shared understanding among stakeholders
- Works well for complex or novel projects
- Documented rationale for estimates
Disadvantages
- Time-consuming (requires multiple meetings)
- Requires multiple qualified experts
- Can be difficult to facilitate
- May not converge if experts have very different perspectives
- More overhead than simpler estimation methods
When to Use
Ideal for large, complex, or high-risk projects where estimation accuracy is critical. Particularly valuable when:
- Project is unprecedented or innovative
- High uncertainty exists
- Multiple technical disciplines are involved
- Stakeholders need high confidence in estimates
- Time investment in estimation is justified
Modern Adaptations
Many teams use simplified versions:
- Fewer rounds (2 instead of 4+)
- Real-time discussion instead of written feedback
- Digital tools for remote estimation
- Combination with Planning Poker for Agile teams
Best Practices
- Select 4-7 experts with diverse relevant experience
- Provide detailed requirements before first meeting
- Use skilled facilitator to manage discussion
- Set time limits for each round
- Document assumptions and risks identified
- Don't force consensus—acknowledge uncertainty if appropriate
- Track actual results vs. estimates to improve future sessions
Related Items
1-3-5 Technique
A daily time management method that structures your to-do list into 1 big task, 3 medium tasks, and 5 small tasks. It provides a simple, focused framework for prioritizing daily work and managing workload capacity.
10 Minute Task
A time management technique where every task on your to-do list should be broken down so that it takes no longer than 10 minutes to complete. If a task would take longer, it must be subdivided into smaller, more manageable pieces. This approach prevents procrastination by making every task feel achievable.
10 Minutes Technique
A task-start strategy where you commit to just 10 minutes of effort on a selected task, after which you can stop if you want. The psychological trick is that once you begin, you usually won't want to quit, overcoming initial resistance and procrastination.
112/26 Rule
An extended productivity technique similar to the 52/17 rule, where you work for 112 minutes followed by a 26-minute break. This longer interval is suggested for tasks requiring sustained deep focus and complex problem-solving.