The Two-Week Project Was Never Really Two Weeks

The two-week project takes six weeks, and nobody in the room did anything wrong. That distance between how long something should take and how long it actually takes is the thing I keep coming back to… I call it the intuition gap, and it costs leaders more trust than almost anything else they do. Four weeks late, you're explaining a delay instead of celebrating a win, and the next estimate you give gets believed a little less than the last one.

Three things open the gap. Capability sits under the first one: technical debt, dependencies nobody mapped, parts of the product that simply take time to learn before anyone can safely change them. Process friction is the second, and it hides better. Handoffs between teams, waiting on an approval, a calendar chopped into pieces small enough that nobody gets a real run at the work. The third is people, which is the least comfortable one to say out loud. We're optimistic by nature, we feel pressure to commit to an ambitious date in front of an audience, and the knowledge that would make the work fast usually lives in two people's heads.

The trap is treating all of this as an estimation problem, because then the only lever available is asking for tighter numbers… and tighter numbers don't move any actual work. You have to close the gap from both ends at once. On the estimate side, learn from what actually happened last time, break the work into pieces small enough to be wrong about cheaply, and push on every "this should be simple" until someone defends it. On the execution side, find the bottleneck, shorten the handoffs, protect focus time, and spread the knowledge so it stops being a single point of failure. Do both and something larger than delivery speed changes. Planning becomes something people believe again, and morale tends to follow belief. The job here was never to push harder. It was to remove the obstacles that created the gap in the first place.

0:00 The gap between expectation and reality

0:18 Introducing the intuition gap

0:25 Three main causes of project delays

1:03 How leaders can systematically close the gap

SUBSCRIBE for more insights on leadership, product, and technology

Newsletter: https://www.nathanbroslawsky.com

LinkedIn: https://www.linkedin.com/in/broslawsky

#leadership #productmanagement #engineering #management #delivery #estimation