Re:The Engineer Who Refused to Approve the Challenger Launch
by ac26 on Friday June 21, 2024 @07:08PM
(#40754774)
Depends on the situation. If there exists little to no consequences then, sure, a "no" is just a "no".
When a "no" is a difference between your business or product succeeding versus not, then maybe the no will allow you to go farther. For example, how many "no"s did Cruise get before they had to shut down in SF? A leader taking that "no" and pivoting to remote monitoring+driving rather than committing to completely autonomous would have netted them another news article on this site -- instead, we get to read about Waymo.
But we talk about this as if there's only two versions: NASA's Challenger and absolute certainty with success. That's not the case and I am sure a lot of the failures from this "no" path has a lot less folks who are willing to do TedTalks on.
When a "no" is a difference between your business or product succeeding versus not, then maybe the no will allow you to go farther. For example, how many "no"s did Cruise get before they had to shut down in SF? A leader taking that "no" and pivoting to remote monitoring+driving rather than committing to completely autonomous would have netted them another news article on this site -- instead, we get to read about Waymo.
But we talk about this as if there's only two versions: NASA's Challenger and absolute certainty with success. That's not the case and I am sure a lot of the failures from this "no" path has a lot less folks who are willing to do TedTalks on.