Millions of people around the world are posting blog entries and commenting on those posts. But technical writers have remained on the sidelines by not letting our users comment on our content.
Here are three reasons you should enable commenting:
Reason #1: People are used to writing comments on blogs and web pages. Millions of people post blog posts. And thousands of us add our comments to those posts. For the most part, technical writers haven’t embraced this feature. I’d hazard a guess that most online help or even support web pages do not support user comments.
I recently read Clay Shirky’s book Cognitive Surplus. Shirky argues that in decades past North Americans spent a lot of time watching TV. But with the Internet, people are spending much less time passively sitting on the couch. We’re participating online writing blogs, creating YouTube videos, and writing and editing content on web sites like Wikipedia. Just a small change in how people spend their time can have astonishing changes in our world. He writes:
“Imagine that everything stays 99 percent the same, that people continue to consume 99 percent of the television they used to but 1 percent of that time gets carved out for producing and sharing. The connected population still watches over a trillion hours of TV a year; 1 percent of that is more than 100 Wikipedias worth of participation per year.”
So the Internet has revolutionized how we spend our free time. As citizens and consumers, we are actively contributing to content. But technical writers have remained on the sidelines by not letting our users comment on our content.
Reason #2: Collaboration helps create an online community. Collaboration offers a number of benefits:
* An online community can help each other share solutions, workarounds, and troubleshooting techniques. Technical writer and author Anne Gentle writes in her book Conversation and Community : “…a community of practice can form now that online tools speed up the process of teaching specific techniques and learning them from others.” Workers can spend about a third of their time looking for information. An online community is one of the ways that users can find information quickly.
* An online community builds goodwill among your users. If your company has seriously invested a lot of time and money in an online community with facilitators that respond helpfully and quickly, the company slowly builds positive goodwill among its users. Over time, your company may be recognized as an innovative provider of support―potentially a differentiator when compared to your competitors.
* An online community can improve your content. We all have blind spots. Maybe your online help doesn’t contain the key content that users need. Perhaps they’re looking for specifics on a difficult task. With an active and engaged community, it won’t be long before someone starts pointing out the missing pieces in your content.
Reason #3: Learning new skills for writers. Technical writers are used to interviewing SMEs, and drafting and editing content. By posting your documentation and acting as a facilitator for user comments, you may learn about blogging software and HTML (depending on which tool you use), and online diplomacy. Anne Gentle writes: “Consider becoming a moderator only after you have been a participant for a while. Most online communities do not recognize any sense of entitlement that you may have because of your employer. Instead you must earn the community’s trust and offer real help, even if you only provide links to your online help. Teaching the community to fish (for information) feeds them longer than just answering questions without citing how you learned the information yourself.”
Of course, I should point out that enabling commenting is no guarantee of documentation nirvana. You may be subject to spammers, your company needs to devote at least one person to monitor and respond to user comments, and you’ll probably notice that a minority of your users are the most likely to comment.
Here are a few examples of online documentation that encourages online discussions and comments:
Microsoft’s Developer Network is one of the first examples of community-contributed content.
http://msdn.microsoft.com/en-us/library/ff851953.aspx#6
Atlassian allows users to post comments on its documentation wiki.
http://confluence.atlassian.com/display/DOC/Confluence+Documentation+Home
On a related note, I wrote a blog entry about how to add comments to your documentation using third-party tools, such as Disqus and Wufoo.
Anamika Sharma says
Hi Robert.. Am Anamika from India and work as a technical writer. Thanks for sharing the valuable insights on your blog.. I liked it.. Looking forward to more of such posts…
Have a great time writing…
DITAWriterDITAWriter says
Adding comments to documentation seems to be an emerging trend. Here’s a link to a blog post I did last October that looked at managing user’s comments to docs within a DITA XML-based environment (“Customer Feedback in Technical Docs Using DITA”): http://www.ditawriter.com/?p=368
Robert Desprez says
DITAWriter: Maybe adding comments to documentation is considered “emerging” even though the technology has been with us for years.
Thanks for both of your comments!
RobertL says
Hi Robert,
I’m using Atlassian’s Confluence product for our wiki-based Knowledge Base. We also allow user comments, but haven’t seen any so far after about 7 months. (Although frankly, our user base is relatively small ~250 users).
We even made users’ sign-ons anonymous so that people leaving a comment would not have their names or company’s names exposed.
Any suggestions for prompting comments from the users? Or should I take it as a sign that no news is good news?
Thanks!
Anonymous says
Hi Robert,
Here’s an example of documentation for a software product delivered as WikiHelp: http://wikihelp.autodesk.com/Revit/enu/2012.
Thanks for sharing your insights on this topic!
Autodesk UA Writer
Robert Desprez says
Hi Robert L,
I could give you a bunch of ideas about encouraging people to comment. But even if you did everything right, I would think that you won’t generate a lot of user comments because your user base is so small.
Not sure if you’ve heard of usability guru Jakob Nielsen. He argues that only one percent of people contribute to a site, nine percent are intermittent contributors, and 90 percent just read the content.
If his stats hold true, you may only get a few people commenting on your content.
Hope this helps.
Jen Jobart says
Excellent points — especially about how collaboration helps create online communities.
Marylyn G. King says
You bring up good points about why technical writers need to enable and encourage user comments on their documentation. I think a big reason for the reluctance is that we’re the professional writers and want control over our information product. We all just need to work with the technology and learn from each other to ensure collaboration AND quality.
weight back says
Good web site you have here.. It’s hard
to find quality writing like yours nowadays.
I really appreciate individuals like you! Take care!!