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.
>
> If you are/were involved with a project that is totally
> rewriting a system's user interface, when did you get
> involved? Do you wait for specs or were you involved prior to
> the specs? If yes, what doc did you write?
>
> Bottom-line: at what step in the system rewrite process do
> you think is the "the best time" for a Twer to be involved?
>
> Paul Hanson
I'd encourage you to become involved during the specification phase. As the
technical writer for the project, you likely have a lot to offer in terms of
usability of the product.
On several projects, I've worked exactly that way. I even helped write the
spec. It's a great opportunity to make a difference on the project as well a
great opportunity to really "bond" with the developers and become a real
part of the team.
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-