I often ask myself why some teams seem to produce better results while having more fun on the way. The other day, while listening to a wise Sadhu in “Enlightened Up!” I had an epiphany: “It’s not how you do it, it’s why you do it!” That’s the whole secret. Let me explain.
Imagine you are in the process of developing a new system. You are following all the good advice from usability gurus like Don Norman or Alan Cooper. Things are flowing nicely: The personas are defined, you already went through a series of usability tests using early mockups and the visual designers just started translating your brand message into an amazing, visual language. But the new system is still lacking something to make it special. Why? How can this be? You are following all the available “how” by the book. Maybe an user experience expert could help?
It’s time to ask yourself “why” you are developing this system. Is it just a job which needs to be done? Would you prefer to actually be working on something else? Do you really care about the users?
Why do you think the espresso in a quiet, little bar in Tuscany smells better than in any Starbucks around the world? Even with the same coffeemaker, the same beans, the same barista training, the coffee still would turn out differently. The “how” might be the same, but the “why” is not. The attitude, the intention of the barista matters. One just wants to make a living to be able to pay for something he really would like to do – which is perfectly ok – the other is content with his live in a small village, exited to prepare an expresso for anyone who happens to step into his bar.
Wan’t something better? Ask everyone “why” they are working on the project. Try to find a reason “why” YOU are working on the project. Try to look in your heart, not the project vision statement. And don’t forget: Everyone has his own reasons “why” he is passionate about something. Don’t try to force your values on anyone else!
Don’t get me wrong: The “how” will get you 80% of the way. But you will need the “why” to get to 100%. Getting to understand the “how” is complicated enough. Trying to answer the “why” is indeed much, much harder.