Re: Doc Design and Conventions

Subject: Re: Doc Design and Conventions
From: "Janoff, Steve" <Steve -dot- Janoff2 -at- Teradata -dot- com>
To: "John Garison" <john -at- garisons -dot- com>
Date: Thu, 5 Nov 2009 21:47:43 -0500

John,

What did you have to start with in this case? Just a product and a goal? Were there any engineering specs? Were there any design meetings?

You're saying the software had not been designed at all yet?

In other words, what kind of information did they give you as a starting point, and what kind of instruction were you given as to how to proceed, or did they just say, "Just write it the way you see it, and we'll develop it that way"?

I think it'd be interesting to hear how this project played out.

Thanks,

Steve

PS - Congratulations on having the good fortune to have that kind of experience! And that kind of trust from the person in charge.


-----Original Message-----
From: John Garison [mailto:john -at- garisons -dot- com]
Sent: Thursday, October 29, 2009 8:33 PM
To: Janoff, Steve
Cc: Chris Despopoulos; techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: TECHWR-L Digest, Vol 48, Issue 25

I have had the opportunity to write a manual that the programmers were told to use as their guide to what the software should do and how it should operate. It didn't happen all that neatly, nor necessarily at the beginning of the project, but it ended well.

My 2¢,

JG

Janoff, Steve said the following on 10/29/2009 9:44 PM:
> H
>
> PS - I forget where I read it but Donald Norman once suggested that
> the user manual be written before the product was even designed.
> That's almost like screenwriting. A heck of an idea! On the other
> hand, you're limited to the writer's vision of how something should be
> used, which could be constrained by what he/she is already familiar
> with in the world. I mean, could a writer have written the iPod user
> manual before the thing was developed? I doubt it, unless that writer
> was incredibly visionary.
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at:
http://www.doctohelp.com/

Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/ for more resources and info.

Please move off-topic discussions to the Chat list, at:
http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat


Follow-Ups:

Previous by Author: Re: Doc Design and Convention ( was TECHWR-L Digest, Vol 48, Issue 27)
Next by Author: RE: Doc Design and Convention ( was TECHWR-L Digest, Vol 48, Issue 27)
Previous by Thread: Re: Doc Design and Conventions
Next by Thread: RE: Doc Design and Conventions


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

Sponsored Ads


Sponsored Ads