Stop 08 · Technical Fluency for PMsTopics · 7/11

Estimation & Trade-off Conversations

In short

"Can you build it faster?" rarely helps. "What could we cut to ship by the 15th?" usually does. Good PMs turn estimates into choices.

Understanding that engineering estimates are probabilistic, not promises, and that 'can we cut scope' is usually a more productive question than 'can we go faster'.

The purple blob balances a big scale with an hourglass on one side and boxes on the other.

Think of it like this

The delivery ETA

A food app says "30 to 40 minutes", not "32 minutes". Rain, traffic and a busy kitchen all add uncertainty. If you need it in 20 minutes, the answer isn't to shout at the rider. It's to order something closer.

Watch it happen

Turning a date into a choice

Tech lead

need it by the 15th

1/5The PM shares the fixed date and why: a college admission season starts then.

The big ideas

What you need to know

Estimates are ranges

A single number hides uncertainty. Ask for a range and what makes it wide.

Scope, time, people

Change one and the others move. Adding people late often slows things down.

Cut scope, not quality

Ship fewer features that work well rather than many half-tested ones.

Ask about unknowns

"What's the riskiest part?" often tells you what to prototype first.

Save yourself the pain

Common mistakes

Oops

Treating an estimate as a promise and blaming the team when it slips.

Do this instead

Treat it as a forecast. Re-check regularly and adjust plans together.

Oops

Asking "can you do it in half the time?"

Do this instead

Ask what could be cut or simplified to hit the date.

Your mission

Practise the trade-off talk

~20 min

Quick check

Engineering says the full feature needs 6 weeks, but the launch is in 3. What's the most productive question?

Go deeper

1Practice reframing a deadline conversation around scope trade-offs instead of pure speed.
2Learn the difference between an estimate, a target, and a commitment.
3Ask an engineer to walk you through why a specific estimate was harder than it looked.