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.
The best way to learn this is to do it. You'll need flow-charting software (big fan of Visio here) and the ability to interview the folks who actually run the current processes. Of course, there are a million examples online to inspire you. Once you document a process clearly, the people who use it should have ideas for improving it.
As for selling the concept , if your company is subject to US regulations or any international standard (e.g., ISO), you might not need to sell this at all. SOPs are SOP. Otherwise, show them one good sample and see if you can make the sale.
-----Original Message-----
From: Cardimon, Craig
Sent: Thursday, January 15, 2015 11:31 AM
To: 'techwr-l -at- lists -dot- techwr-l -dot- com'
Subject: RE: Additional roles for technical writers
How does someone start documenting business processes?
How do you sell that to management?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy & Procedure Guides, eBooks, and more using Microsoft Word | http://bit.ly/doctohelp2015
