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.
Re: Necessity of Doc Plans for a Single Chapter or Section
Subject:Re: Necessity of Doc Plans for a Single Chapter or Section From:Andrew Plato <intrepid_es -at- yahoo -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 19 Nov 2001 07:54:02 -0800 (PST)
<SteveFJong -at- aol -dot- com> wrote in message news:130079 -at- techwr-l -dot- -dot- -dot-
>
> Andrew, if you have ever done work for a client without signing a
contract,
> then I will happily accept your advice. Otherwise, I think you're
indulging
> in preaching what is good for me but not for thee.
My work is much different than a full-time employee. Yes, we always do a
project assessment report before beginning a documentation project. It
includes such things as what the document will cover, timeline,
requirements, etc. But this is for a consulting arrangement, and it is a
discernable amount of work, and we are competing to win that work.
Moreover, it isn't about planning the entire document, its planning the
project. Our projects often include a lot more than just writing a
document. While we may do a doc plan of sorts once the project us
underway, this usually consists of an email exchange between the lead
writer and our client contact.
I surely wouldn't waste my client's time demanding a new project report
everytime a word changed. That is ludicrious. Now, if a client wanted it
(and would pay) that's a different story. :-)
As an employee, a doc plan should be written to help focus work, not to
CYA. If you were writing a brand new doc from day one, yes a plan would
help focus people. But it must be written as such.
Writing a plan just so you can demand strict adhearance to that plan later
on when things change is a pretty pathetic reason to write a plan in the
first place.
Andrew Plato
__________________________________________________
Do You Yahoo!?
Find the one for you at Yahoo! Personals http://personals.yahoo.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr
---
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.