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.
I am working with a someone for approximately a month
now, and I am starting to get a little frustrated with
a couple things, so I thought I would ask for some
advice. I know some of my question will probably start
a pretty lively debate.
The question is... (drum roll please):
How have you other there dealt with someone who
insists time after time after time on harping on a
theoretical notion of what is "good documentation" in
their own eyes when that drastically clashes with the
opinions of others (especially management!!!!).
At our place, as at many others, "good documentation"
is basically whatever the boss SAYS is good
documentation, with as many of our experienced special
touches as we can possibly work in before getting
vetoed.
This issue that caused this to arise is basically a
major management business-related decision to withhold
a specific type of information from the documentation
for important reasons. This person, however, won't
accept that -- even though he hasn't been around long
enough to even fathom what the important reasons are.
No matter how many times I have tried to explain that
it's not an argument worth having, it still comes up.
It is actually in a situation where he was so adamant
with some people here (including management) about
changing an entire vital buisness process (that he
knows nothing about) and got shot down so many times
in a row that he has now informed us that he has
"quit" the document. (How someone who has only been
here a month feels entitled to "quit" assigned
projects, don't ask me!)
I think part of this situation stems from his
stick-in-the-mud nature, which has proven itself
during the last month, and part from some zany notion
that the tech writer is the ONLY person who has the
mental capacity to determine what ought and ought not
be in a document. It does, however, seem to be coming
across --perhaps unintended -- as a condescending "If
I can't do the document MY WAY, then I won't do it at
all."
ROBOHELP X5: Featuring Word 2003 support, Content Management, Multi-Author
support, PDF and XML support and much more!
TRY IT TODAY at http://www.macromedia.com/go/techwrl
WEBWORKS FINALDRAFT: New! Document review system for Word and FrameMaker
authors. Automatic browser-based drafts with unlimited reviewers. Full
online discussions -- no Web server needed! http://www.webworks.com/techwr-l
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.