RE: Antwort: Re: Responsibility, blame, managers, and getting the job done

Subject: RE: Antwort: Re: Responsibility, blame, managers, and getting the job done
From: MList -at- chrysalis-its -dot- com
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Tue, 8 Apr 2003 14:20:17 -0400



> But, if management has not been positively encouraging
> cooperation or has infact
> been working against it where do you stand?

First, I'd hope that I hadn't been giving cause...

Second, I'd request, in writing, that the particular management
person say what they meant, in writing. Most likely, I'd sum
up my understanding in a memo/e-mail and ask "Is this your
understanding of the situation? Please clarify."

If they were being deliberately obstructive or condoning non-
cooperation), then I'd bury them in specific requests for
information. I'd make it a special point to highlight aspects
of the specs that had changed (but not been yet recorded) or or
the developing product that were not according to spec, and
I'd show just a couple of samples from my customer documents
that would be different depending upon the answer -- with the
stated or unstated implication that there were plenty more.

If that wasn't giving results, then I might recruit other
stake-holders, like the Customer Support people who would
inevitably have to take up the slack, or the Marketing and
Sales people who would have a tougher job if the product
documents began to get a bad rep.

If all that wasn't sufficient, then I might bump the problem
upstairs, with a nice recorded history to back me up.

But then, that would be a very different environment than
I'm working in now, so another environmental factor might
be very different as well -- that is, I might face reluctant,
close-mouthed developers, but have the compensation of actually
having nearly-final, working product from which to create
documents. As it is, I work with a great bunch of people, who
are endlessly patient (even if I'm not bringing homebaked treats),
and so I'm working a great deal from their input, and only using a
product sample to verify and clean up, near/at the end of the
release cycle.

/kevin

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Purchase RoboHelp X3 in April and receive a $100 mail-in
rebate, plus FREE RoboScreenCapture and WebHelp Merge Module.
Order here: http://www.ehelp.com/products/robohelp/


Help celebrate TECHWR-L's 10th Anniversary starting this month!
Check out the contests at http://www.raycomm.com/techwhirl/special/contests/
Happy birthday to you, happy birthday to you, happy birthday TECHWR-L....

---
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.



Previous by Author: Reading level (was RE: Principles for procedure writing)
Next by Author: RE: IX-nay (was RE: About Responsibility and Fault)
Previous by Thread: Re: Antwort: Re: Responsibility, blame, managers, and getting the job done
Next by Thread: Re: Antwort: Re: Responsibility, blame, managers, and getting the job done


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

Sponsored Ads


Sponsored Ads