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: Building a documentation knowledgebase From:chevotilburg -at- postmaster -dot- co -dot- uk To:techwr-l -at- lists -dot- raycomm -dot- com Date:Tue, 17 Feb 2004 05:10:19 -0700
> If both you and the trainer have (legitimately) full
> calendars without this new make-work project, then
We've been asked to put some priority on this. The guy in charge has been
asked to drop his current task and spend full time on it.
> One thing that you could do is to point this out
> and suggest that the company rent the services of
> a consultant who has some actual experience in this
My boss at the time put this plan in motion- even had a consultant come by
but it was shot down. :( Based on everyone's comments - i'll put forward
the following:
- requirements per group and current workflow per group
- end result each group would like to see
- an owner per group
- how this affects the current work flow
- solution that would suit all groups
