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.
Subject:Re: How do hiring companies view TW resumes? From:Bill Swallow <techcommdood -at- gmail -dot- com> To:Christine Leisgen <Christine -dot- Leisgen -at- gmgcolor -dot- com> Date:Tue, 23 Mar 2010 09:52:18 -0400
Without getting into too much detail, you need to align with the
strategic goals of the company. You know those boring old mission
statements? They are actually used by the mucky-mucks to measure and
direct company successes. You need to whittle the 10-mile-high
rhetoric down to something tangible, and then create measurable goals
around it.
Yeah, I know... "yawn"... "It never works"... "you've been breathing
the thin air and drinking the top floor Kool Aid again"...
Just saying, it works. You need to measure success not by your own
standards, but by the company's. They may conflict, they may align,
but that's not up for discussion. If you work for a company, success
is defined by the company, and anything else that jives with you is
gravy (and I love gravy).
I'm sorry that I cannot get into too much detail. I have my own
strategic goals, and giving the farm away for free isn't on that list.
I can recommend that you start with "Managing Your Documentation
Projects" by Hackos to get a feel for some of the metrics available to
you <http://www.comtech-serv.com/managing.shtml>. Other than that...
Well, per list rules I'm not allowed to say anything more than "look
at my sig".
On Tue, Mar 23, 2010 at 4:45 AM, Christine Leisgen
<Christine -dot- Leisgen -at- gmgcolor -dot- com> wrote:
> I would be interested in this as well. Our CEO just happened to demand exactly the same thing, not only for documentation, but for the entire development department, but it would be a start to hear some opinions for TWs.
>
> In the following are ideas we came up with so far:
>
> - Priorize use cases and review after the release, whether the products cover them sufficiently.
> - Survey, either web or telephone based, directed at customers, in regular intervals. Compare the results.
>
> Any suggestions, how you evaluate the quality of your documentation or products?
Available for contract and full time opportunities.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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-
