--- title: "Estimates: The Art of Guessing Badly | 1:1 mentoring" description: "Oftentimes I hear stakeholders or PMs complaining that the engineering team repeatedly fails to complete their work on time." url: "https://www.marian.coach/blog/dont-let-yourself-be-held-hostage-by-estimates/" lang: "en" image: "https://www.marian.coach/images/blog-covers/dont-let-yourself-be-held-hostage-by-estimates.png" --- ![Estimates: The Art of Guessing Badly](https://www.marian.coach/images/blog-covers/dont-let-yourself-be-held-hostage-by-estimates.png) ## Problem Oftentimes I hear stakeholders or PMs complaining that the engineering team repeatedly [fails to complete their work on time](https://www.marian.coach/engineering-teams-productivity-audit/). They would push even harder on deadlines assuming that that would help. In reality, it only creates additional tension that helps no one. They would also try adding artificial buffers, further complicating the problem. However, estimates themselves are rarely a problem and constant delays are usually caused by things other than inaccurate estimates. Therefore, don’t let yourself be held hostage by estimates! ## Actions taken I tried to underline that estimates shouldn’t be understood as commitments, but should be interpreted more broadly to include the value of the development process and shouldn’t be exposed and discussed outside of software development. ![Marian Kamenistak in a leadership workshop, in front of a slide titled "Top 3 dangers — Why we haven't delivered the roadmap this quarter."](https://www.marian.coach/_astro/talk-01.BK9BNN9P_Z1Q1Q8u.webp) The slide I use in workshops to unpack why a roadmap slips — it’s rarely the estimate. If a team fails to deliver on time, their estimates are believed to be imprecise or inaccurate. Only using the right insights could help us establish what the problem is really about. I would typically find out that the delivery system is not functioning properly. Namely, during a sprint planning, a team would commit to several issues to be implemented, but a great number of unplanned things, from bugs to different types of blockers, would emerge that couldn’t be anticipated. The solution would be to identify possible unplanned or ad hoc issues and clearly define under which circumstances they could interrupt the implementation of the planned activities. That would include defining all of those unplanned issues; for example, what would constitute a blocker, etc. If a team deals with a few ad hoc issues monthly, things would likely go according to a plan. But, if the unplanned issues constitute up to 20 to 30 percent of the output that would cause serious problems and consequently delays. Also, PMs and tech leads should have a [clear insight into the type of work](https://www.marian.coach/blog/better-than-dora-metrics-team-productivity/) a team is completing; for example, how many features or bugs they were working on, how much support they offered or helped with customers, etc. If you have a full insight, you could adjust your expected ratio and incorporate that into the next sprint planning. This approach would help with estimates since it would provide guarantees for the output as included in the roadmap. If the team and a PM would act transparently and inform stakeholders regularly on the status of the features, the result would be understanding and support. If we would notice at any point in time that the possibility of a delay increases, we should immediately inform stakeholders about it. The worst-case scenario would be to keep the information about possible delays till the very delivery day. Another thing I encountered was a lack of communication between product and engineering. Product would usually hand over the requirements and engineering would deliver on those. That is a Waterfall-ish approach, and it hinders the productivity of engineering. Instead, product and engineering should have an opportunity to design things together, which would help engineers understand the complexity and all edge cases and thus increase the possibility that the estimates would be correct. Only after those other issues are addressed, I would look at the accuracy of estimates. We could create a matrix that reveals the variation or differentiation of estimates. If the variation is high, then the team is clearly not making estimates right. To fix that we could build the estimation checklist that identifies what should be part of estimates: code review, QA, deployment, etc. It should also include the implantation and design. ## Lessons learned - Most of the time, estimates are not the problem. The problem is, however, that engineering acts as a black box. Specifically, in the case of under-estimated work, I ask engineers to update the stakeholders promptly. - It is not the estimates that matter the most, but whether a PM has chosen the right features a team should be working on and that would benefit customers and bring us the most revenue. Therefore, instead of focusing on estimates, we should focus on prioritization. _Originally published at_ [_https://www.platohq.com_](https://www.platohq.com/resources/dont-let-yourself-be-held-hostage-by-estimates-809067689) _on September 14, 2020._ 1:1 mentoring ## Ready to move this from advice to action? 1:1 mentoring for engineering leaders. 300+ mentees since 2019. Pay-as-you-go or a 6-session pack. First intro is free. [Book a free 30-min intro →](https://www.marian.coach/mentoring/) ## Read next - [ ### 11 Red Flags It’s Time to Fire Your Consultant Too many consultants linger without results. Spot the 11 red flags that signal it’s time to fire your consultant, end dependency, and reclaim control. 13 August 2025 · By Marian Read → ](https://www.marian.coach/blog/11-signs-to-fire-your-consultant/) - [ ### 10x Your Market Value: The Tech Leader’s 8-Step Playbook Learn how to 10x your market value as a tech leader with 8 proven steps to boost your impact and become an irreplaceable asset in any company. 1 July 2025 · By Marian Read → ](https://www.marian.coach/blog/10x-your-market-value-tech-leader-8-steps/) - [ ### Learn or die: 11 steps to transform your ‘learning culture’ from buzzword to reality Without a real learning culture, your top talent will leave. This guide shows you how to build high-performing teams that thrive through continuous learning. 12 December 2024 · By Marian Read → ](https://www.marian.coach/blog/11-steps-to-transform-your-learning-culture/) ### New posts, straight to your inbox. Your emailSubscribe You're on it. Nothing hits your inbox today. First send goes out once the list is live, and you're already on it. [Connect on LinkedIn →](https://www.linkedin.com/in/mariankamenistak/)[See the free tools →](https://www.marian.coach/ai-coaching-tools/) ## Structured data ```json {"@context":"https://schema.org","@type":"ProfessionalService","name":"Marian Kamenistak | Engineering Leadership Mentoring","url":"https://www.marian.coach/blog/dont-let-yourself-be-held-hostage-by-estimates/","image":"https://www.marian.coach/images/blog-covers/dont-let-yourself-be-held-hostage-by-estimates.png","description":"Oftentimes I hear stakeholders or PMs complaining that the engineering team repeatedly fails to complete their work on time.","serviceType":["Engineering leadership mentoring","Engineering manager coaching","CTO coaching","Fractional CTO","Leadership development for software engineers"],"hasOfferCatalog":{"@type":"OfferCatalog","name":"Engineering leadership mentoring and advisory","itemListElement":[{"@type":"Offer","itemOffered":{"@type":"Service","name":"1:1 engineering leadership mentoring","description":"One-to-one mentoring for engineering leaders from Staff Engineer to CTO. 60-minute sessions, weekly or bi-weekly.","url":"https://www.marian.coach/pricing/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"Engineering manager coaching","description":"Coaching for first-time and experienced engineering managers: delegation, performance, hiring, team scaling.","url":"https://www.marian.coach/engineering-manager-mentor/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"CTO and VP Engineering mentoring","description":"Mentoring for CTOs, VPs of Engineering and Heads of Engineering running 30-200 person organisations.","url":"https://www.marian.coach/cto-mentor/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"Mentor in Residence","description":"A dedicated onsite mentor for your engineering organisation, booked by the quarter.","url":"https://www.marian.coach/mentor-in-residence/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"Fractional CTO","description":"Part-time CTO engagements for companies without a full-time technology leader.","url":"https://www.marian.coach/fractional-cto/"}}]},"telephone":"+420 736 519 879","email":"marian@marian.coach","sameAs":["https://www.linkedin.com/in/mariankamenistak/","https://www.youtube.com/@engineeringleaders","https://github.com/marian-kamenistak","https://www.engineeringleaders.io/","https://twitter.com/marian_coaches","https://www.elc-conference.io/","https://www.marianslist.com/","https://www.mentoringhub.io/"],"address":{"@type":"PostalAddress","streetAddress":"Varšavská 715/36, Vinohrady","addressLocality":"Praha 2","postalCode":"12000","addressCountry":"CZ"},"geo":{"@type":"GeoCoordinates","latitude":50.0734418,"longitude":14.4385757},"openingHoursSpecification":[{"@type":"OpeningHoursSpecification","dayOfWeek":["Monday","Tuesday","Wednesday","Thursday","Friday"],"opens":"09:00","closes":"17:00"}],"priceRange":"361–430 EUR","areaServed":[{"@type":"Place","name":"Europe"},{"@type":"Country","name":"Czechia"},{"@type":"Country","name":"Slovakia"},{"@type":"Country","name":"Poland"},{"@type":"Place","name":"North America"}]} {"@context":"https://schema.org","@type":"Person","@id":"https://www.marian.coach/#person","name":"Marian Kamenistak","url":"https://www.marian.coach/","image":"https://www.marian.coach/images/blog-covers/dont-let-yourself-be-held-hostage-by-estimates.png","jobTitle":["Engineering Leadership Mentor","Engineering Manager Coach","CTO Coach","Keynote Speaker"],"hasOccupation":{"@type":"Occupation","name":"Engineering Leadership Mentor"},"worksFor":{"@type":"Organization","name":"Engineering Leaders Community","url":"https://www.engineeringleaders.io/"},"alumniOf":[{"@type":"Organization","name":"Mews"},{"@type":"Organization","name":"Manta (acquired by IBM)"},{"@type":"Organization","name":"Databricks"}],"knowsLanguage":["English","Czech","Slovak"],"knowsAbout":["Engineering leadership","Engineering management","Scaling engineering teams","CTO mentoring","Engineering org design","VP of Engineering role","Engineering director role","CTPO role","Team lead development","Staff engineer career path","Fractional CTO engagements","AI-assisted engineering leadership","Conference keynotes on engineering leadership","Panel moderation","Podcast guest — engineering leadership"],"homeLocation":{"@type":"Place","name":"Prague, Czechia"},"sameAs":["https://www.linkedin.com/in/mariankamenistak/","https://www.youtube.com/@engineeringleaders","https://github.com/marian-kamenistak","https://www.engineeringleaders.io/","https://twitter.com/marian_coaches","https://www.elc-conference.io/","https://www.marianslist.com/","https://www.mentoringhub.io/","https://www.crunchbase.com/person/marian-kamenistak","https://www.wikidata.org/wiki/Q140488098","https://developers.mews.com/author/marian/","https://startupdisrupt.com/speakers/marian-kamenistak/","https://theorg.com/org/engineering-leaders-community/org-chart/marian-kamenistak"]} {"@context":"https://schema.org","@type":"WebPage","url":"https://www.marian.coach/blog/dont-let-yourself-be-held-hostage-by-estimates/","name":"Estimates: The Art of Guessing Badly | 1:1 mentoring","inLanguage":"en","dateModified":"2023-08-16T00:00:00.000Z"} {"@context":"https://schema.org","@type":"BlogPosting","headline":"Estimates: The Art of Guessing Badly","description":"Oftentimes I hear stakeholders or PMs complaining that the engineering team repeatedly fails to complete their work on time.","inLanguage":"en","articleSection":"compensation","datePublished":"2020-09-15T00:00:00.000Z","dateModified":"2023-08-16T00:00:00.000Z","author":{"@id":"https://www.marian.coach/#person"},"publisher":{"@type":"Organization","name":"Marian Kamenistak","url":"https://www.marian.coach/","logo":{"@type":"ImageObject","url":"https://www.marian.coach/favicon-192x192.webp","width":192,"height":192}},"image":{"@type":"ImageObject","url":"https://www.marian.coach/images/blog-covers/dont-let-yourself-be-held-hostage-by-estimates.png"},"mainEntityOfPage":{"@type":"WebPage","@id":"https://www.marian.coach/blog/dont-let-yourself-be-held-hostage-by-estimates/"},"keywords":"compensation","wordCount":730,"timeRequired":"PT3M","isAccessibleForFree":true} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://www.marian.coach/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://www.marian.coach/blog/"},{"@type":"ListItem","position":3,"name":"Estimates: The Art of Guessing Badly","item":"https://www.marian.coach/blog/dont-let-yourself-be-held-hostage-by-estimates/"}]} ```