Commonly management tasked with say, rescuing a disabled train have a plan A and they get focused on trying to make plan A work even if plan A has now introduce

Commonly management tasked with say, rescuing a disabled train have a plan A and they get focused on trying to make plan A work even if plan A has now introduced so many further obstacles that a complete re-evaluation is appropriate. Yesterday was the first day of in person exams at my employer (a large University) and we got reports that a key system wasn't working, the students were not able to take one of the exams on offer that morning as instead a "User friendly" something-went-wrong-tell-a-grown-up message appeared. We didn't know, but in fact this bug could have been fixed by (temporarily) removing a single line of code from some server software, maybe 5-10 minutes to implement, test and ship to production under emergency conditions, then an afternoon of paperwork. However our early attempts to diagnose tickled a different bug making it seem hopeless, and so effort focused on manually tweaking the configuration of every single exam computer across the entire physical estate, which took maybe half an hour or more. The bug could also have been worked around, with insight, by a single SQL query, taking maybe 10 seconds to write and execute. The software would still be broken, but those students could have taken their exam which is what mattered. But we soldiered on with plan A. And that worked, it was just much slower. If it had taken a whole day I'd like to hope we'd have re-evaluated instead.