Having been through a number of reorgs, I consider them rearranging the
deck chairs on the Titanic. New structures are rarely permanent, by
themselves they can not solve underlying issues and serve no purpose
other then giving some senior exec something to pass the time.

A far more important management function, to my thinking is to come up
with a two items

First a rational method for giving priorities to work that both IT and
outside staff can live with. Without that, no management structure can
succeed.

Second is a process for moving projects and operational tasks through to
completion that assures a quality end product. This process MUST avoid
the "no time to do it right but plenty of time to do it over" trap that
kills IT morale and makes IT look like fools to the users.

The problem, of course, is that the managers must now tell people "no"
or "wait" and they hate that, so they simply reorg instead of making the
tougher decisions that are supposed to earn them the bigger $.

Of course, what do I know. As a DBA I am a management victim.

My $.02


-----Original Message-----
From: Zelli Brian
[mailto:oracledba-ezmlmshield-x19244911.[Email address protected]
Sent: Friday, September 30, 2005 11:34 AM
To: LazyDBA Discussion
Subject: org structure

Hello all,
We had a radical shakeup of management in our IT organization and now
the "new" management is trying to form a hierarchy chart. Can any of
you give me a high level overview of how your company is organized as
far as departments within IT? I have a feeling that if we don't do this
right out of the gate, we will be in the same chaotic situation....

Brian


--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html


Oracle LazyDBA home page