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.
There is also Open Office or Office Libre (open source version of MS
Office). I rarely need to create diagrams, so I don't tend to ask
management for a Visio license. The few occasions when I need to create
diagrams, I can usually manage with Office Draw. The only caveat is that
there are far fewer image templates for Draw (I did finally manage to track
down some servers that I liked for my architecture diagrams). But if
you're creating flow charts? You should be fine with the default boxes and
arrows.
On Thu, Jan 15, 2015 at 11:47 AM, Dan Goldstein <DGoldstein -at- nuot -dot- com> wrote:
> For proof of concept, you can create flow charts in MS Word. There are
> also free alternatives (Gliffy, etc.).
>
> -----Original Message-----
> From: Cardimon, Craig
> Sent: Thursday, January 15, 2015 11:41 AM
> To: Dan Goldstein; 'TECHWR-L (techwr-l -at- lists -dot- techwr-l -dot- com)'
> Subject: RE: Additional roles for technical writers
>
> Getting approval to buy software, especially something new, can be
> difficult.
>
> I would need to build a proof-of-concept first.
>
> -----Original Message-----
> From: Dan Goldstein
> Sent: Thursday, January 15, 2015 11:37 AM
> To: TECHWR-L (techwr-l -at- lists -dot- techwr-l -dot- com)
> Subject: RE: Additional roles for technical writers
>
> 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
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as jstickler -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>
--
Julie Stickler http://heratech.wordpress.com/
Blogging about Agile and technical writing
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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
