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.
Re: Defining Professional Technical Communicator (was STC is broken)
Subject:Re: Defining Professional Technical Communicator (was STC is broken) From:"Gene Kim-Eng" <techwr -at- genek -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 2 May 2008 12:19:48 -0700
I would say the responsiblity is to understand the client's
(or employer's) goals, point out issues seen and recommend
solutions, then implement whatever decision is made. If
I'm a direct employee, if my employer sets the requirements
at a certain point despite my recommendations I'm not going
to spend time going beyond those requirments that I could
be devoteing to other projects (if I have loads of spare time
on my hands, that's another matter); if I'm a contractor, I'm
not giving my clients $80/hr services when they have opted
to decline them and engage me for $60/hr services instead.
In either case, if I'm repeatedly asked to do work that I think
is shoddy, it's probably be an indication that I shouldn't be
there.
Gene Kim-Eng
----- Original Message -----
From: <jlshaeffer -at- aol -dot- com>
> Yes, but Beth's original post implies that a real Technical
> Communicator has a responsibility to always raise those? higher level
> issues (like a doctor discussing observed symptoms that have nothing
> to do with why you made the appointment).
> So, is raising those communication and usability issues the
> responsibility of the professional Technical Communicator or is it
> equally professional to just do the work as it was offered?
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-