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: Being an Expert From:jgarison -at- ide -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 14 Aug 2002 13:31:39 -0400
Sounds eerily like an experience from my past ...
As doc manager for a project (back in the days of proprietary PCs) we were
developing a PC-like system. We writers noticed that the operating system
people and printing people were not on the same wavelength. I pointed this
out to the project manager who pooh-poohed my concerns.
At the next doc review meeting, I had the Printer folks follow the OS folks.
Since we ran a little late (also by design IIRC), both groups were in the
room at the same time and when the Printer people go to the matter at hand,
all of a sudden he OS people were huddling and pointing and whispering
rather loudly. After the meeting, the OD lead called the project leader over
and said "Houston, we have a problem."
The result: they coded the software to agree with the documentation (which
we had most certainly coordinated).
The moral of the story: You don't have to be an absolute expert. You just
have to listen well and know what to do with the information you get.
And furthermore: in several situations I have been working on absolutely NEW
products that had never been done before. There were no experts - we were
all flying by the seats of our pants. We had to make it up as we went along.
From: Doc [mailto:doc -at- vertext -dot- org]
Sent: Wednesday, August 14, 2002 12:19 PM
Subject: Re: Being an Expert
The InfoDev group (that's me and my writers) had raised the alarm two months
earlier while going through our standard task walk-through. Even though we
only had a prototype and a PFS to work with, we could tell that things were
not lining up properly. Our warnings were ignored. The product shipped six
months late. But the QA and SWE team leads both asked to be included in our
walkthrough sessions from then on.
Save up to 50% with RoboHelp Deluxe. Get 2 great products for 1 low price!
You'll get RoboHelp Office PLUS RoboDemo, the software demonstration tool
that everyone's been talking about. Check it out and save! http://www.ehelp.com/techwr-l
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.