Subject:Re: First Technical Writer From:Chris Morton <salt -dot- morton -at- gmail -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Thu, 11 Mar 2010 10:24:26 -0800
Congrats, Melissa.
My suggestion is to start by creating a company-specific style guide that
addresses common errors you see in the current documentation (and any stuff
that is client-facing, e.g., marketing pieces). This (friendly) guide could
eventually be distributed on a wide scale when the timing and perceived
reception are right (no one wants something shoved down their throat from
the "know-it-all new kid"). The guidee might also incorporate usage of
company collateral such as its logo, etc.
Another way in which you could make an immediate mark is to create a
corporate PowerPoint template for all to use. The Techwr-l archives also
contain PPT presentation tips you could adopt and pass along to those who
might make use of such info. If you can't find these and would like a copy,
send me a private e-mail and I'll forward a copy.
Best of luck!
> Chris
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
