The resistance you get from engineers to estimates is a reflection of your culture as a leader

That resistance to estimate in my experience is actually a fear of blame and failure.

If they worry that they’ll be judged and blamed for not delivering “on time” — which means that, without any discussion or warning, the estimate became a deadline.

Everyone knows that engineers often underestimate how long things will take.

The estimation changes:

1. Because they are likely doing this for the first time and haven’t learnt the pitfalls yet

2. Because requirements change as things get clearer as the project progresses.

But what underpins all of this is trust and communication.

Trust that their estimation won’t be treated as a deadline.

Trust that they won’t be blamed for it taking longer… especially as requirements change.

And that change is not acknowledged as having an impact on the original estimation.

Communication — because they trust you, the leaders, enough to communicate as soon as they realise (without worrying about being blamed) that the estimation was inaccurate because of xyz pitfalls or change in requirements.

So… stop pointing fingers at the engineers for resisting estimation and look at your leadership skills and the culture you’re building.

You might just find that your culture is the reason they resist estimating…

What do you think?

#cto #ceo #reengineeringleadership #estimates #softwaredevelopnent