Quick answers
- How do you give estimates?
- Give a number or range, state assumptions and dependencies, and offer to refine.
Key takeaways
- Give a range or a single number with confidence.
- State assumptions and dependencies.
- Say when you'll refine.
- Don't overcommit.
Instead of → Say
| Instead of | Say |
|---|---|
| It'll take a while | Roughly two to three days, assuming the API is ready. I'll refine after I spike it. |
| I don't know | I need to spike it first. I'll have a better estimate by tomorrow. |
| It's easy | Core work is about a day. Integration and tests add another day. So two days total. |
| Maybe a week | Best case: three days. With the migration dependency: five days. I'll know more by EOD. |
Example dialogue
PM: How long for the integration?
You: I'd estimate two to three days. That assumes we have the API schema by Monday. If not, add a day. I can give a firmer number after I spike it tomorrow.
PM: Can we have it by Friday?
You: Yes, if the schema lands Monday. Otherwise we're looking at early next week.
Common mistakes
- Vague estimates.
- Underestimating.
- Not stating dependencies.
Frequently asked questions
- How do I give a time estimate?
- Give a number or range, state assumptions, and say when you'll refine.
- What if I'm unsure?
- 'I need to spike it first. I'll have a better estimate by [date].'
Related
Ready to practice?
Try a scenario with AI and get feedback on your communication.
Start practicing