Over the last several months I've delivered a talk entitled Why Technical Writers Shouldn't Be "Writers" at several STC regional meetings and conferences (such as last week at DocTrain West)
The presentation was inspired by an earlier post on this blog, and takes a look at why we are so focused on the written word, and presents a few ideas about better ways for us to deliver our message to the end user in a way that increases customer satisfaction.
What can we as documentation professionals learn from just observing the world around us, and how people communicate? What is the impact of new Web2.0 technology and social networks, and how they will change the way we need to view documentation design, distribution and usage?
Several people have asked for copies of the slides I used, so here they are.
However the slides are not full of text and bulleted lists, in line with the central theme of the presentation, they are mainly graphics used to illustrate an idea or to serve as talking points. This is a "performance best seen live."
If anyone is interested in me delivering this presentation to their STC group, the writing team at their company, or a conference - then just send me an email, and let's chat.
Why Technical Writers Shouldn't be "Writers"
View more presentations from 4JsGroup.
1 comment:
The graphics are fine, but the words are absolutely critical for those of us with print reading disabilities. If graphics, slides and other visual elements are included in any form of communication, reasonable accommodations must be made to ensure they deliver equal accessibility to listeners and readers with disabilities. Not only is accessibility the right thing to do, but it is often the law.
Post a Comment