Re: Lone Technical Writer

[Jo Baer <jbaer -at- mailbox1 -dot- tcfbank -dot- com>]

I agree with everything Dawson has said. I would add one thing: In your overall
plan for the year (or whatever your overall plan encompasses), propose a
priority for each project, and for each item within each project. Point out that
the lower priority items may either have to be discarded or done to minimum
standards. Then have someone at the appropriate level approve the priorities.

I work with five other writers, and, for some projects, there are still
documentation tasks that never get done. But we have proposed priorities to the
project team in advance, pointed out that the lowest priority items will be done
only if there's enough time at the end of the project, and gotten everyone to
sign off on the plan.

When multiple project teams compete for our time, which happens often, and
everyone wants his or her priorities bumped up, which happens often, we escalate
to someone who has the authority to allocate our time and resources. (You might
want to get it in writing.) You don't want to be in the position of being a
highly valued writer who's universally resented because project teams think
you're working on the wrong projects or priorities!

--
Jo Baer
Senior Technical Writer
TCF National Bank
Minneapolis, Minnesota
jbaer -at- mailbox1 -dot- tcfbank -dot- com


Weakness Through Strength

Fanatics may defend a point of view
so strongly as to prove it can't be true.

                       Piet Hein


Dawson McKnight wrote: <snip>

> My main bit of advice is that you should be realistic about what you can
> accomplish, and make sure that you communicate that realism very publicly.
> If you can't realistically write all of the documentation you are being
> asked to write, make sure that everyone knows it.  But don't just present it
> as a problem without a solution.  Offer alternative approaches and detailed
> plans for getting the work done.  You may have to act more as a
> documentation coordinator on some projects, organizing teams of non-writers
> within your company to get documentation projects done.
>
> That is not unheard of, particularly if you make the analogy to a proposal
> development situation.  Typically, in proposal development, proposal
> coordinator or manager's job is to gather input from technical experts,
> financial experts, and other SMEs to come up with a complete proposal.  Each
> expert is typically responsible for writing a section or chapter.  In many
> situations, this isn't the full-time job of the experts, but they are doing
> it to contribute to an overall goal that the company has of getting new
> business.
>
> Also, work hard to meet your deadlines and be sure to let everyone know what
> you are working on and how you're spending your time.  People will tend to
> think that documentation is your realm and that somehow it will all
> magically get done by you (and you alone).  Making everyone aware that you
> are working hard to contribute what you can realistically contribute will
> protect you from finger-pointing from co-workers who don't understand the
> constraints you are under.
>
> Keep positive!  You aren't the only one in your situation.  At least you
> know that you are fulfilling a necessary function in your company. :)


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com

A landmark hotel, one of America's most beautiful cities, and 
three and a half days of immersion in the state of the art:
IPCC 01, Oct. 24-27 in Santa Fe.  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.