{"id":2248,"date":"2012-01-09T11:32:09","date_gmt":"2012-01-09T16:32:09","guid":{"rendered":"http:\/\/www.encoretechresources.com\/insights\/?p=2248"},"modified":"2012-01-09T20:06:23","modified_gmt":"2012-01-10T01:06:23","slug":"2248","status":"publish","type":"post","link":"http:\/\/www.encoretechresources.com\/insights\/2012\/01\/09\/2248\/","title":{"rendered":"Procedure Writing for the ‘Masses’"},"content":{"rendered":"

On ffeathers, one of the technical writing blogs we visit, a question’s been raised<\/a> about whether comments should be allowed on documentation pages, from, we presume, just about anyone in an organization, and maybe customers, too. Sarah Maddox, who presides over ffeathers, is a technical writer for Atlassian, an Australian software company.<\/p>\n

So here we have another example of the web’s ability to promote an international discussion. The question of who might have access to documentation these days becomes wider than when paper, or a personal computer file, was the medium of expression. Atlassian produces its product documentation on a wikki \u2013 it happens to produce Confluence<\/a>, one of the leading wikki software packages.
\n<\/p>\n

Thus group writing of documentation and procedures via commenting becomes a distinct possibility. And with it, not only might more complete and responsive software manuals arise, but a broader-beamed organization could come into being as well. If communication input is a prime means of organizational development, and it is, allowing a wider circle of commenters on a company’s emerging products could alter the organization’s reality. (If that scares you, read no further.)<\/p>\n

Atlassian allows anyone to add comments on its documentation. “Even people who have not logged in to the wiki \u2013 their comments are recorded as ‘anonymous.'” Many of the people our colleague Dennis Owen works with in providing technical assistance at nuclear power plants will, no doubt, be appalled at the notion of anonymous comments on plant procedures. Nuclear, and other highly sensitive procedures, are available only on a need-to-know\/authorized-to-know basis.<\/p>\n

Yet, providing that enough familiarity exists with the subject at hand, group commenting on documentation can be a consciousness-raising exercise. A user’s point of view is more likely to be included, rather than just the developer’s.<\/p>\n

And there’s always the possibility of heightened awareness as to how the developer is coming across. “What benefits do we, as technical writers, get from the comments people add?,” Sarah asks, “And do we suffer any pain?”<\/p>\n

\"\"<\/a>As a matter of fact, a few months ago Atlassian moved all of its developer documentation – procedures on software being developed for use with its own products \u2013 to a different wiki site. There, they’ve turned off the page comments and have replaced them with two panels at the bottom of each page, one allowing comments on a page in response to inquiries in a question box, and the other requesting detailed feedback if someone wants to provide it.<\/p>\n

Making procedure writing as transparent and helpful as possible is, thus, a challenging job to do well, always with the end user, and sometimes security awareness, in mind. We know that. How to insure that we live it is sometimes another matter. \u2013 Doug Bedell
\n<\/em><\/p>\n

Dennis Owen, indeed, notes that he can imagine the day when all workers will carry an iPad-like device and follow their procedures on a screen instead of paper. In that case, it would make perfect sense to allow plant workers (but not just anyone) to comment. Those comments would not appear on the paper itself, which is to some extent a legal document that can’t have ambiguous information on it. Instead, they would be e-mailed directly to the procedure’s author and added to a tracking database, and he or she would be responsible for addressing them. That would be a nice, seamless way to encourage procedure comments and user-to-author dialogue. <\/p>\n

Many procedures have sign-off steps, so after a job some paper procedures must be retrieved and digitized to become part of a plant’s record. Electronic procedures would capture all those signatures in real time and would save even more time and money.
\n<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

On ffeathers, one of the technical writing blogs we visit, a question’s been raised about whether comments should be allowed on documentation pages, from, we presume, just about anyone in an organization, and maybe customers, too. Sarah Maddox, who presides over ffeathers, is a technical writer for Atlassian, an Australian software company. So here we […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,3,5],"tags":[],"class_list":["post-2248","post","type-post","status-publish","format-standard","hentry","category-communication","category-technology","category-the-writing-life"],"aioseo_notices":[],"_links":{"self":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/2248"}],"collection":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/comments?post=2248"}],"version-history":[{"count":21,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/2248\/revisions"}],"predecessor-version":[{"id":2285,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/2248\/revisions\/2285"}],"wp:attachment":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/media?parent=2248"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/categories?post=2248"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/tags?post=2248"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}