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:Chat: MIS vs. the user success/horror stories? From:Geoff Hart <Geoff-h -at- MTL -dot- FERIC -dot- CA> Date:Fri, 4 Jun 1999 10:20:54 -0400
First off, apologies for cross-posting to both techwr-l and
copyediting-l (CEL). This isn't really related to either list, so please
reply directly to me unless you want to start a separate thread
more germane to the list. That's a definite possiblity, by the way.
I've just landed a position as a semi-regular columnist for a
newsletter aimed at MIS folks, the ones who run the computer and
end-user support departments at larger firms. (Yes, that's a brag...
guess who's extremely smug today? <g>) I'll be publishing a
column entitled "Devil's advocate". The basic notion is that during
my brief stint doing technical support, I learned that many MIS
people look upon end-users as "the devils who torment us";
however, since I've worked in both worlds (as devil and as MIS
slave), I recognize the value of getting the two groups to work
together... in short, acting as an advocate for those devilish end-
users. The techwhirler and CELmate tie-in is that I'm going to be
emphasizing the aspects of communications and how editors and
writers can form the bridge between the two groups and make both
happier and more productive. Really!
I currently have enough column ideas to get me most of the way
through my first year, and I expect (I hope!) that reader feedback
will provide additional fodder for articles, but I always like to build
up a reserve of articles to get me through dry spells. So if you've
had a particularly good or bad experience that relates to what I'll be
writing about, I'd be grateful for a quick summary that I can use as
the basis for an article. If you personally resolved the problem, I'd
be happy to "give the Devil his due" <g> (acknowledge your
solution). Of course, if I mention your name, I'll run the article past
you first to be sure you agree with how I've presented things.