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.
Subject:Re[4]: multiple TWs for a project From:Harry Hager <hhager -at- dttus -dot- com> To:techwr-l -at- lists -dot- raycomm -dot- com, jims -at- spsi -dot- com Date:10 Feb 2000 12:53:07 -0600
Jim Shaeffer,
I do not think this an 'either or' situation with only one of the
following approaches being the correct approach for a team of tech
writers:
1. Lots of up-front planning and no, or minimal, coordination and peer
review needed.
2. Not so much up-front planning and lots of coordination and peer
review to avoid disaster.
I have used and prefer the following approach:
1. Lots of up-front planning and regular (weekly or every other week)
team meetings and regular coordination and peer review.
I guess I don't understand why anybody would object to or be afraid of
this approach.
H. Jim Hager
______________________________ Reply Separator _________________________________
Subject: RE: Re[2]: multiple TWs for a project
Author: jims -at- spsi -dot- com at Internet-USA
Date: 2/10/00 9:49 AM
Harry Hager asks:
So, Tony, you are advocating that tech writers individually go off in their
own corner, write their chunks of a large project, and then add it to the
pile of chunks without any coordinating or peer reviews in the meantime?
Jim Shaeffer chimes in:
If (note the IF) the up-front planning is done right, this is the way it
should work. In this case, any coordination or peer review, while necessary,
will be minimal. The "chunks" will be easy to knit together. If major
decisions and picky usage points are left until the peer review /
coordination phase, we are asking for trouble.
Of course, there are many degrees of planning, peer review and coordination
that can work in many combinations.
Jim Shaeffer
Jims -at- spsi -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Sponsored by Weisner Associates Inc., Online Information Services
Training & consulting for RoboHELP, Dreamweaver, HTML, and HTML-Based Help.
More info at http://www.weisner.com/train/ or mailto:training -at- weisner -dot- com -dot-
Your web site in 32 languages? Maybe not now, but sooner than you think.
Contact ForeignExchange for the FREE paper, "3 steps to successful
translation management" (http://www.fxtrans.com/3steps.html?tw).
---
You are currently subscribed to techwr-l as: hhager -at- dttus -dot- com
To unsubscribe send a blank email to leave-techwr-l-27056L -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
