Talk:Go fever

I am voting to have this stub deleted. Does anybody also agree? SimonHarvey (talk) 20:16, 26 March 2008 (UTC)

I oppose. This was directly responsible for most of the Space Shuttle Challenger disaster and I think that makes it WP:Notable, however, yes it must be greatly improved. 602p (talk) 00:57, 18 November 2014 (UTC)

Psychology

Go Fever will only ever occur on sophistocated projects, it occurs because of the assumption that everything has been engineered properly prior to the event, and when the time comes and a hiccup occurs you can only assume it has been properly designed for - because if you were to take the time to decide if it is safe, it can take days or weeks - and of course, the window is then long gone. A solution would be during the design phase, is to have the engineers ask themselves: "is it safe to go today?" everyday at the expected go time, and to come up with reasons for and against, and because they are in the blueprints, they may still be able to design for it (either in the design or to design a proceedure on what to check, and how, on the day to allow a safe cancellation decision) - budget permitting! Go fever is more common then you think, remember the phrase, "here goes nothing..."? which is said, or expressed as a hesitiation before the press of a button (or beginning an event sequence). The person hopes that everything is prepared properly - usually when there is no time for double checking (or due to uncertainties due to reliability, etc)! Charlieb000 (talk) 10:17, 14 September 2013 (UTC)