Author(s):	Fraser Mitchell
Location	C2
Date	jan Tue 22	Days Raw Files
Start	14:00	First Raw Start	13:42
Duration	0:30:0	Offset	0:17:41
End	14:30	Last Raw End	14:42
Chapters	00:00 0:12:49
Total cuts_time	26 min.

https://2019.linux.conf.au/schedule/presentation/229/
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

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

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
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:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Technical writing and user testing may seem like two compltetly different fields, but they actually intersect more often than not. If you think about it, they both share the same purpose of ensuring that the UX is smooth and streamlined. When in the position of writing documentation, we are always told about the issues that users face on a daily basis. But what if we tumbled down the rabbithole and into the world of user testing, and actually witnessed the users issue first hand? In this talk I want to discuss the many benefits of intersecting user testing with technical documentation. I will share my experiences of writing documnetation and conducting user testing, while also going over several skills and techniques that can be used to convert the results from user testing into better documentation. markdown
Comment:	production notes