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.
Re: Has anyone ever written the user guide before the product was developed (coded)?
Subject:Re: Has anyone ever written the user guide before the product was developed (coded)? From:John G <john -at- garisons -dot- com> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 12 Nov 2010 15:44:13 -0500
I did this once many years ago and it worked out very well. It was a
desperation move by the product manager to save an off-the-track project,
but it worked. I wanted to do it again but they said it was too unorthodox a
development methodology.
If you can finagle your way into the spec-writing side of things, it's very
similar and you end up with a darned good spec that lends itself nicely to
creating a great set of docs.
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-