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:On-line help proposal From:Denise Cusano <Denise_Cusano -at- CAPGROUP -dot- COM> Date:Tue, 10 Nov 1998 08:39:52 -0800
Greetings Techwhirlers!
Could you offer some words of wisdom in writing a proposal for on-line
help?
For the past six months I've been trying to persuade my client to develop
on-line help for a large proprietary software app. Now they want to see a
proposal. My background is in Instructional Design, and have developed
only one small help project (100 topics, NOT context sensitive), and can't
really fathom a guess as to how long a project like this might take. I
also have no clue how long it takes a programmer to implement context
sensitive and field-level help.
I'd say that this application is about the size of one SAP R/3 module, and
about as complicated. About 75 process windows and another 50 display
windows. It's for in-house Portfolio Accounting, and the help project must
contain not only "how to use the application" but also "why would you
process a reversal/reentry of a dividend instead of just adjusting it," as
well as "how this transaction will affect other systems." You get the
picture.
I just helped the training team develop a 30-hour, instructor-led training
program, so I'm pretty familiar with how this app works. I want to be
realistic so there are no surprises, but I don't want to scare them off (so
far, they major obstacle has been "too cost prohibitive, too programmer
intensive" and "turnover is so minimal, that everyone will be a pro very
quickly"). Only a small group of accountants is using the app now, but it
is rolling out to a bigger group, and other applications interface with
this system, so non-users often have to access the application to research
discrepancies.
IMHO, it's absurd to have an application this huge without help, but they
don't see it that way.