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:
>
> Luckily, I had an interview with my boss about this yesterday. He is a
> really great boss. He stood by me and agreed this SME was a jerk. I have
> support there, but I think the best thing to do for me is to make sure
> everyone knows why the release was held up, and also 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.
Good point here, Sierra. In the final analysis, it doesn't matter whether an
SME is difficult or how many of them we have to deal with. In the final
analysis, we have to be able to work with all kinds of SMEs, and we have to get
results doing it.
It doesn't do you a lot of good to think of certain SMEs as jerks; you still
have to work with them. "Instituting a better plan" is a great attitude to take
forward with you.
Besides, as this list proves from time to time, there ARE Tech Writers who are
jerks, too. (There, I've said it, the unsayable thing.)