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 sincerely hope that you have not started another
ridiculous thread about how impossible those darned
SMEs are to work with.
I have two comments:
(1) First, it doesn't do any good to immediately get
your back up and be indigant about the programmer's
"arrogance". Why not give him the benefit of the doubt
and assume that he simply doesn't understand what is
obvious or not to your users.
Remember, that's your job - figuring out who the users
are, what they need to do, and what they need to know
to do it. So explain to the programmer why <xyz> isn't
obvious to a particular user group and explain
(patiently) how important it is that these users
understand it to use the product effectively.
(2) Maybe what you're planning to document is obvious.
I've seen lots of technical writers spend lots of time
to document things that their users already know. I
know when I started writing system administration
guides for UNIX-based software, it took me a while to
figure out what these sysadmins already knew and what
they need to learn from my documentation. Just a
thought.
Bottom line: technical writers are supposed to be
effective communicators. So try communicating with
your programmers. You should be able to explain quite
clearly why your documentation is important to
particular users, and why you need his help to produce
good documentation.
Scott
--
Scott Wahl
Manager, Customer Documentation
Bridgewater Systems Corporation
www.bridgewatersystems.com
--- Mike <techmail_mike -at- yahoo -dot- com> wrote:
> I recently had trouble setting a time to discuss a
> software program with one of the programmers on my
> team. After refusing to work with my flexible
> times, he said, "I don't see why we need to document
> what is obvious already."
>
> Has anyone else on this list ever run into someone
> that arrogant?
_______________________________________________________
Do You Yahoo!?
Get your free @yahoo.ca address at http://mail.yahoo.ca
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-based Help with Macromedia Dreamweaver! (STC Discount.)
**NEW DATE/LOCATION!** January 16-17, 2001, New York, NY. http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.
Sponsored by DigiPub Solutions Corp, producers of PDF 2001
Conference East, June 4-5, Baltimore/Washington D.C. area. http://www.pdfconference.com or toll-free 877/278-2131.
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.