eLearning Learning

Become a Fan

« Writing & Grammar: How Do You Like Your Steak? | Main | Adobe Captivate: Preloaders »

May 12, 2014


Feed You can follow this conversation by subscribing to the comment feed for this post.

Greg Babb

Thanks for the interesting post. The first thing one must consider is the set of standards governing our industry and product. Take it from me; I work in the German-speaking part of Europe (DACH), and companies here are obsessed with standards. Such standards often also dictate what goes into the documentation. So in a way, by the time we've implemented these layers of standards, we're often not in need of yet another standard for the technical communication process itself. Having said that, it might however be useful to check out technical communications standards - if and when we have time for it.

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment

Comments are moderated, and will not appear until the author has approved them.

Your Information

(Name and email address are required. Email address will not be displayed with the comment.)