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.
Sorry, but I'm respectfully sticking with "guaranteeing," a word I agree
should rarely be used. In my other life as a teamwork consultant, I have
probably spent far *too* much of my life reviewing more than 500 studies
on these issues. I've seen no scientific (versus anecdotal) evidence of
a team that *prospered* for more than a year in the conditions of
constant long hours, and significant contrary evidence of properly
project-managed teams outperforming (and outlasting) teams that just
used long hours instead.
Though I usually agree with Gene, I don't even believe his idea of
managers and employees who like long hours finding each other would
work. The human mind and body are subject to certain limits, plus the
situation reduces flexibility in the project (when one 60-hour person
goes down, you lose 50% more labor hours from your project schedule).
Under those strains, other problems begin to creep into the environment
that increase the stresses over time to levels the team can't withstand.
Dori's wonderful post makes this point with the way she manages stress,
in part, by (I infer) ignoring irrational demands from people who are
not managing their stress as admirably as she does. Right now, I envy
her situation even though I only work 40 hours. But over time, I'd bet,
that environment will deteriorate to where she is no longer enjoying it
and be willing to put in the long hours.
My point, again, is not that a team can't get a job done through brute
hours. I am questioning the real financial (and of course, human) costs
of doing it that way rather than applying all available best practices
to work as cost-effectively as possible.
Thank you all for the discussion,
Jim
Jim Morgan
Senior Technical Writer and Team Development Consultant
(www.suddenteams.com)
Seattle, WA
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
