01
Gather the Estimate Evidence
Separate confirmed scope from assumptions and unresolved questions before explaining the range.
Made for Engineers
Explain Why the Estimate Is a Range
Also useful for: people in Software Engineering
20 min
Intermediate
Software Engineering
Engineer
Communicate Better
Career outcome:
Avoid Professional Risk
Explain an engineering estimate without presenting uncertain work as a fixed promise or burying the decision in technical detail.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Make the estimate defensible by separating known work from assumptions, naming the biggest uncertainty drivers, and setting checkpoints that replace guesswork with evidence.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
02
Find What Moves the Range
Identify the few conditions that meaningfully push the estimate toward the low or high end.
03
Produce the Stakeholder Explanation
Translate the analysis into a concise explanation, talking points, and direct answers to predictable pushback.
Make Your Play
Explain Why the Estimate Is a Range
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
Describe the engineering work, intended outcome, and relevant scope boundaries.
0/10000
Enter the current range, including units such as weeks, engineer-days, or dollars.
List confirmed requirements, completed discovery, historical data, prototypes, or other evidence supporting the estimate.
0/10000
List the assumptions that must remain true for the estimate to hold.
0/10000
List unresolved technical questions, dependencies, approvals, or scope choices that could move the estimate.
0/10000
Select the confidence level that best matches the current evidence.
List the tests, reviews, decisions, or discovery points that will make the estimate more precise.
0/10000
Describe who needs the explanation and what decision the estimate will inform.
0/10000
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Gather the Estimate Evidence
Separate confirmed scope from assumptions and unresolved questions before explaining the range.
02
Find What Moves the Range
Identify the few conditions that meaningfully push the estimate toward the low or high end.
03
Produce the Stakeholder Explanation
Translate the analysis into a concise explanation, talking points, and direct answers to predictable pushback.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Start with the facts already used to produce the estimate. Write assumptions as statements that could later prove true or false. If an uncertainty driver is vague, describe the specific unknown and how it could change effort, cost, or time.
Advanced instructions
Add probability-weighted scenarios, dependency sensitivity, or historical comparison data when available. Keep the stakeholder explanation short, but preserve the evidence behind the confidence level for technical review.
Use this when
You need to explain a cost, effort, capacity, or timeline range to stakeholders who may expect a single number.
You'll need
- Work Being Estimated
- Estimate Range
- Known Scope and Evidence
- Assumptions
- Uncertainty Drivers
- Confidence Level
- Narrowing Checkpoints
- Audience and Decision
You'll get
- A range tied to clear lower-end and upper-end conditions
- Material assumptions separated from confirmed facts
- The largest uncertainty drivers ranked by impact
- A confidence level supported by evidence
- Specific checkpoints linked to a narrower estimate
- Stakeholder-ready language without unsupported guarantees
By the end of this playbook
You will have:
- A range tied to clear lower-end and upper-end conditions
- Material assumptions separated from confirmed facts
- The largest uncertainty drivers ranked by impact
- A confidence level supported by evidence
- Specific checkpoints linked to a narrower estimate
- Stakeholder-ready language without unsupported guarantees
Examples
Progress 1 of 3