How’s that? ‘Emotionally Satisfying’ Procedure Writing?
Posted on June 12, 2013
Filed Under Business, Communication, Technology | Leave a Comment
Imagine viewing technical writing as “an emotional experience.” Larry Kunz does just that, but he doesn’t propose approaching a technical manual or document as a potboiler. What he means is producing technical writing that elicits “a feeling of trust,” and that’s right on the mark. Good technical writing should produce a feeling of confidence in its utility.
Think of the times when you’ve been frustrated by obscure or meandering directions. The only emotional reaction they likely produced was annoyance, and who needs that?
Kunz is a product manager and information architect with SDI, a global consulting firm. “Technical writing,” he advises, “exists to help someone perform a task or gain some knowledge.” Indeed, good technical writing should elicit feelings of accomplishment. You should be able to trust a manual or procedure to get you efficiently to a desired result. That feels great when it happens!
Our Encore owner and colleague, Dennis Owen, notes, however, that emotionally satisfying technical writing can be hard to produce when it has to be based on a prescriptive writer’s guide or on satisfying numerous reviewers “who don’t necessarily place the reader’s interests uppermost.” Yet technical systems don’t exist for themselves, but for those assigned to operate and maintain them. Why make work-life a downer for the users?
Illustrations can help. Dennis recalls when he once added sidebars to a technical report on bar coding he wrote “on various things I’d discovered when researching the topic. For example, bar codes began in the railroad industry, as big symbols on the sides of rail cars so that trackside readers could track cargo. Also, bar code-like symbology is actually quite old. The bars and dashes on the South Korean flag, for example, convey a message and hark back to a very old way of communicating. As I recall, though, none of my sidebars made it to the final printed document.” Too bad. Illustrative material can highlight and hasten understanding of a process.
“Customers,” Larry Kunz notes, “are willing to read technical content when they trust it to be helpful. Granted, many readers will sooner trust other readers than the ‘official’ company documentation.” Hence the rise of online forums.
Yet when an employee is in a plant or other workplace setting with a technical manual or procedure in hand, he or she wants it to be revealing, not puzzling. The satisfaction of success is a highly emotional reward for work done well, by the writer and reader alike. – Doug Bedell
Comments
Leave a Comment
If you would like to make a comment, please fill out the form below.
Recently
- Presentations With Forethought
- Technical Writing’s Lineage – Surely It’s Deeper than Digital
- At the Holidays, Twitting Amazon
- Successful Cookie Baking – From Mom, an Acknowledged Expert
- Slides for a Tech Writer’s Craft
- Digital or Not, Be Clear
- Being Watchful About Digital Designs…
- When Proposals Don’t Click, Keep Making Them Anyway
- Like a Good Gardener, Help an Enterprise Keep Itself Current
- We’re Leaders All, And Need to Think That Way
Categories
Archives
- January 2017
- December 2016
- November 2016
- October 2016
- September 2016
- August 2016
- July 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- November 2014
- October 2014
- March 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
Blogroll