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: Content Moratorium From:jgarison -at- ide -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 22 Mar 2001 16:09:10 -0500
I wrote the following earlier today, and I should have prefaced it by saying
that this is a way to cope with the current situation while you work to make
some very needed process changes. (That also helps me sound less like
I worked in the "who knows what the final product will look like" mode for
many, many years. It sucks. You feel like the guy at the end of the parade
with the broom and dustbin. But it is possible to get out in front - or at
least in the head ranks. It takes a lot of work and commitment by all
involved, and a huge amount of management support. Quite honestly, I have
never personally seen it happen in a company larger than 25 people because
such cultural changes are very difficult to foment.
But it can happen as part of a MAJOR corporate overhaul - like when they pay
gazillions of dollars to a consultant company to come in and create better
development processes for the whole company.
So, if you want to cope, heed the following words. But if you want to make
your world a better place, start enlisting powerful allies or look for a
150 Baker Avenue Extension
Concord, MA 01742
My strategy is to figure out what the most the product could do is, and then
write a "skim coat" for everything so that at least everything is minimally
documented. Then, using the skills I teach in my patented "Swamp Draining"
metaphor, I figure out which pieces of the software morass will harden
first, and document them. Then, as more of the swamp becomes terra firma, I
move on and document the solid ground. Eventually, there are still one or
two quicksand areas that I step around as trepidaciously as possible, trying
to catch them as they dry up. This usually gets me as close to getting
everything described as possible at the time they ship. Of course, I keep a
weather eye out on those pieces of dried up sod, too, as often someone is
tempted to add a new hillock, or dig something up that used to work and
replace it with something that may or may not work, but is certainly
If I put too much time and effort into the perpetually slushy stuff,
something awful happens - like they decide to not ship that chunk and I have
wasted a lot of time watching swamp dry when I could have been doing
something more useful.
Well, it makes sense to me ... and I'm starting to sound like Andrew!!!
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available 4/30/01 at http://www.devahelp.com or info -at- devahelp -dot- com
IPCC 01, the IEEE International Professional Communication Conference,
October 24-27, 2001 at historic La Fonda in Santa Fe, New Mexico, USA.
CALL FOR PAPERS OPEN UNTIL MARCH 15. http://ieeepcs.org/2001/
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.