I know that estimates have a bad reputation. Most engineers hear “estimate” and immediately think of micro management, unrealistic deadlines, and that manager who asks “Is it already done?” Every few hours. I have seen teams fill their figures reflexively with 3x only to prevent the inevitable disappointment when the reality does not match the plan.
But after years of construction products, I started seeing estimates differently. Good estimate is not about checking or following every minute of your day. It is about trusting and creating transparency in your team.
Estimates as conversations, no contracts
If I give an estimate, I don’t make a promise or sign a contract. I start a conversation. Saying “This should take about two days” immediately opens important discussions. Someone can point out a dependence on the auth service that adds another day. Another teammate can ask if we include the database migration in that estimate. These conversations come hidden complexity to the surface before it becomes a problem.
The real value comes when estimates become a shared language between you and your stakeholders. Instead of being rigid deadlines where everyone fears, they become reference points for meaningful discussions about progress and priorities.
Creating visibility without supervision
I have seen teams completely transform as soon as they felt at ease with estimate. Not because they suddenly became perfect in predicting the future (no one is it), but because they created visibility in their work.
Your prime minister knows when to check in without being intrusive. Your teammates know when you might need help without having to ask. Your users have realistic expectations about when the function they have waited for, perhaps actually send. No more surprise delays that derailed every three -month planning. Not vaguely “It will be done when it is ready”, reactions that frustrate all involved.
The teams that ship
This is what I have noticed of teams that deliver consistently: they are not necessarily those who code faster or work longer hours. They are those who communicate better. They treat estimates as a tool for cooperation instead of a source of stress.
These teams understand that missing an estimate does not fail if you have been transparent about why. They know that adjusting an estimate based on new information does not allow defeat, it is professional. They have learned that honest communication about progress and blockers builds more confidence than any perfectly placed deadline could ever.
Good estimate is really about creating a culture in which everyone understands what happens, why it happens and when things can change. It is about replacing fear and uncertainty with clarity and shared concept.
What was your experience with estimate? Have you found ways to make it work for your team, or is it still a source of tension?
#Jola.dev #estimates #valuable