Asking for engineering estimates without proper requirements, context, or time to think is akin to ordering pizza without specifying toppings or owning an oven.
Devs cannot provide accurate estimates without essential details or questions being asked.
Using estimates as commitments, ammunition, or leverage is not a sign of good leadership but rather a form of corporate gaslighting.
To obtain real estimates, provide clear requirements, let developers break down the work, encourage honest responses, ask for ranges instead of single-point answers, and use estimates as a basis for discussion, not final commitments.