TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
It's my belief that the technical document output of the automotive
industry, if not the greatest in the world, is at least one of the top
ten groups. And having, seemingly, had to deal with all of it I think I
can say with some authority that the standard for writing step
procedures is...every possible way that it can be done, well or badly.
I would have to agree with the general trend of style advice from this
bunch of experts. Your teacher's style is not one I've seen very often.
-----Original Message----- From: Gene Kim-Eng
Generally speaking, anytime anyone says "never" do something in a
document I wouldn't give the adminishment much credibility. Almost
every seemingly bad idea is the right thing to do somewhere.
In this particilar case, my response is that "follow these steps" is
ALMOST always unnecessary and your teach is wrong MOST of the time.
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-