veyepar: Designing Information for Growth

Author(s):	Marya DeVoto
Location	Crystal Ballroom
Date	may Mon 18	Days Raw Files
Start	16:10	First Raw Start	16:09
Duration	00:30:00	Offset	0:00:46
End	16:40	Last Raw End	16:44
Chapters	00:00
Total cuts_time	31 min.

http://lanyrd.com/2015/writethedocs/sdmwyg/
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf Designing_Information_for_Growth.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

Every tech company or organization organically produces docs in some form, but as scale increases, the information design decisions you started with will almost certainly serve some information consumers better than others. Depending on who&#39;s creating information and who&#39;s using it, the approach to designing and delivering information can be dramatically different, with very different outcomes that probably won&#39;t work across an entire larger organization. Be aware of the information design decisions you&#39;re making so you can plan for growth. Design by default is not a good strategy!
This talk discusses how:
Information inherently includes design, whether or not you meant to do it. Information also requires design, no matter how simple and straightforward it may seem.
Technical information can be roughly sorted into modes such as descriptive, defensive, procedural, and tutorial. (These are different from concept-task-reference.)
Each of these modes has different design implications that address different audiences and needs.
Being aware of your design priorities can help you understand how to make your stakeholders happier as your documentation base grows with the organization.

Comment:

production notes