RE: A technique to get on development's good side

[John Posada <jposada01 -at- yahoo -dot- com>]

1) Write it
2) Submit for review and document who and when it was submitted
3) When you get no response, ask for alternate means of submission
and document that you asked.
4) When you get no response, submit again, cc next level of
management, say you are going to release as is if you get no
response, and document this
5) When you get no response, release it as is.

When you are asked "Why did you release something that was wrong,
produce #2-#4

--- "Downing, David" <DavidDowning -at- Users -dot- com> wrote:
> 
> The problem is that moving on isn't an option when you gotta find
> out something you need to know in order to write your document.
> The best way to deal with it is to try different approaches, and
> hope people will meet you half way. Otherwise, chalk it up
> to "people" and move on as much as you can. It can be frustrating.


John Posada
Senior Technical Writer

?Never be afraid to try something new. Remember that a lone 
amateur built the Ark. A large group of professionals built 
the Titanic.? - Dave Barry

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

New from Quadralay Corporation: WebWorks ePublisher Pro!
Completely XML-based online publishing. Easily create 14 online formats, including 6 Help systems, in a streamlined project-based workflow. Word version ships in June, FrameMaker version ships in July. Sign up for a live, online demo! http://www.webworks.com/techwr-l

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.