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.
>I recently watched a team of 10-15 technical
>writers design their own intranet site and
>was surprised at how bad the final product was.
You know the definition of a camel-a horse designed by committee.
Granted, you give little guidance on how the team was organized, but 15
of anybody is too many to collaborate on a single project, unless there
is a hierarchy of responsibility. It could be that all 15 had equal
authority, which is bad because it encourages someone with a strong
personality who may be the least expert to highjack the project.
The 15 people must be divided into small (2-3) people per element, based
on their expertise or natural abilities.