Why Engineers Should Always Communicate Uncertainty With Time Estimates

Software engineer Serguey Shinder argues that the gap between an engineer's intended estimate and how business stakeholders interpret it is a major source of workplace friction. When developers give a bare figure like 'two weeks,' decision-makers treat it as a firm commitment and build launch plans, client promises, and marketing efforts around it. Shinder recommends replacing single-number estimates with ranges tied to specific conditions and risk factors, so that uncertainty is explicitly communicated rather than assumed. He also stresses telling stakeholders when the uncertainty will resolve, giving them a concrete moment to expect a more reliable answer. According to Shinder, engineers who consistently convey honest uncertainty earn more lasting trust than those who either over-promise or pad estimates into vagueness.