Time Estimates
6 exercises — give ranges, qualify uncertainty, name assumptions, and communicate revised estimates professionally.
0 / 6 completed
1 / 6
A product manager asks: "How long will the new user authentication feature take?" You have not seen the full spec. Which response is most professional?
Option C — a range estimate with a named assumption and a commitment to a better estimate after scoping.
Structure of a professional rough estimate:
Example: "1–2 weeks, assuming the OAuth integration is straightforward — I can give a firmer number after I've reviewed the spec."
Why this works:
• Provides a number the PM can use for planning (not a refusal)
• The range (1–2 weeks) communicates uncertainty better than a single number
• The assumption ("assuming OAuth is straightforward") tells the PM what to watch for
• The commitment ("firmer number after review") is professional — not a blank cheque
Common estimation hedging phrases:
• "rough estimate" — signal this is not a commitment
• "in the ballpark of" — informal; conveys approximation
• "assuming [X]" — names the key dependency
• "I'd want to caveat that with" — introduces uncertainty
• "I can give you a number, but hold it loosely" — informal, honest
• "I'll have a better number for you after [X]" — commits to a refined estimate
Avoid: single-number answers without caveats ("two weeks") — they become commitments regardless of your intent.
Structure of a professional rough estimate:
[Range] + [key assumption] + [qualifier/commitment to refine]
Example: "1–2 weeks, assuming the OAuth integration is straightforward — I can give a firmer number after I've reviewed the spec."
Why this works:
• Provides a number the PM can use for planning (not a refusal)
• The range (1–2 weeks) communicates uncertainty better than a single number
• The assumption ("assuming OAuth is straightforward") tells the PM what to watch for
• The commitment ("firmer number after review") is professional — not a blank cheque
Common estimation hedging phrases:
• "rough estimate" — signal this is not a commitment
• "in the ballpark of" — informal; conveys approximation
• "assuming [X]" — names the key dependency
• "I'd want to caveat that with" — introduces uncertainty
• "I can give you a number, but hold it loosely" — informal, honest
• "I'll have a better number for you after [X]" — commits to a refined estimate
Avoid: single-number answers without caveats ("two weeks") — they become commitments regardless of your intent.