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:Re: text production process From:Tom Storer <tstorer_tw -at- yahoo -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 29 Jan 2003 06:03:31 -0800 (PST)
Andrew Plato said:
> ...and eat up all sorts of time. Why work when there
> are MEETINGS to be had!
<chortle> I understand this exasperation with
meeting-itis. However, especially in larger
organizations, too few meetings can be worse than too
many. Information has to be shared, decisions agreed
to; relegating this to hallway conversations and email
is no solution. In any case, not an efficient one, in
my experience. It can get certain things done but
prevents the synergy and group communication that
*well-planned and well-conducted* meetings provide.
The problem is that people so often call meetings and
conduct them without adequately judging their utility,
defining their purpose, or controlling their flow.
Rather than saying, "Right, we've decided we need to
come up with a plan for X. Jane, you're responsible
for X, so come up with a plan and submit it," or "Joe,
we need to contact the legal department for advice on
our obligations here. You're assigned the task of
doing that and telling me the results," the organizer
will join a roomful of people in meandering arguments
about what the plan for X should be or what *they*
think legal requirements are and how to meet them...
as the clock ticks and ticks and ticks and the meeting
eventually ends in disarray with no one sure what they
should do next.
But if meetings are called only when they will truly
help a project advance, and when they are conducted
efficiently, politely but ruthlessly halting all
off-topic discussions, inappropriate debate and
blather, then they're very good.
Of course, many meetings are called just because
someone is supposed to do something with a project and
has no clear focus; having meetings provides the
illusion of working. That kind of meeting is the bane
of the workplace.
I realize I've just made an "if-by-whiskey" speech!
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A new book on Single Sourcing has been released by William Andrew
Publishing: _Single Sourcing: Building Modular Documentation_
is now available at: http://www.williamandrew.com/titles/1491.html.
Help Authoring Seminar 2003, coming soon to a city near you! Attend this
educational and affordable one-day seminar covering existing and emerging
trends in Help authoring technology. See http://www.ehelp.com/techwr-l2.
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.