Low hanging fruit LO8331

Keith Cowan (72212.51@CompuServe.COM)
05 Jul 96 21:37:04 EDT

Michael Erickson <sysengr@atc.boeing.com> comments:
>My only comments about the easy to make changes are:
>They often are very superficial changes that don't go very deep or result
>in any long term improvement. I also have been involved with the type of
>change activity (taking 10-20% of my time) and the results have been that
>I've been busy as something someone could measure, but looking back two
>or three years, I find most of my efforts are lost in the dust. Real
>changes seem to require the deeper look. Picking the low hanging fruit
>seems to be a reactive activity that only works with the symptoms of
>problems and doesn't ever really get at causes.

I think we are in agreement. The low-hanging fruit term in my post was
misleading. The term I should have used was "easy to identify" when asking
why five times and interviewing enough people and gaining their confidence
so they would be candid and honest. The changes I am talking about are not
easy to implement, just easy to identify.

In one instance, it involved centralizing an operation that was spread
across three centres, changing job descriptions, moving people, training
and some investment in technology. It was not however a major capital
project. Hence the term ENTITLEMENT. It stayed in place and delivers major
benefits in cost efficiencies and improved service levels now after four
years.

However, identifying the move and getting corporate buy-in was easy. It
made sense as soon as people saw it. Even though it had NOT been done for
over ten years previously! ...Keith

-- 


Keith Cowan <72212.51@CompuServe.COM>
 


     Learning-org -- An Internet Dialog on Learning Organizations
    For info: <rkarash@karash.com> -or- <http://world.std.com/~lo/>