I don’t know the estimate

Written by anshum4n | Published 2017/04/06
Tech Story Tags: software-development | spending | estimations | professional-development | project-management

TLDRvia the TL;DR App

You do. Whether its a delivery project, feature or sales budget, you have an estimate. It might be a really large range e.g. between $10 to $100,000 but that is okay. By definition an estimate isn’t exact.

So its important to put a stake in the ground by putting an estimate. Even if its off, it lets you retrospect, improve your intuition and do a better job next time.

Objection

Putting an initial estimate down has a cognitive bias — Anchoring. Maybe you can avoid it if you know about it! Otherwise, always give a range e.g. you can say “I believe it will take 30 to 70 hrs (or $30K to $70K) and I can give you a more accurate estimate if I know X”.

Summary

Your estimate accuracy depends on your past experience and intelligence. If someone tells me they don’t know the estimate, I question both. So always give an estimate and then work to make it better.

This post came about in a discussion with MeetNotes.co team. MeetNotes.co is a meeting notes application for teams trying to make meetings engaging. If that interests you, you can try it here.

Hacker Noon is how hackers start their afternoons. We’re a part of the @AMIfamily. We are now accepting submissions and happy to discuss advertising & sponsorship opportunities.

To learn more, read our about page, like/message us on Facebook, or simply, tweet/DM @HackerNoon.

If you enjoyed this story, we recommend reading our latest tech stories and trending tech stories. Until next time, don’t take the realities of the world for granted!


Published by HackerNoon on 2017/04/06