Discussion about this post

User's avatar
Nigel Ford's avatar

Don't underestimate the Y2K bug. It only wasn't a disaster because developers saw it coming years beforehand, and persuaded their bosd to get armies of programmers to comb through the code and correct it. Even then, truck loads of food were rejected as use by dates appeared to be 1900.

There was a similar unreported but rare bug that went unfixed a few years later. Some code was unaware of leap years, causing software to freeze for 24 hrs as the internal date didn't match the PC's

Expand full comment
PZE's avatar

Thanks for an interesting read. One of the crisis challenges is recognising that you need to adjust your style of leadership. Wicked Problems and Clumsy Solutions by Prof Keith Grint is an excellent article that addresses this issue. For a longer, and still excellent read, his book on Rethinking D-Day in terms of Leadership, Management and Commmand is very insightful too. All too often senior leaders have got to the top through one style of leadership that happened to work in once and they double down on it. However this can backfire if they think theirs is the only way. Someone with the humility to learn different behavioural approaches may be a better choice, even someone who steps back and let’s more junior staff lead (see Karl Weicks work on High Performing Organisations). And with that I’m off to re-read Keith’s article for the umpteenth time. 😁

Expand full comment
4 more comments...

No posts