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.
Our ordinarily peerless management was recently infected by the
"pointy-haired manager" virus, and before we could isolate them and let the
fever burn itself out, they managed to jump on a bandwagon known as
"Kaizen". The basic notion doesn't appear to be particularly different from
any of several other quality-improvement religions (e.g., TQM, continuous
improvement): it dismisses all the competing approaches, cloaked itself in
the usual religious fervor, and invents its own important-sounding,
consultant-enriching jargon. (Can you tell I'm skeptical of management
I _do_ trust our managers to exercise basic common sense rather than blindly
following yet another of the trends du jour that have increasingly afflicted
business for the past few decades, but before we enter into this brave new
adventure, I'd love to hear from others about their experiences with this
process. Opinions? War stories? Cautionary tales?
"Technical writing... requires understanding the audience, understanding
what activities the user wants to accomplish, and translating the often
idiosyncratic and unplanned design into something that appears to make
sense."--Donald Norman, The Invisible Computer