Name: Missed Estimates
Uploaded: 2025-06-06T20:12:13+00:00
Duration: undefined
Description: In this segment, we’re challenged with a new scenario: an individual contributor consistently misses their own estimates

Missed Estimates

In this segment, we’re challenged with a new scenario: an individual contributor consistently misses their own estimates. This is our opportunity to apply the essence of management—creating positive, sustainable change in organizational performance.

- We frame the issue not just as a problem to fix, but as an opportunity to **create a delta** in this person’s effectiveness and the team’s overall reliability.

- Our goal is to **understand the root cause**—is it due to optimism bias, poor time management, lack of clarity, or systemic issues in the planning process?

- We can introduce **structured changes**: better estimation techniques, mentoring, regular retrospectives, or adjusting sprint planning to account for variability.

- We aim for improvements that are **sustainable**—equipping the individual with tools or frameworks they can continue to use independently.

- As always, our success isn’t in reacting to the problem but in **proactively shaping a better outcome** that would not have happened without our involvement.

If you want to learn more from Gilad, he shares free leadership advice daily on [LinkedIn](https://www.linkedin.com/in/giladnaor/?utm_source=taro&utm_medium=course&utm_campaign=cta) and weekly on the[ δeltas newsletter](https://posts.managementdeltas.com/?utm_source=taro&utm_medium=course&utm_campaign=cta)

In this segment, we’re challenged with a new scenario: an individual contributor consistently misses their own estimates

Being a good manager is hard enough already - It's even tougher for engineering. Learn more about this complex craft and how you can land a stellar engineering manager yourself.

Becoming a tech lead is the most common growth path for software engineers as they grow to senior and staff levels.

Taro offers advice for tech leads who want to manage their projects or teams more effectively

A tech lead is responsible for guiding multiple software engineers throughout the execution of a project. They usually have many years of software engineer experience and system design knowledge to help them navigate through complex software engineering situations. They work with multiple stakeholders to ensure that a project is delivered on time. They also set expectations for deliverables and quality of the project.