I found this post that I published elsewhere almost a year ago. I was prompted to find it because someone more famous wrote something similar last week. I thought it could do with a second airing, with a bit of editing.
My children ask 'why' a lot. I'm glad they do, and try to give a full answer - to their obvious dismay sometimes. But it got me thinking about its use as part of the design process. When you know how to do something its easy to apply the rudiments subconsciously. But nobody fails to get something important from proper consideration of the fundamentals of their discipline from time to time. This is a way to do that.
Asking 'why?' at the right time can save a lot of bother and help get things right. Why put cooking instructions on food packaging? - so people know how to cook it properly and don't get poisoned by it. It has to be readable, otherwise it's useless. In this case the answer is "so people can read it". When they can't, because the text is too small or not contrasting enough, it doesn't work. Can't read the instructions, cook it wrong, doesn't taste good, won't buy it again. Everyone loses.
I look around and wonder why this seemingly simple question isn't asked more often. Maybe it's that it gets asked at the start and gets lost somewhere during the process. The design develops and requirements are refined - hey, what were we trying to do again?
In my first week at architecture school, my tutor told me I had to explain all the decisions I made during the design process. I was flummoxed at the time, but soon learnt to make up something to suit. "Because it looks good" wasn't a legitimate answer. Apart from the fact that it didn't look good - it was my first week after all.
I hope for a time when 'why?' is thought and heard more than 'why not?'. 'Why not open an account/give us a call/make an appointment today?' How different it would be if that not was not there. It would mean you do things with good reason, instead of doing them without a good enough reason not to.