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.
>--- Sierra Godfrey <kittenbreath -at- hotbot -dot- com> wrote:
>>
>> I think the best thing to do for me is to institute a better plan.
>> This cannot be a black and white thing, because you almost have to tailor the
>> plan according to the SME. If it's a good SME who gets reviews in on time,
>> then less strict of a review plan can be used. But with this guy, clearly I
>> have to use all sorts of methods, like freeze dates.
I've been keeping up with this thread somewhat haphazardly, so I might have
missed something. But...
I get the sense that you're kinda dropping review drafts on the SMEs desk,
willynilly, w/o a schedule of draft production, perhaps w/o coordinating your
draft production with the SW development cycle?
Sure, you have to tailor your plan, but probably not according to the SME, but
to milestones in the development process. For example: deliver srafts for
component level testing, system testing, release to QA, beta release, etc. (of
course, I'm assuming that the development cycle is this advanced, and not simply
fly-by-night coding). If your SME is going to be silly enough to take a month
off, with his own project milestones looming ahead, you've got more serious
problems than just having a recalcitrant SME.
