5 Whys

I came across the 5 Whys (via Jason Kottke), and was extremely pleased to find it as a technique used in Toyota. For quite sometime I have been consciously trying to ask a series of Whys during designing to arrive at either a business decision or a fact. It saves from making assumptions about hidden and underlying purposes. Any form of problem solving approach, including designing, will have to do this one way or the other. The only way I could explain it to others was through the analogy of a ladder. I get down the ladder step by step with every why and finally get down on the base of it; and you can imagine that it was not very effective. An established technique like 5 Whys does a much better job than that, and am I glad to discover it!

Discussion [Participate or Link]

  1. Finding the root of the issue at Candyjar - David Ward said:

    […] found this theory on iface thoughts used by¬† Toyota. When something goes wrong dont stop finding the problem, keep asking until you […]

Say your thought!

If you want to use HTML you can use these tags: <a>, <em>, <strong>, <abbr>, <code>, <blockquote>. Closing the tags will be appreciated as this site uses valid XHTML.



Abhijit Nadgouda
iface Consulting
+91 9819820312
My bookmarks


This is the weblog of Abhijit Nadgouda where he writes down his thoughts on software development and related topics. You are invited to subscribe to the feed to stay updated or check out more subscription options. Or you can choose to browse by one of the topics.