Re: Additional roles for technical writers
Yeah, "user interface redesign". That one usually involves treading heavily on someone's toes.
- "I'm sorry, but the user interface is the responsibility of the developer." (We won that battle.)
- "Right, it won't do X, but the customer won't WANT to do X." (We lost, but customers rejected the product.)
- "Stop talking to my developers. I'm the manager. All communication goes through ME." (Explicitly contrary to company policy. Manager ousted.)
- "The problem is [the writer] doesn't understand the software. Oh, wait a minute. Yes, she's right. That's a design error."
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1pJ4zPa
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com
Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.
Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
- Re: Additional roles for technical writers, David Farbey
Previous by Author:
Re: Lost in Translation
Next by Author: Re: $500 million for an error in a policy manual
Previous by Thread: Re: Additional roles for technical writers
Next by Thread: Re: Additional roles for technical writers
Search our Technical Writing Archives & Magazine