The Curious Case of the '5 Whys' Method

When I was younger, I had this rather tedious habit of asking "Why?" to just about everything. It drove my parents crazy, especially during those long summer road trips. "Why does the sun set?" "Why does that bird fly so high?" "Why can't I have ice cream for dinner?" The questions were endless. Little did I know, I was unwittingly practicing what would later become a staple in the world of user experience design - the "5 Whys" method.

Now, the "5 Whys" method is as simple as it sounds. You ask "Why?" not once, not twice, but five times in a row. It's like being a child again, but this time, it's socially acceptable, and you're getting paid for it. You see, each "Why?" peels away another layer of the user's reasoning, like peeling an onion, but without the tears. Well, usually without the tears.

It's funny to think that such a simple method was first adopted by the likes of Toyota. Yes, the car company. They used it to analyze problems with a welding robot. Imagine, for a moment, being that robot. One day you're happily welding away, and the next, you're being interrogated by a bunch of engineers asking you "Why?" five times over. It's enough to send any robot into an existential crisis.

But I digress. As a UX professional, using the "5 Whys" method is like having a secret weapon. It allows you to dig into the nitty-gritty of user behavior, uncovering insights that are as surprising as they are valuable. So, the next time you find yourself in conversation with a user, channel your inner five-year-old and ask them "Why?". And then ask it again. And again. And again. And once more for good measure.

Who knows, you might just stumble upon a revelation. Or, at the very least, annoy someone into a state of enlightenment.

‍