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: Productivity Gains? From:quills -at- airmail -dot- net To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Wed, 28 Jan 2009 13:52:57 -0600
All of that is nice.
However, what do you do when you've done that? Just report bogus
gains? Improvement is rarely consistent, nor is it always measurable.
And once you've done something, can you use it the next year as an
ongoing improvement? Certainly you can. Make the SWAG, and continue
with your efforts.
Management is always grasping at straws to justify their existence,
and that trickles downhill to us. You have to continue showing that
you are productive and cost-effective. The daily grind.
Scott
At 12:08 PM -0500 1/28/09, John Posada wrote:
> > How about suggesting that management do its job properly instead of
>> wasting employee time by mandating arbitrary "productivity gains"
>> reports of them?
>
>Yeah...that will work.
>
>Look, whether you agree with the request or not, they made it and you
>need to make an effort. Did the specify "General document production"?
>Something that wide is something the doc manager has to worry about.
>You need to worry about your little pond.
>
>Keep in mind that they aren't looking for gains that will add millions
>to their bottom line; little ones will keep them happy, they just want
>to know that you are considerate of the bottom line, which you should
>be doing anyway. Think of it this way. If you have 5,000 employees and
>each of them implement something that saves $500 annually, they've
>moved $2,500,000 to their bottom line.
>
>What have you done on a daily basis? Examples could be
>
>- Scripted anything that was done manually?
>- Added a plugin to your application that make using styles easier?
>- Streamlined a template that you then sent out to the other writers?
>- Initiated any training of your fellow-writers on how to do something
>more efficiently in FrameMaker?
>
>These are just examples.
>
>--
>John Posada
>Senior Technical Writer
>NYMetro STC President
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
