Designing from the Inside-Out: Behaviour as the Engine of Product Design


Published on

Talk given at UX London, June 2009.

Published in: Technology, Business, Design
1 Comment
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Designing from the Inside-Out: Behaviour as the Engine of Product Design

  1. Imagine I asked you to design a product. Maybe a website. For sharing medical information.
  2. The product is for the blind. And the deaf.
  3. Could you do it? Where would you start?
  4. Designing from the Inside-Out: Behaviour as the Engine of Product Design Dan Saffer, Kicker Studio
  5. Users experience products from the outside-in, namely from the interface and the physical form. In other words, as far as users are concerned, the interface is the product.
  6. But. The best products are usually not those that are designed with only the outside in mind.
  7. Those delight briefly. But prolonged use turns delight to anger and disgust. They are quickly discarded, replaced, and forgotten. They are the junk food of products.
  8. It is easier to focus on form than behaviour.
  9. Likewise, it is equally easy to focus on the mechanics: the technology that makes the product possible.
  10. Easier not because the work is easier (it isn’t). But it is easier to talk or demonstrate or even think about how a product looks or will be built than it is to design how it will work.
  11. This isn’t to say we should ignore aesthetics or technology, because that would be foolish.
  12. The best products are designed from the inside-out. Meaning, everything flows from behaviour.
  13. Behaviour How the product acts (feedback) The tasks the product allows users to do Maximising the abilities of the product A focus on actions it (you) want to engender through use
  14. An honest job of design should flow from the inside out, not from the outside in. Henry Dreyfuss, 1955
  15. We mold clay into a pot, but it is the emptiness inside that makes the vessel useful. Tao Te Ching
  16. The best products are aesthetically-pleasing are plug and play have personal or professional value seem transparent offer clear affordances/instruction put functionality on the correct platform have responsive feedback use conventions... ...or something radically better make it difficult to make mistakes are aware of context of use have moments of delight respect time and effort
  17. The best way to achieve most of those characteristics is by focusing on behaviour as the starting point.
  18. But then we’ve got this problem. If The Interface is The Product, how do we design from the inside out?
  19. A lot of products have been made from the inside out that you’d never want to own or use.
  20. Step 1: Behaviour as Design Strategy
  21. Avoid what Nicholas Nova calls the utilitarian fallacy: “a tendency to think that people want/must have products to optimize their lives.”
  22. Behaviour can be a major product differentiator.
  23. Differentiators have traditionally been features. But we can make behaviour the differentiator. In not only how the product behaves, but the behaviour it engenders.
  24. Behaviour is one defense against feature-itis.
  25. People love features. We enjoy comparing products side-by-side and choosing the one with the most features.
  26. Obligatory Don Norman Quote [P]eople are not willing to pay for a system that looks simpler because it looks less capable…[Make] the actual complexity low, the real simplicity high. That’s an exciting design challenge: make it look powerful while also making it easy to use. Don Norman
  27. Companies love features, too. It gives them something to easily market and talk about. It also allows them to simply replicate what their competitors are doing without having to come up with real differentiators.
  28. It’s easy to replicate features. But is is hard to copy how features behave if care is taken to design them well.
  29. Step 2: Behaviour as Design Research
  30. Stop looking for people’s goals and preferences, start looking for what they do and why they do it.
  31. Motivations Expectations Actions
  32. Translating goals or (worse) preferences into a design will probably lead to something terrible.
  33. Step 3: Behaviour as Product Structure
  34. How does the system behave when users engage with it? In other words, what is the feedback like?
  35. The same feature can feel completely different based on how it responds and how it is accessed. Transitions matter.
  36. What activities does the product need to support?
  37. Especially figure out what is the core activity. This will determine the product’s Buddha Nature.
  38. The core activity also determines the Hero Task.
  39. What behaviour do you want to encourage? Discourage?
  40. It is hard to change learned behaviour. Once people get used to do something one way, especially if they do it very regularly, it is hard to get them to change. It is often easier to change the non-human parts of the system than it is to change human behaviour.
  41. It can be helpful when concepting to consider metaphor. If this product was an action, what would it be?
  42. There is a big difference between: Design a shower and Design something to clean a person
  43. How would it work if it was magic? Alan Cooper
  44. Where does your mobile phone’s ringer “live?” Where does Twitter live? Where does a product like live?
  45. Functional cartography Should the controls be digital, physical, or both? When and where will the feature be used? What’s the feature’s priority? Does it need to be available all the time? Frequently? How much resources should be spent? Consider ergonomics. Will a physical control ruin the form? Will a screen? How tangible should the feature be? Does the feature need a visible presence (affordance)? This can also spread cross-platform too.
  46. Start from the behaviour, and then figure out what should control it: the physical form, UI elements on a screen, or even gestures in space. For users, the interface is the system, and they don’t care which discipline(s) designed it, only that it looks good and works well.
  47. This is how we overcome the interface/inside-out paradox. Behaviour drives the form and the mechanics.
  48. So am I saying form follows function? Somewhat. But don’t quote me.
  49. We’re often not making things better, we’re just making things different. Peter Saville
  50. Go make things better.
  51. Thanks. odannyboy on Twitter