Yes the string on OC vs CM is interesting.
But for the useful contribution below - its a case of stop the flaw!
BPR notwithstanding its bad press, was about slimming down essential
product/service production processes to allow those who do the work to do it
irrespective of the tasks (and status) of those who were 'indirect' employees.
In old language cut down on staff functions and let the line functions get on
with it. Surely, the present BPR recommendations (from Mike Hammer) merely
replicate the OLD recommendations (of the late '50s onwards) that led to the
growth of OD as a staff function. Explain to me the difference between and OD
manager (c.1975) and a Chief Transformation Officer c. 1998?
This brings me to the OD vs CM. The former was precisely the attempt to
BUILD-IN change (driven by a theory that said this was good) by hiving it off
to specialists (a staff function). Little difference to BPR now - its fallen
in its own hole. This recommendation appears to be the complete antithesis of
BPR.
CM on the other hand is saying change is needed (almost irrespective of why)
so lets do it. It then says well, there are four or five (or whatever number)
of strategies lets use one or two - this is determined by the senior managers
and the context. Dunphy and Stace ('Under New Management, 1990) develop a
model based on scale of change/style of change that has change ranging from
collaborative based fine-tuning to coercive corporate transformation. Its a
case of horses for courses.
My $0.2 worth.
David
--
__________________________
David E. Morgan,
School of Industrial Relations and Organisational Behaviour,
University of New South Wales,
Sydney, 2052, AUSTRALIA.
Ph. +61 2 9385 2181 (w) +61 2 9489 1448 (h)
Fax +61 2 9662 8531 Email
d.morgan@unsw.edu.au
===========================================================
Jim Massfeller wrote:
>
> Davis, Miles K wrote:
>
> > I am doing research on change management (as advertised by consulting
> > companies) and how this does or does not differ from organization
> > development ( as taught in most universities). I have received a number
> > of arguments on why the two are the same and that the term change
> > management is just a marketing ploy to sell a product (this very
> > strongly from my advisor Peter Vaill).
>
> I believe very strongly that change management is totally different from
> organizational development. Change management (allow me to call it "CM")
> came about as a result of many Business Process Reengineering (BPR)
> initiatives. BPR has gotten a lot of "bad press" lately because one of the
> easiest ways to reduce recurring costs is to eliminate jobs. We have
> (unfortunately, I think) move away from the old concept of "a job for life"
> and we are now hearing that college graduates can expect to work for 5-7
> companies during their lifetime.
>
> I understand that companies are now competing in a global market and that
> costs have to be reduced. I also understand that robotics and automation
> can replace people for many tasks. There are tax advantages to investing in
> technology and eliminating people results in savings year after year. But
> my 8 year old, Calvin, was completely defeated by AT&T's automated, computer
> generated voice, collect calling system when I tried to call home while
> traveling recently. Calvin was babbling away and said everything except
> either of the two words (yes or no) that the computer was listening for.
> This is progress?
>
> I am a consultant in reengineering, continuous process improvement, and
> change management. I believe that change management includes the activities
> that take place after the decision has been made to reengineer a process or
> reorganize the structure of a company. CM involves the employee issues such
> as fear of job loss that arise whenever change occurs.
>
> Two good sources of information on CM are:
>
> ProSci's BPR Online Learning Center at
http://www.prosci.com which has
> a lot of excellent material on reengineering. There is an excellent article
> by Jeanenne LaMarsh of LaMarsh & Associates at
>
http://www.prosci.com/change.htm which addresses the people side of BPR
> which addresses communication, education/training, and rewards/reinforcement
> as major elements of CM. She addresses the fear of job loss and resistance
> to change that are two of the major parts of CM and points out that without
> management the process of change, reengineering initiatives often fail. In
> this context, CM is not a system, or a process, or a computer program. CM
> is the actions managers and leaders take to resolve the problems associated
> with change.
>
> Michael Hammer's book "Beyond Reengineering," ISBN 0-88730-729-9 has an
> excellent chapter (13) on "The Process Of Change." In this chapter, Hammer
> addresses Long Term Change and how an organization must be structures to
> enable change to occur. A good quote from page 209 is:
>
> "When a new idea is conceived in a traditional company without
> built-in change enabling mechanisms, it must run a gauntlet of
> gatekeepers before reaching anyone with the authority and resources to
> act on it. Even when a good idea manages to find a champion, it is
> analyzed and pondered by a seemingly endless parade of task forces,
> committees, and study groups. By the time the notion gets to a point of
>
> action, the opportunity it was meant to capture has often passed. The
> implicit assumption underlying all this is that innovation is risky and
> suspect, and that carrying on in the traditional way is almost always
> the best course."
>
> Hammer than states that organizations need two business systems:
>
> The Surface System includes the value adding activities of the
> business processes, the jobs, the structures, the people, etc.
>
> The Deep System is the structure for change and modernization of the
> Surface System. Its three purposes are learning (exploration &
> interpretation), redesign, and transition
>
> Hammer proposes creation of a "Chief Transformation Officer" (CTO) who
> would be similar to and on line with the Chief Operating Officer (COO) or
> the Chief Financial Officer (CFO). He says that finding a CTO today is like
> finding a computer programmer in the '50s because there is no established
> professional school to produce them. He lists desirable traits such as:
>
> - "an organic dissatisfaction with the status quo"
> - "a creative itch to improve things"
> - "the ability to see processes and business holistically"
> - "energized and animated by challenge"
>
> Hammer forgot to include "a skilled and tactful communicator" because
> any CTO who is not will probably be lynched by a mob of dissatisfied
> employees.
>
> In summery, I believe that Change Management has two major parts:
>
> - the leadership actions managers must take to smoothly implement
> change
> - establishing a climate for long term change so that an
> organization can react to external factors and innovation from
> within
>
> I hope this helps...
>
> Jim Massfeller