

Loved the replies. Once it’s over (that’s the hard part), everyone has a funny story to tell!
Mine was a race condition in an outsourced core system that showed up about six months after release, only when enough transactions hit at the same moment. The contact centre was on fire, with people calling non-stop.
Same lesson as yours: when something fails only sometimes, stop staring at the code and look at what else is running at that moment.


Not surprising, but there’s a useful lesson in why it works.
A ban takes away the decision, and the daily willpower fight against old habits. Same thing I’ve seen in change projects: if the new way depends on people choosing it again and again, it fades.
Make it the default and it sticks.