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: AW: How do hiring companies view TW resumes? From:Keith Hood <klhra -at- yahoo -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com, Chris Despopoulos <despopoulos_chriss -at- yahoo -dot- com> Date:Wed, 24 Mar 2010 08:02:06 -0700 (PDT)
I agree with you. But as to convincing those who need to be convinced...how do you provide that extra value when you're kept on a hatrack? It's been my experience that software engineers and project managers consider technical writers as much a normal part of the process as a cat in an operating room. If you think they consider our products a necessary evil that they wouldn't waste time on if they didn't have to, how do you think they consider us? The goal of creating acceptable metrics is child's play compared to the goal of being accepted as valuable in project planning and execution.
The reasons why inclusion in the process is even more problematic are territoriality and insecurity. The design process is owned by other people and they don't want to share. In too many minds, admitting that a TW can be valuable in the process is tantamount to admitting that they missed out on a good idea. And that is the same to them as admitting they don't know how to do their job.
I think that developing usable metrics would help pry open the door to inclusion in the process, easier than the other way around. Camel's nose in the tent and all that. Metrics aren't a challenge to some manager's territorial instincts.
> But here's one of my soap boxes...
> Tech writers can and should provide more value than merely
> producing pages of user documentation. Organizing and
> clarifying the design process is a whopping-huge opportunity
> for adding value. It resists outsourcing, and it gets
> the writer directly involved at the very start of the
> project. And it fits well with Agile.
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-