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.
>
> To me, the ideal way to document this interface would be some sort of
online
> help. Obviously, it would be rather restrictive given the screen size on
> these units, but at least it would always be available wherever the
operator
> is at. However, on several occasions I've been approached by some of our
> sales reps asking for documentation they can show in meetings with
> prospects. Since RF is a big feature of our total system, they often ask
for
> RF documentation. Obviously, they can't show RF help in a sales meeting -
> they probably won't even have an operating RF unit in the meeting. And the
> primary purpose of showing the documentation is really to show off some of
> the system features (not to show off the documentation), complete with
> screen shots.
>
> I'm sure sales/marketing is going to want to do a printed manual. In an
> ideal world, we would do both, and probably will at some point. But how do
I
> convince the PHB that we should put the needs of our current users over
> those of our sales force? A printed manual will look pretty, and will
> probably make for a nice door stop for a team leader on the floor. But I
> can't see that it would be of much practical use except perhaps in
training
> situations.
>
> Any suggestions from those of you who have had to balance marketing needs
> over practical application?
>
A few random thoughts:
Does PHB = sales/marketing? Sounds like they're just presenting their "Like
to have" list to the bosses. You should point out that Help is for the
user. Period.
However, why not offer to modify the handheld help into a manual? It could
just be a compilation of the help you write, perhaps as a Powerpoint
presentation. Or better - how about offering to write a training manual
also? That's something that current users, sales people, and new customers
can all use.
It sounds to me like you might have two separate projects - the handheld
help and some sort of training manual. Just show the PHBs how everyone will
benefit - both in the organization and customers. And show the sales
weenies how this will enhance the product by offering training for new
users.
Paul Strasser
Windsor Technologies, Inc.
2569 Park Lane, Suite 200
Lafayette, Colorado 80026
Phone: 303-926-1982
FAX: 303-926-1510
E-mail: paul -dot- strasser -at- windsor-tech -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Free copy of ARTS PDF Tools when you register for the PDF
Conference by April 30. Leading-Edge Practices for Enterprise
& Government, June 3-5, Bethesda,MD. www.PDFConference.com
Are you using Doc-to-Help or ForeHelp? Switch to RoboHelp for Word for $249
or to RoboHelp Office for only $499. Get the PC Magazine five-star rated
Help authoring tool for less! Go to http://www.ehelp.com/techwr
---
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.
