Book Notes Extract by Daisy, mostly user experience area.( keep updating)

「 Thoughts on interaction design 」

Section Four: Getting Design Done. — A contributed essay, by Ellen Beldner.

Don’t make your prototypes look too fancy or polished, or you’ll never get really challenging feedback. Your clients, team, and users will hesitate to rip apart something that is too finished.


  • The ability to keep in mind the core vision(create a great-looking car; code a useful mobile app) while also mitigating worst-case scenarios( car hits a tree; mobile device joins an insecure network) is something designers and developers alike need to learn — particularly when it comes to human failures. It’s the ability to simultaneously work toward and challenge your vision — to ask yourself not only, How can I make this even better? but also, How can I keep this from inflicting plain?
  • When we ask users to share information, we’re asking for their trust. But it’s hard to trust a site when you’re not sure about the intentions of the people behind it. Why do they need your data? How will they use it? What will happen once you provide it?
  • We can’t know precisely which information is sensitive for any given user. What we can do is be honest about our informations. We can ask users only for what we truly need, and be clear about what we’ll do with what they give us. And we can provide context, explaining why we want information and disclosing when and how a use’s actions affect what happens next.
  • The point of compassion isn’t to soften bad news or stressful situations with niceties. It’s to come from a place of kindness and understanding, rather than a place of judgement. It’s to tell the truth in such a way that you’re allowing others to tell their truths, too.