veyepar: Documentation with Human Connection

Author(s):	Hannah Gilberg
Location	Crystal Ballroom
Date	may Tue 24	Days Raw Files
Start	16:00	First Raw Start	15:59
Duration	00:30.0:00	Offset	0:00:58
End	16:30	Last Raw End	16:59
Chapters	00:00 0:28:46
Total cuts_time	30 min.

http://lanyrd.com/2016/writethedocs/sfbztz/
raw-playlist raw-mp4-playlist encoded-files-playlist host tweet mp4 svg png

assets release.pdf Documentation_with_Human_Connection_Hannah_Gilberg.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

As technical writers, it’s easy to sacrifice human connection in the strenuous effort to present technically accurate information. Maybe you feel the human connection is marketing’s job, or if you’re in a highly technical field, maybe you think your users are smart enough to make the connections themselves. Maybe you have so much work, it’s all you can do to write something technically accurate before moving on to the next update. The result can be documentation that is airless, academic, and overly technical. In other words, not something that users would want to read! If the success of your company depends on your users actually using your documentation, you have to engage them and build understanding.
This presentation will discuss how to create documentation that engages readers and focuses them on what matters. Using the writing process developed by Peter Elbow, author of “Writing without Teachers,” I’ll show how to conduct peer reviews that elicit the reader’s subjective experience -- what Peter Elbow called “movies of the reader’s mind” -- to reveal the ambiguities that can plague our writing. We’ll look at how to use the &quot;summary and sayback&quot; and “center of gravity” techniques to help writers distill a technical passage down to its core. We’ll also look at how giving your documentation a more human voice can improve not only the reader’s experience, but your own experience as a writer as well!

Comment:

production notes