Why your timeline is a guess dressed up as a plan

Ask most teams how they landed on a project's end date, and you'll get some version of the same answer: it felt right, the client asked for it, or someone said it out loud in a meeting and nobody corrected them. None of that is a plan. It's a guess that got promoted.

An estimate is not a promise

An estimate is a statement about uncertainty. It says "based on what we know right now, this will probably take about this long." A promise is a commitment you're accountable for. Most timelines fail because somewhere between the estimate and the client email, the uncertainty quietly disappeared and what's left looks like a promise nobody actually agreed to keep.

Where it actually goes wrong

• The first number said out loud becomes the anchor, even if it was a rough guess
• Nobody writes down the assumptions the estimate depended on, so nobody notices when they change
• Scope keeps growing quietly, while the original date stays fixed
• The person managing the work isn't the person who made the original promise

What to do instead

Write the assumptions down next to the date, not just the date. "Six weeks, assuming two rounds of feedback and no new requirements after week two" is a plan. "Six weeks" on its own is a hope. When an assumption breaks, you have grounds to revisit the date honestly, instead of quietly absorbing the difference and hoping nobody notices.

That's most of what a project manager actually does day to day: not predicting the future perfectly, but keeping the gap between the estimate and the promise small enough that nobody gets blindsided by it.