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: Re[2]: multiple TWs for a project From:Jim Shaeffer <jims -at- spsi -dot- com> To:TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 10 Feb 2000 09:46:00 -0500
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.
