How do you estimate effort and uncertainty, and which techniques help you reduce delivery risk?

A structured way to estimate effort and manage uncertainty is through the 3C Framework – Clarity, Calibration, and Control. It helps balance speed with confidence in delivery. Clarity ensures the team understands the “what,” Calibration refines the “how much,” and Control continuously manages the “what if.” 1. Clarity – define before you decide Begin with a requirements walkthrough to align engineering, design, and product on the “definition of done.” Break epics into small, testable stories to ...Read More

Honestly, a lot of it comes down to experience….both individual and organizational. We look at what we've built before, what our teams are capable of, and where uncertainty exists in the concept. Those data points inform the estimation process more than any formula could. There are traditional agile practices, story pointing, planning poker, velocity tracking, but past experience combined with deep collaboration gets you the most accurate estimates. Not saying you shouldn’t use those methods, th ...Read More

In AI projects, I estimate both effort and uncertainty separately to avoid surprises. Effort covers build time, while uncertainty reflects data quality, model readiness, and dependency risks. I use confidence scoring (high, medium, low) for each feature, timebox unknown areas as short experiments, and track risks like model drift or latency in a shared doc. Estimates are revisited at each milestone as new information emerges. This dual approach keeps delivery predictable while allowing flexibili ...Read More

Success in this area starts with trust and data. Trust: Reducing risk starts with trust within the product triad of product management, engineering and design. This trust enables transparent conversations about levels of effort and levels of confidence in execution. Check in regularly to refine the quality of your estimations. Data: Use internal and competitive data to inform your strategic priorities and enable more efficient trade-off discussions. Early data from product experiments can build ...Read More

In my experience, estimating effort is less about getting to a magically precise number and more about creating a shared understanding of what we’re actually building and where the uncertainty lives. At least with the teams that I’ve worked with, most bad estimates come from hidden assumptions and unclear requirements, not lack of skill. It's a PMs job is to make the unknowns visible early and reduce ambiguity before engineering starts sizing. With engineering managers, the conversation usually ...Read More