After the first time I was told to change the product name on a docset the day before GA, I took to using variables for product names.
One example of pulling a Scottie. If your development process is *predictably* immature, you can use automations to make your job easier and more accurate. A win-win. Cheers, Sean -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Beth Agnew Sent: Wednesday, January 10, 2007 1:44 PM Cc: [email protected] Subject: Re: [TCP] Creeping Deadlines I agree with Tom. Every time someone changes a deadline or the major parameters of a job on me, I give them some consequences that make them think twice about doing it again. I always display a positive attitude "Sure, I can do that for you" but there is a cost "but we'll have to send the manual without an index". I try to pick something that I know they absolutely want, and then show them how it's put into jeopardy because of their last-minute changes. I once had a product manager decide to change the name of the product five days before release. It took two circuits of the block before I was calm enough to tell him the implications of his cavalier decision. The thing he was most concerned about -- releasing on time -- was the first casualty in my plan to accommodate his wishes. In a product with a 2-year development cycle, and a suite of 11 manuals as documentation, a "global search and replace on the product name" was not going to cut it. It's okay to pull the rabbit out of the hat; make sure it's always to your advantage. DISCLAIMER: Important Notice ************************************************* This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail.E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with IPC. IPC reserves the right, to the extent and under circumstances permitted by applicable law, to retain, monitor and intercept e-mail messages to and from its systems. ______________________________________________ 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
