Defining Professional Technical Communicator (was STC is broken)

[jlshaeffer at aol.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?

Jim
 

 


 

-----Original Message-----
From: Gene Kim-Eng <techwr at genek.com>
To: techwr-l at lists.techwr-l.com
Sent: Thu, 1 May 2008 9:19 pm
Subject: Re: STC is broken










Whether the client just wants documentation that meets their current
requirements, templates, formats, etc., or a comprehensive reboot
and redesign is the sort of thing that needs to be defined at the front
end of the contract.  This is especially true if you charge different
rates for these alternative levels of work/rework.

Gene Kim-Eng


front end of a contract.
----- Original Message ----- 
From: "Michael West" <mbwest at bigpond.com>
> In many cases that's all they'd be allowed to do. We can recommend, explain,
> cajole; but in the end the guys who pay us have the final say in the scope
> of work. This is especially true in short-term contracting situations. Where
> we have more time to spend campaigning for usability, and we can produce
> prototypes and examples, we have a better chance of being heard.