RE: Tech Writer Lawsuit

Subject: RE: Tech Writer Lawsuit
From: "McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com>
To: "Beth Agnew" <beth -dot- agnew -at- senecac -dot- on -dot- ca>, "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 20 May 2008 16:08:50 -0400

On Behalf Of Beth Agnew observed:

> The foundational issue, however, is the tendency
> of companies to require unpaid overtime to mask poor project
> Sure, there are times on some projects when heroic effort and overtime
> near release date is required because of unforeseen events, but that
> should be an extraordinary occurrence. If every project, every time,
> only gets done because people are pulling all-nighters and working
> weekends, they are probably allowing rampant scope creep, not tracking
> work correctly, and don't have a handle on change control, among other
> issues. One would think a company such as Sun Microsystems would have
> little more organizational maturity than that.

Disclaimer: I was a little busy at the end of last week, and we (Canada)
had a holiday on Monday, so I'm sorry if this is a tad late...

Here's one thing to consider in the saga:

When a small-ish company with informal/semi-formal processes - that have
worked smoothly for years - is acquired by a much larger, older entity
that has massive, rigorous, thoroughly documented formal procedures, it
can take well over a year for the small company to switch over, without
sacrificing any of the "current" and near-future projects and schedules.
Everything happens slower / takes more time when you are unfamiliar with
the workings of the infrastructure, and a new infrastructure needs to be
overlaid on the ways that you've been accustomed to using... then the
old ways "smoothly" yanked out, leaving the dishes and crystal of the
new forms undisturbed on the banquet table of your work.... er....
ah.... I think we've just witnessed a metaphor be tortured to death -
sorry you all had to see that.

Anyway, I can see that the new members of the borg might be working
extra hard and extra long to accomplish not much more than they did the
year before the collective came for them. (!! Another metaphor? So
soon? OH, just STOP it! Schmeck-schmeck-schmeck! )

Perhaps if the suing writer had held out just another few months, the
operation would have turned the corner and the purchased unit would have
finally blended into the collec... er into Sun, and hew whole group
would have been toasting the success, savoring the bonuses, and settling
into the joys of reasonable, predictable workloads and hours.

I'm just sayin'.



The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.


Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more.

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity!

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Tech Writer Lawsuit: From: Eric J. Ray
Re: Tech Writer Lawsuit: From: Rob Hudson
Re: Tech Writer Lawsuit: From: Beth Agnew

Previous by Author: RE: TC vs TW
Next by Author: RE: Tech Writer Lawsuit
Previous by Thread: Re: Tech Writer Lawsuit
Next by Thread: Re: Tech Writer Lawsuit

What this post helpful? Share it with friends and colleagues:

Sponsored Ads