"Like everyone else" is the key. Why are documentation groups 
consistently treated as afterthoughts in so many organizations? If we 
approach projects in the same way as everyone else, with plans, project 
schedules, milestones and deadlines, reviews, and management of scope, 
we should be given the same consideration as everyone else. If a product 
manager notifies development the release date has been moved up, s/he 
fully expects to be told that something has to be sacrificed in order to 
make that deadline. When documentation says it, those blank looks Bill 
talks about are priceless!

Bill Swallow wrote:
> We used to have that problem until we pushed back consistently through
> project and management chains of authority. We're now involved at the
> very beginning like everyone else, and our scope of work affects and
> is affected by the overall project schedule just like everyone else.
> Should someone come in and trim 2 weeks away, we don't think twice
> about asking them what they would like to cut from the documentation
> in order to meet that deadline.
>
> The blank, dumbfounded stares are my favorite. ;-)
>

______________________________________________

Author Help files and create printed documentation with Doc-To-Help.
New release adds Team Authoring Support, enhanced Web-based help
technology and PDF output. Learn more at www.doctohelp.com/tcp.


DITA West 2007--Use a discount code of "TECHCOMMPROS" to get a discount rate of 
$200 off the $800 price if you register before close of business January 15, 
2007. http://www.travelthepath.com/conf/dita2007.shtml
_______________________________________________

Technical Communication Professionals

Post a message to the list: email [EMAIL PROTECTED]

Subscribe, unsubscribe, archives, account options, list info: 
http://techcommpros.com/mailman/listinfo/tcp_techcommpros.com
Subscribe (email): send a blank message to [EMAIL PROTECTED]
Unsubscribe (email): send a blank message to [EMAIL PROTECTED]

Need help? Contact [EMAIL PROTECTED]

Get the TCP whole experience! http://www.techcommpros.com

Reply via email to