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: User documentation as product specs? From:Karen Otto <KAREN_OTTO -at- HP-SPOKANE-OM2 -dot- OM -dot- HP -dot- COM> Date:Fri, 19 Apr 1996 09:53:04 -0600
Item Subject: cc:Mail Text
Frank,
I think your company is trying to do the right thing, but they seem to
have missed the point.
Meeting the users' needs is the paramount objective. The documentation
and the rest of the product are merely tools to achieve that
objective.
Where you really need to start is with the user identification, and
work with developers and marketeers to create a list of the users'
needs.
From that, you can evaluate what the requirements are for
documentation, HW, SW, and other parts of the product.
Finally, you will have to evaluate which of these needs you can
actually fulfill, given your resource restrictions. Then you have a
useful product specification. You can also easily derive priorities
for features from this specification.
Maybe you can influence the product development cycle by presenting
the users' needs in place of the documentation outline as the starting
point.
It sounds exciting! I find it thrilling to have that kind of influence
on the product.
regards,
Karen Otto
Hewlett-Packard
Spokane Division
karen_otto -at- hp-spokane-om2 -dot- om -dot- hp -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net