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: Is the Customer Always Right? From:"Susan W. Gallagher" <sgallagher -at- STARBASECORP -dot- COM> Date:Mon, 30 Jan 1995 11:03:11 -0800
I guess I hit reply too soon, now I don't know who originated
this message...
> When it comes to matters of design, style and language, is the
> customer/client always right? Or is this an abandonment of the
> professionalism that technical writers rightfully assume?
[snip]>
> So, if technical writers consider themselves professionals, are they
> entitled to say to clients: "No; page numbers can't be aligned along the
> inside margins. Or, no, paragraphs must be indented. Or, no, we don't
> instruct trainees to "originate a plan", we tell them to " devise a plan"
> ... and so on ... whatever you might wish?
> [Suppose a client's specification, if followed, would result is a barely
> readable text. Would you argue against the specification? Or follow the
> client's specification, because "the client is always right"?)
Part of the problem we face is that *everyone* speaks English and
everyoone can write (notice I didn't say *well* here). It follows,
then, that everyone knows how a tech manual should be put together...
And we've all faced those customers (whether they are company
management or software architects or contracting clients) that have
strong opinions about how things should be worded, how many screen
shots we should include, and what font we should use.
I usually listen very carefully without saying a word, then go
back to my office, grab several issues of Tech Comm, Journal of
Tech Writing... and toddle on over to the copy machine. At our
next meeting, I say "I know that you want me to do this your way.
These are my reasons for disagreeing with you." At this point, I
dump about 25 pages or real English-nerd stuff that supports my
position on their lap. :-)
Occasionally I have to do this more than once before garnering
complete acceptance for my doc plans.
Sue Gallagher
StarBase Corp, Irvine CA
sgallagher -at- starbasecorp -dot- com