The Wherespresso site and app experience (UI and UX) has been hugely influenced by the guys at 37Signals. There’s no one who influences my thinking more than these guys (apart from maybe Seth Godin).
I wrote a case study on the Wherespresso Design Philosophy on one of my sites Get Implemented (GI is my small-business consulting business).
I think it makes for interesting reading – the WDP can be summarised thusly.
- Have One Big Idea – Our big idea is to help you find and share the location of the best coffee. That’s it.
- Build Less – We’re all so time poor these days that the last thing I want is to complicate things further. Keep it simple.
- Perfection for Wherespresso will be reached not when everything is added, but when there is nothing left to take away.
- Less Mass – this means simple and clean interfaces, making mistakes (but less of them) and everything else that goes with being lean and fast moving.
- Embrace Constraints – Wherespresso has real constraints; constraints on having loads of money to be spent is the big one. I use my wages to fund development so funding is a good problem as it focuses the mind on what is truly important for end users and sustainability of the site.
- Our Site and App takes sides – by building less, I remove decisions for users. Whilst this might piss some users off – “Oh why can’t I do such and such” – in reality, less decisions for users means more decisive action and a simpler user experience.
- Build what matters – my first consideration with any new feature (suggested by someone else, or even that I think of is): “does this really matter? How will it make the user experience better”.
- Feature Requests – are forgotten and met with a no, until the call for their implementation is too hard to ignore and I have to consider their worthiness.
This is a brief summary of a more in depth explanation, which you can read on GetImplemented if you’re interested.