In a previous post on Ethnography, I invited Aza Raskin, founder of Humanized and son of Jef Raskin, the inventor of the Macintosh and author of The Humane Interface: New Directions for Designing Interactive Systems â€” to possibly answer readerâ€™s questions about design, visual management, ethnography, genchi genbutsu, man-machine interactions, or anything related.Â Several readers responded with interesting questions for Aza.Â In todayâ€™s post, Aza Raskin responds to a readerâ€™s question about Google Search Results page and how messy it is.
Be sure to read our other interviews in our leadership series.
The Google search box is simple, clean, and intuitive. BUT, the search results, from what customers tell us is confusing and messy as hell. How do you suggest we clean up the natural search and the paid search results?Â Is there a more intuitive way of doing it?Â Thanks — A Googler
Ironically, one of the fundamental goal of interaction designers is to reduce interaction.Â When we do our jobs perfectly, few people ever notice (except when comparing your solution to other products).
In this light, I would make one suggestion: remove the pagination from the Google search results.Â At best, its somewhat annoying to click through the pages, and at worst its aggravating trying to remember which page had the result you are looking for. One of Google’s magics is the extremely fast loading times, and I understand that loading long pages takes a long time. The solution is a good implementation of an non-intrusive infinite scroll.
As a side note, playful touches make a great interface into home-run products (as long as playful doesn’t become annoying). I like the elongation of “Goooooooogle”. That’s a great playful touch. That should be kept in some form.
Other articles in the “Ask Aza Raskin” Series:
- Aza RaskinÂ discusses the â€œinfinite scrollâ€ approach to Google search results.
- Aza RaskinÂ shares his thoughts onÂ Feature BloatÂ (aka, â€œFeaturitisâ€)
- Aza RaskinÂ describes the concept ofÂ Quasimodal Design.
- Aza RaskinÂ explains the role ofÂ Poka Yoke in the User Experience