Software design and end-user documentation

Subject: Software design and end-user documentation
From: "A.H." <isaac840 -at- yahoo -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 24 Nov 2004 08:50:31 -0800 (PST)

Hello, all,

I am one of a staff of two doing end-user
documentation for a database program created by a NYC
non-profit org. The program has already been released
and we're working with other non-profits, mostly in
NYC, to implement the database and get feedback about
usability, end-user documentation, and other concerns
they may have. I just read,
where it is written good design should reduce the need
for end-user documentation. I know this is true.
Here's my dilemma: The design for the program is
pretty much set. Although there will be minor tweaks
along the way, it is what it is. We have conducted
about 6 focus groups to get feedback on the end-user
documentation, which we are now in the process of
revising. If design is the ultimate issue and we can't
change it, then how else can we best help the
end-user? Has anyone faced the same problem before?

Anthony Hernandez
Technical Writing Intern
Fund for the City of New York

Do you Yahoo!?
All your favorites on one personal page ? Try My Yahoo!



RoboHelp X5 is a giant leap forward in Help authoring technology, featuring all new Word 2003 support, Content Management, Multi-Author support, PDF and XML support and much more! View an online demo:

You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit for more resources and info.

Previous by Author: Help Files
Next by Author: Re: Is wildcard functionality well known enough?
Previous by Thread: RE: Word tips and tricks books or websites
Next by Thread: RE: Software design and end-user documentation

What this post helpful? Share it with friends and colleagues:

Sponsored Ads