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: getting info From:"Michael West" <mbwest -at- bigpond -dot- net -dot- au> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Sat, 7 Jun 2003 09:07:28 +1000
Subject: Re: getting info
> All I had to do was marry one of the
> software guys and now everyone is quite helpful.
Ah, but how many shots do you get with that old
ploy before you're found out?
More seriously, this problem can best be addressed
before it happens -- in the planning and scheduling
stages. You should try to make your deliveries
contingent upon scheduled reviews and interviews
with SMEs. Get it into the SIGNED-OFF project plan
that you deliver a final draft <n> days after the
completion of the scheduled reviews -- and publish
the schedule often. That doesn't guarantee you'll get
their time when you need it, but at least they can't pretend
that it's something that wasn't in the plan
Other than that, think of how journalists get their
scoops. Do you think they get a friendly welcome when
they go after a story? Persistence and persuasion are part
of the successful tech writer's toolkit. Choose your own
style, but you can be sure that whining and complaining
will never get you what you want.
Something else that's worked for me in the past --
developers and engineers are the least likely people
in the organization to appreciate the importance of
end-user assistance material. Cultivate supporters in
Sales & Marketing or Customer Service who can put
pressure on developers to give more attention to the
quality of your deliverables. They know how frequently
a good documentation package can be the deciding
factor in a sales decision. Developers don't -- and
wouldn't believe it if it happened in front of them.
---
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.