Stop hiding your real timeline from stakeholders, it always backfires

Last month I had a client demo for a dashboard build and told them it would take 5 days when I knew it needed 8. I crammed the last 3 days of work into one all-nighter, shipped a buggy version, and the client noticed labels were wrong in the first 2 minutes. I keep seeing people do this in our project threads, trimming the estimate to look good for the kickoff call and then paying for it with way worse chaos later. The deadline gets moved anyway, but now you're exhausted and your work is trash. I learned it the hard way and now I add 20% to any number I say out loud, even if it makes the PM frown. Does anyone else pad their estimates just to survive the crunch, or am I the only one who lied to myself this bad?

1 comments

1 Comment

daniel_martin1mo ago

That post hit different because I used to be the guy who shaved days off estimates just to keep the room happy. Thought I was being slick, like the extra time was some kind of secret weapon. Then I pulled a similar move, shipped something half baked, and the client caught a typo in the first screen. That's when it clicked that the crunch isn't a badge of honor, it's just a slower way to fail. Now I give the real number plus a buffer, and honestly the awkward pause is easier than the 2 a.m. panic. The PM might frown for ten seconds, but that's better than a week of damage control with a pissed off client. Your 20% rule sounds about right, and I wish I'd learned that math years ago.