Yes, then you must have a rough estimate for that. Or in the other extreme example - in the case of an outage, estimates must be much more precise (i.e. "we should have a workaround in ~30 minutes").

But neither case requires too much thought or discussion. My point was more that estimation ends up overwhelming time and energy, when you can just do the thing instead. I've worked on teams where we've spent more time arguing about how complex a task than it would've been for someone to crank out a solution.

I also don't mean engineers shouldn't collaborate, just that it should be more ad-hoc and not manager/tpm/scrum-master driven.