This technique is called a 5-Why in lean manufacturing. Useful tool in digging into a root cause, and helps people think deeply about the causes of issues that are not inherently obvious.
Also, 5 is just the "suggested" number. More or less may be needed. If you reach 'Because I don't want to die alone' in 3 whys, probably no need to try for 5...
I had a boss that worked in Continuous Improvement. As a manager he was great because he was very good at coming up with the nucleus of an idea. He was terrible about implementing the idea, but had a crew that was great at implementing his vision (think George Lucas).
Left to his own devices, he had some horribly implemented ideas that really messed with our manufacturing floor. He was then moved to supervise a couple of manufacturing departments, which also resulted in disaster. He was moved to another facility shortly thereafter.
When writing crappy code you are either not thinking long term at all, or you are just "kicking the can down the road", in that you'll pay for it later when there isn't a time crunch.
For mine, participation entails a yearly health screening.
The screening measures blood pressure, BMI, nicotine usage, and cholesterol (via a blood draw).
Depending on the findings, you fall into 1 of 3 tiers, which results in a penalty on every pay check if you don't fall into the numbers.
I have an excellent example of this.
Despite having both Chrome and Firefox installed on my home desktop computer, my wife continues to use IE 11. Even with her own profile for Chrome, and using an Android phone with Chrome, she still sticks with IE for some odd reason.
Also, 5 is just the "suggested" number. More or less may be needed. If you reach 'Because I don't want to die alone' in 3 whys, probably no need to try for 5...