Interface Writing: Code for Humans

C367948a0b16e9f060f735ebe94cff39?s=47 Nicole Fenton
September 13, 2014

Interface Writing: Code for Humans

We build systems to help real people. But honestly, are we being that helpful in our interfaces? Or are we treating the copy as an afterthought and letting people fend for themselves? Instead of debating the latest design trends, let’s reflect on something that isn’t going away: the text on your website. We’ll look at how strings, labels, forms, and flows shape the user experience.

C367948a0b16e9f060f735ebe94cff39?s=128

Nicole Fenton

September 13, 2014
Tweet

Transcript

  1. 2.
  2. 3.
  3. 4.
  4. 5.
  5. 6.
  6. 8.
  7. 9.
  8. 10.

    Interface Writing •buttons •errors and alerts •forms •in-app disclosures •links

    •navigation •notifications •product tours •setting names •tooltips •transactional emails
  9. 11.
  10. 12.
  11. 13.
  12. 14.
  13. 17.

    DO  YOU  BELIEVE  IT  IS   NORMAL  TO  {BE  BORED}?

      WHAT  MAKES  YOU  {BORED} {NICOLE},  DON’T  BE  SO   DEFENSIVE Strings
  14. 18.

    —Tim Maly, “We Have Always Coded” “It is no coincidence

    that many women have compared weaving code to instructing a child. With both kids and computers, you must carefully think through what you want them to do, and then carefully phrase your commands.”
  15. 20.
  16. 21.

    Practical Tips Start with questions. Be a good tour guide.

    Turn your chair. Show you care. Write iteratively.
  17. 23.

    Questions • What is the user trying to do? •

    What might they be feeling? • How did they get here? • What happens next? • What do they need to understand? • Why does this matter to them?
  18. 25.
  19. 26.
  20. 27.

    Log in Sign up today Sign in Edit my identity

    Edit your info Settings Sign out
  21. 29.
  22. 30.
  23. 31.
  24. 32.
  25. 34.
  26. 35.
  27. 36.
  28. 37.
  29. 38.

    —Paul Ford, “10 Timeframes” “The only unit of time that

    matters is heartbeats. The time you spend is not your own.”
  30. 40.