+ All Categories
Home > Design > Before the docs: writing for user interfaces

Before the docs: writing for user interfaces

Date post: 10-Jan-2017
Category:
Upload: beth-aitman
View: 11,911 times
Download: 0 times
Share this document with a friend
85
Before the docs Writing for user interfaces Beth Aitman @baitman
Transcript
Page 1: Before the docs: writing for user interfaces

Before the docsWriting for user interfaces

Beth Aitman@baitman

Page 2: Before the docs: writing for user interfaces
Page 3: Before the docs: writing for user interfaces

Why does UI text matter?Introduction - Microcopy - Help - Errors

Page 4: Before the docs: writing for user interfaces

Why does UI text matter?

The UI comes first.

Introduction - Microcopy - Help - Errors

Page 5: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 6: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 7: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 8: Before the docs: writing for user interfaces

It’s not one or the otherIntroduction - Microcopy - Help - Errors

Page 9: Before the docs: writing for user interfaces

It’s not one or the other

Docs and UI support each other.

Introduction - Microcopy - Help - Errors

Page 10: Before the docs: writing for user interfaces

Three main areas

1. Microcopy2. Embedded help3. Error messages

Introduction - Microcopy - Help - Errors

Page 11: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 12: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 13: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 14: Before the docs: writing for user interfaces

First, microcopyIntroduction - Microcopy - Help - Errors

Page 15: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 16: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 17: Before the docs: writing for user interfaces

Text makes UIs meaningful

from https://signalvnoise.com/posts/3404-reminder-design-is-still-about-words

Introduction - Microcopy - Help - Errors

Page 18: Before the docs: writing for user interfaces

Text makes UIs meaningful

from https://signalvnoise.com/posts/3404-reminder-design-is-still-about-words

Introduction - Microcopy - Help - Errors

Page 19: Before the docs: writing for user interfaces

Microcopy is difficult

“Naming things is hard!”

Introduction - Microcopy - Help - Errors

Page 20: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 21: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 22: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 23: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 24: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 25: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 26: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 27: Before the docs: writing for user interfaces

Three strategies for microcopy

1. Think from the user perspective2. Choose names they can understand3. Experiment with phrasing

Introduction - Microcopy - Help - Errors

Page 28: Before the docs: writing for user interfaces

1. Think from the user perspective

Explain what a feature does, not how it works

Introduction - Microcopy - Help - Errors

Page 29: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 30: Before the docs: writing for user interfaces

For buttons, think actionsIntroduction - Microcopy - Help - Errors

Page 31: Before the docs: writing for user interfaces

Not this!

For buttons, think actionsIntroduction - Microcopy - Help - Errors

Page 32: Before the docs: writing for user interfaces

2. What’s it normally called?What do users call it?What will they understand?

Introduction - Microcopy - Help - Errors

Page 33: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 34: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 35: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 36: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 37: Before the docs: writing for user interfaces

3. Experiment with phrasing

Introduction - Microcopy - Help - Errors

Page 38: Before the docs: writing for user interfaces

3. Experiment with phrasing

Try explaining it in a sentence.

Introduction - Microcopy - Help - Errors

Page 39: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 40: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 41: Before the docs: writing for user interfaces

… and embedded help is there if you need it.

Introduction - Microcopy - Help - Errors

Page 42: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 43: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 44: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 45: Before the docs: writing for user interfaces

Embedded helpIntroduction - Microcopy - Help - Errors

Page 46: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 47: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 48: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 49: Before the docs: writing for user interfaces

Embedded help

- What do you include?- When do you use docs?- Where do you put help?- Styles

Introduction - Microcopy - Help - Errors

Page 50: Before the docs: writing for user interfaces

What goes in embedded help?

“What does your user need to know to complete their task?”

Introduction - Microcopy - Help - Errors

Page 51: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 52: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 53: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 54: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 55: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 56: Before the docs: writing for user interfaces

Don’t overload peopleIntroduction - Microcopy - Help - Errors

Page 57: Before the docs: writing for user interfaces

Embedded help vs docs

- If it’s necessary information:probably keep it in the UI

- If it’s huge:summarise, then link to a doc

Introduction - Microcopy - Help - Errors

Page 58: Before the docs: writing for user interfaces

Show it in the relevant placeIntroduction - Microcopy - Help - Errors

Page 59: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 60: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 61: Before the docs: writing for user interfaces

Embedded help styles

There are tons.

Introduction - Microcopy - Help - Errors

Page 62: Before the docs: writing for user interfaces

Embedded help styles

There are tons. But I like:- inline help

Introduction - Microcopy - Help - Errors

Page 63: Before the docs: writing for user interfaces

Embedded help styles

There are tons. But I like:- expandable questions

Introduction - Microcopy - Help - Errors

Page 64: Before the docs: writing for user interfaces

Embedded help styles

There are tons. But I like:- hover text

Introduction - Microcopy - Help - Errors

Page 65: Before the docs: writing for user interfaces

Embedded help styles

There are tons.So experiment!

Introduction - Microcopy - Help - Errors

Page 66: Before the docs: writing for user interfaces

In summary

- find out what user needs to complete task

- don’t overload with information- show help in a relevant place and time

Introduction - Microcopy - Help - Errors

Page 67: Before the docs: writing for user interfaces

Error messagesIntroduction - Microcopy - Help - Errors

Page 68: Before the docs: writing for user interfaces

Error messages are easy!

I’ve got a formula.

Introduction - Microcopy - Help - Errors

Page 69: Before the docs: writing for user interfaces

- what went wrong- consequences- how to fix it

Introduction - Microcopy - Help - Errors

Page 70: Before the docs: writing for user interfaces

- what went wrong- consequences- how to fix it

Introduction - Microcopy - Help - Errors

Page 71: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 72: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 73: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 74: Before the docs: writing for user interfaces

- what went wrong- consequences- how to fix it

Introduction - Microcopy - Help - Errors

Page 75: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 76: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 77: Before the docs: writing for user interfaces

- what went wrong- consequences- how to fix it

Introduction - Microcopy - Help - Errors

Page 78: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 79: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 80: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 81: Before the docs: writing for user interfaces

Introduction - Microcopy - Help - Errors

Page 82: Before the docs: writing for user interfaces

- what went wrong- consequences- how to fix it

(and leave it out if it doesn’t apply)

Introduction - Microcopy - Help - Errors

Page 83: Before the docs: writing for user interfaces

In summary...

- Experiment with naming to get your microcopy right.

- Support users with embedded help in the UI, but be ready to link to docs.

- Use the formula for error messages!

Introduction - Microcopy - Help - Errors

Page 84: Before the docs: writing for user interfaces

One last thing!

uiwriting.tumblr.com@baitman

Page 85: Before the docs: writing for user interfaces

Thanks for listening :)If you have questions/opinions, talk to me after, or get in touch!

uiwriting.tumblr.com@baitman


Recommended