[Author Prev][Author Next][Thread Prev][Thread Next]
[Author Index (this month)][Thread Index (this month)][Top of Archive]

Re: Fwd: gaining control of a dysfunctional environment?

Subject: Re: Fwd: gaining control of a dysfunctional environment?
From: "Gene Kim-Eng" <techwr -at- genek -dot- com>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Sun, 25 Jun 2006 14:03:43 -0700

I found this in my outbox, so it apparently never went out and may now be
a bit stale, but here it is anyway...

If there's anything the dot.com taught us, or should have taught us, it's that
we should always have that resume up to date, be regularly reevaluating
our positions as objectively as possible and prepared to decide that
it's time to move on. There are still a lot of companies out there that are
being operated the same way the dot.coms were, but even if yours is not
it only takes a small shift in management and who you report to to suddenly
turn what you thought was your dream job into a nightmare that has you
clawing the walls to get out.

Gene Kim-Eng


"Al Geist" <al -dot- geist -at- geistassociates -dot- com> wrote in message news:44909EAC -dot- 8040707 -at- geistassociates -dot- com -dot- -dot- -dot-


You are doing nothing wrong. The problem is not you, it's the company and
unless you own the company, it's very hard (if not impossible) to change
corporate philosophy. The bigger the company, the harder it is to change
things.
I worked at a small company once that held the same "high" regard toward
documentation and processes. Everything was done on the fly. The argument
was by not conforming to a fixed process they could serve the customer
faster and stay ahead of the competition. I gave the company a good three
years and developed some good manuals and marketing collateral, then woke up
and decided that it was time to move on. A short time after I left, the
company folded. Although my ego would like to take credit and it would have
been nice to tell management "I told you so," the reality was this company
operated like a lot of other companies did in the "dot com" era and was
bound to fail because it couldn't get organized.
My advice is to take a good hard look at the company and what needs to be
done and the barriers you need to overcome to get it done. Don't waste time
with a company that won't listen because sooner or later you'll be looking
for work anyway. If you think you can change things, go for it. Otherwise,
get your resume out now and get this bad experience behind you.

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

WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content delivery. Try it today!. http://www.webworks.com/techwr-l
Doc-To-Help includes a one-click RoboHelp project converter. It's that easy. Watch the demo at http://www.DocToHelp.com/TechwrlList

---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-
To unsubscribe send a blank email to techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40infoinfocus.com


To subscribe, send a blank email to techwr-l-join -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.

References:
Re: Technical writing in the development process: From: Melissa Nelson
Re: Technical writing in the development process: From: Gene Kim-Eng

Previous by Author: Re: Technical writing in the development process
Next by Author: Re: Technical writing in the development process? (take II)
Previous by Thread: Re: Technical writing in the development process
Next by Thread: RE: Technical writing in the development process

[Top of Archive] | [Author Index (this month)] | [Thread Index (this month)]

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

Sponsored Ads