Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions
Zak
@devzl
Ever worked on a project that blew past its deadline? (who hasn’t?) Even the best PMs can’t estimate time accurately. Why is estimating time so hard? Let’s unravel the mystery behind project timelines and why we often miss the mark 🧵
1 reply
0 recast
0 reaction
Zak
@devzl
At the start of a project, we know the least… …and yet, that’s when we’re asked: “How long will this take?” Spoiler: we’re all just guessing.
1 reply
0 recast
0 reaction
Zak
@devzl
There’s a name for this: the Cone of Uncertainty. 🟢 At the beginning, your estimates can be off by a lot (like 4x). 🟢 As you work and learn more, your estimates get better. But by then? You’re halfway to the deadline. ⏳
1 reply
0 recast
0 reaction
Zak
@devzl
This creates a fun little paradox: You’re expected to commit when you know the least… …but by the time you actually understand the work, you’re running out of time. 😅
1 reply
0 recast
0 reaction
Zak
@devzl
The result? ⛔️ Deadlines slip ⛔️ Features get cut ⛔️ People stress out Sound familiar?
1 reply
0 recast
0 reaction
Zak
@devzl
So how do you deal with this? ✅ Plan in iterations (short sprints > big launches) ✅ Use time ranges, not fixed dates ✅ Communicate early and often (very important) ✅ Expect change, and build in wiggle room
1 reply
0 recast
0 reaction
Zak
@devzl
Instead of saying “it’ll take 4 weeks,” try: “We estimate 3–5 weeks, depending on what we discover.” It sounds less confident, but it’s actually more professional. Good teams make room for uncertainty.
1 reply
0 recast
0 reaction
