RE: The End Of Technical Writing

Subject: RE: The End Of Technical Writing
From: eric -dot- dunn -at- ca -dot- transport -dot- bombardier -dot- com
To: "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Thu, 28 Oct 2004 17:32:06 -0400

bounce-techwr-l-106467 -at- lists -dot- techwr-l -dot- com wrote on 10/28/2004 04:55:08 PM:
> You're talking a significant beast here. I'm not sure how
> the 25 million is relevant to the writing task nor what it encompassed,
> so it's a bit of a red herring. Plus your DFDs are really insignificant
> the rest of the project. Seeing as the project already had a huge
> "analysis" phase, you've simply continued the corporate culture.
> It allows you to do analysis as a separate step.

Wow. I came across as a little harsh there, didn't I. An off-list response
referred to it in unkind terms.

All I meant is that yes, if 25 million was spent on what I will assume is
the engineering or design analysis, there's no reason not to expect a
significant amount of analysis of the resulting data to produce user
documentation. I didn't mean to sound like I was saying the DFDs were
insignificant only that the time spend on them was insignificant compared
to the rest of the project and certainly understandable.

I'd be wary of a techwriter that didn't spend a week or more learning the
systems and familiarising themselves with existing documents and analysis
before proceeding.

I doubt however that the re-analysis was doing it "correct" and the
original analysis was a complete failure. Unless the claim is that the
original 25 million was spent on user task analysis.

I also doubt how far 6 days of diagramming would have progressed without
the previous outlay and effort towards analysis.

This all goes to show why these discussions don't seem to fit what you
seem to desire Tony. I have yet to be able to determine EXACTLY what it is
that your project was about, nor what field it is in, nor what environment
or expectations you were working under. Without a common point of
comparison between list members situations and requirements it's very
difficult to have a meaningful discussion.

Unless you're simply looking for adoration and self aggrandisement, you're
going to have to tell us more about the project, the requirements, the
users, the hurdles that you had to overcome ....

Eric L. Dunn
Senior Technical Writer


ROBOHELP X5: Featuring Word 2003 support, Content Management, Multi-Author
support, PDF and XML support and much more!

WEBWORKS FINALDRAFT: New! Document review system for Word and FrameMaker
authors. Automatic browser-based drafts with unlimited reviewers. Full
online discussions -- no Web server needed!

You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit for more resources and info.


RE: The End Of Technical Writing: From: eric . dunn

Previous by Author: RE: The End Of Technical Writing
Next by Author: Re: The End Of Technical Writing
Previous by Thread: RE: The End Of Technical Writing
Next by Thread: RE: The End Of Technical Writing

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

Sponsored Ads