Re: User documentation as product specs?

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
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

Where you really need to start is with the user identification, and
work with developers and marketeers to create a list of the users'

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
It sounds exciting! I find it thrilling to have that kind of influence
on the product.

Karen Otto
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

Previous by Author: Re: Re. DTP vs. design
Next by Author: Windows 95 Terminology:minimized dialog boxes
Previous by Thread: User documentation as product specs?
Next by Thread: Re: User documentation as product specs?

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

Sponsored Ads