Discussion: View Thread

Expand all | Collapse all

Technology-driven change

  • 1.  Technology-driven change

    Posted 02-25-2000 09:33
    Rule 1. WIFM. What's In It For ME? People will accept the pain of
    transitioning to a new situation when they see the new situtation (not the
    transitioning) has something in it for them.
    Rule 2. Transition requires learning. People learn fastest from someone
    who has direct influence over their future.

    In the example cited by Dick Montgomery, the people learned directly from
    the CEO (fast). And they learned a new pattern to which to conform. Being
    already trained conformists, this was not too much of a transition.
    Turning them into non-conformists would have taken lots more time.
    Apparently, however, the new pattern smelled like freedom and the smell of
    freedom is unmistakable. It remains to be seen how long it took (or takes)
    for them to learn that "freedom from" is not the real freedom and how well
    they leverage "freedom to.".

    Now the bad news.
    There is little demonstratable benefit in ERP but there is a decade of
    horror strories from those who have undergone such trauma.
    Be careful to discern whether you are talking technology in general or
    talking specific, perhaps even toxic, forms of technology.


    On Thu, 24 Feb 2000 Steve Harper wrote RE: public sector organizations --
    and/or our expectations?
    [...]
    >I would like to pose the following questions to the list:
    >
    >1) In times of rapid technological change, what, if anything, can external
    >people (consultants) do to help organizations prepare for and absorb that
    >change? [...]
    >
    >2) What types of education and training can future managers (both technical
    >and non-technical) be provided that would help in this process? [...]
    >
    >3) Is there/should there be a role for "change management" consultants
    >(OD?) in technical consulting organizations [...]?
    >
    >I am interested in the academic, practitioner, and consulting perspectives
    >on these questions. Replies will be most welcome.

    Jack Ring, 32712 N. 70th St., Snottsdale, AZ 85262-7143
    480-488-4615, Cell) 602.369.4615
    A system must be designed not for the existing situation but for the
    situation that will exist after the system is activated.


  • 2.  Technology-driven change

    Posted 02-25-2000 14:52
    Jack --

    Thanks for the two rules.

    I would agree that WIFM is the key. Unfortunately, sometimes the benefits
    of change (to senior management) are distributed differently than the pains
    (to the front line), so meeting this rule can be a challenge. Nonetheless,
    it serves as a good place to start.

    Part of the challenge to rule 2 is how to consistently identify the "early
    adopters" who can exert the kind of influence necessary for success.
    Frequently, unfortunately, they are not the designated leaders of the
    organization. Any thoughts on what the characteristics are of those early
    adopters?

    I was also interested in your comments about ERP. While it is true that
    there are spectacular failures in that field (a 60% failure rate in
    implementations), it is also true that, for some companies, the integration
    that has come with ERP systems has helped them solve significant
    operational and strategic problems. Examples of the problems are:

    1) No single "source of truth". One client I worked with recently had two
    different systems (merchandising and general ledger) that both reported
    Inventory value. Unfortunately the values could be up to $200,000
    different in any given month. Neither the direction of difference nor the
    magnitude were consistent month-to-month. For a $30M company, this was a
    very significant problem. The problem vanished when they installed a new
    integrated system that handled all of the business requirements.

    2) Consistent accuracy of data. Frequently there is a small, but
    non-negligible error rate when data is re-entered into multiple systems.
    This also frequently leads to significant staff time put into
    reconciliation activity.

    3) Faster flow of information. Electrons flow faster than paper, and
    modern ERP systems provide organizations with the capability of managing
    larger information flows in a much more efficient and effective fashion.

    4) Automation of manual processes. One client I called on recently tried
    to manage a 17-site company through faxing PO's, Invoices, and other
    documents all over the place. The result was that they needed 2-3 clerks
    at each site simply to shuffle the paper!

    I could go on for a while, but, in the interests of brevity, will simply
    state that, like any organizational change initiative, technological change
    can be done right or it can be done wrong. The ones that are done wrong
    end up sitting on a shelf somewhere -- with lots of press! The ones that
    are successful get less public visibility. (My experience has been similar
    in relationship to more general management consulting.)

    Steve

    =================================
    PRAGMATEK Consulting Group, Ltd.
    Web: www.PRAGMATEK.com
    Email: Steve.Harper@pragmatek.com
    -----------------------------------------------------------------
    "Many are stubborn in pursuit of the path
    they have chosen, few in pursuit of the goal."
    -- Friedrich Nietzsche
    ================================


    -----Original Message-----
    From: Jack Ring [SMTP:jring@AMUG.ORG]
    Sent: Friday, February 25, 2000 9:33 AM
    To: MG-ED-DV@MAELSTROM.STJOHNS.EDU
    Subject: Re: Technology-driven change

    Rule 1. WIFM. What's In It For ME? People will accept the pain of
    transitioning to a new situation when they see the new situtation (not the
    transitioning) has something in it for them.
    Rule 2. Transition requires learning. People learn fastest from someone
    who has direct influence over their future.

    In the example cited by Dick Montgomery, the people learned directly from
    the CEO (fast). And they learned a new pattern to which to conform. Being
    already trained conformists, this was not too much of a transition.
    Turning them into non-conformists would have taken lots more time.
    Apparently, however, the new pattern smelled like freedom and the smell of
    freedom is unmistakable. It remains to be seen how long it took (or takes)
    for them to learn that "freedom from" is not the real freedom and how well
    they leverage "freedom to.".

    Now the bad news.
    There is little demonstratable benefit in ERP but there is a decade of
    horror strories from those who have undergone such trauma.
    Be careful to discern whether you are talking technology in general or
    talking specific, perhaps even toxic, forms of technology.


    On Thu, 24 Feb 2000 Steve Harper wrote RE: public sector organizations --
    and/or our expectations?
    [...]
    >I would like to pose the following questions to the list:
    >
    >1) In times of rapid technological change, what, if anything, can external
    >people (consultants) do to help organizations prepare for and absorb that
    >change? [...]
    >
    >2) What types of education and training can future managers (both
    technical
    >and non-technical) be provided that would help in this process? [...]
    >
    >3) Is there/should there be a role for "change management" consultants
    >(OD?) in technical consulting organizations [...]?
    >
    >I am interested in the academic, practitioner, and consulting perspectives
    >on these questions. Replies will be most welcome.

    Jack Ring, 32712 N. 70th St., Snottsdale, AZ 85262-7143
    480-488-4615, Cell) 602.369.4615
    A system must be designed not for the existing situation but for the
    situation that will exist after the system is activated.


  • 3.  Technology-driven change

    Posted 02-25-2000 17:46
    Colleagues,

    Steve Harper asks if there is room for change management in consulting.
    Here are results of studies I've done:

    Change is the single most important factor in business today.
    ? Every business is an ongoing source of change.
    ? Every professional discipline is a process of change.
    ? Every fundamental business principle directs us to change.
    ? Every market force (customers, competitors, technology,
    regulations, distribution channels, suppliers, allies, subsidiaries,
    corporate parents, and more) creates change that forces
    our change in response.
    ? Globalization of markets demands globalization of businesses.

    We are all agents of change.
    ? Change-agent skills are as important to our success
    as are our professional discipline skills.
    ? The purpose of our jobs is to change what is possible,
    as companies and as individuals, by adding value every day.

    To answer your questions directly,

    1. Every consultant is an agent of change. That is our job. As agents of
    change, we need to balance the technical side (new equipment) with the
    skills side (technical training) and the emotional side (overcoming
    resistance to change). That's our job.

    2. Change is the single most sought after subject when hiring professional
    speakers. There is lots of room for specialists in change management.

    3. I've redefined my marketing consulting as "strategic change leadership".
    I use the same tools, but keep much more focused on real client needs. They
    don't need new brochures. They do need faster, more effective market
    penetration.
    By thinking of myself as a change leader, I work better with their
    business leaders.
    By working at strategic levels, I become a more powerful strategy for
    achieving their goals. (Yes, consultants are strategies used by clients to
    achieve desired results.)

    Steve, you are beginning a transition that will separate you from your
    peers. I may miss the precise pattern of growth, but I suspect your path
    will be something like:
    Engineer (technology focus)
    Consultant (tactical service focus)
    Change agent (strategic service focus)
    Corporate Leader (strategic leadership focus)
    Visionary (inspirational focus)

    Enjoy your trip. It's all about change. Most people never know the
    options.

    Gary
    ----------------------------
    Dr. Gary Lundquist -- The Scientist-Marketer
    Author of: TECHNOLOGY AND THE AGENTS OF CHANGE
    The power of marketing to change companies and change lives
    Garyl@market-engineering.com
    Market Engineering International, Inc.
    The Bridge Between Science and Marketing
    www.market-engineering.com
    303-840-9929, FAX: 303-841-6636
    12006 N. Antelope Trail, Parker, CO 80138, USA


  • 4.  Technology-driven change

    Posted 02-25-2000 18:28
    I second Gary's perspective that consulting is about change. It is
    something I tell me clients up front. I consult in the area of leadership
    development and planning. It is all about change. If fact, if they don't
    want to change, they will change...change for the worse. So if you can
    master change management, then you have a real beneficial set of skills and
    knowledge to provide clients. Another way you can discuss change is as
    transformation... from what to what is a place to begin...but begin they
    must.

    Ed Brenegar
    Community of Leadership, Inc.
    Hendersonville, NC

    ----- Original Message -----
    From: Dr. Gary Lundquist <garyl@MARKET-ENGINEERING.COM>
    To: <MG-ED-DV@MAELSTROM.STJOHNS.EDU>
    Sent: Friday, February 25, 2000 5:45 PM
    Subject: Re: Technology-driven change


    > Colleagues,
    >
    > Steve Harper asks if there is room for change management in consulting.
    > Here are results of studies I've done:
    >
    > Change is the single most important factor in business today.
    > ? Every business is an ongoing source of change.
    > ? Every professional discipline is a process of change.
    > ? Every fundamental business principle directs us to change.
    > ? Every market force (customers, competitors, technology,
    > regulations, distribution channels, suppliers, allies,
    subsidiaries,
    > corporate parents, and more) creates change that forces
    > our change in response.
    > ? Globalization of markets demands globalization of businesses.
    >
    > We are all agents of change.
    > ? Change-agent skills are as important to our success
    > as are our professional discipline skills.
    > ? The purpose of our jobs is to change what is possible,
    > as companies and as individuals, by adding value every day.
    >
    > To answer your questions directly,
    >
    > 1. Every consultant is an agent of change. That is our job. As agents
    of
    > change, we need to balance the technical side (new equipment) with the
    > skills side (technical training) and the emotional side (overcoming
    > resistance to change). That's our job.
    >
    > 2. Change is the single most sought after subject when hiring
    professional
    > speakers. There is lots of room for specialists in change management.
    >
    > 3. I've redefined my marketing consulting as "strategic change
    leadership".
    > I use the same tools, but keep much more focused on real client needs.
    They
    > don't need new brochures. They do need faster, more effective market
    > penetration.
    > By thinking of myself as a change leader, I work better with their
    > business leaders.
    > By working at strategic levels, I become a more powerful strategy for
    > achieving their goals. (Yes, consultants are strategies used by clients
    to
    > achieve desired results.)
    >
    > Steve, you are beginning a transition that will separate you from your
    > peers. I may miss the precise pattern of growth, but I suspect your path
    > will be something like:
    > Engineer (technology focus)
    > Consultant (tactical service focus)
    > Change agent (strategic service focus)
    > Corporate Leader (strategic leadership focus)
    > Visionary (inspirational focus)
    >
    > Enjoy your trip. It's all about change. Most people never know the
    > options.
    >
    > Gary
    > ----------------------------
    > Dr. Gary Lundquist -- The Scientist-Marketer
    > Author of: TECHNOLOGY AND THE AGENTS OF CHANGE
    > The power of marketing to change companies and change lives
    > Garyl@market-engineering.com
    > Market Engineering International, Inc.
    > The Bridge Between Science and Marketing
    > www.market-engineering.com
    > 303-840-9929, FAX: 303-841-6636
    > 12006 N. Antelope Trail, Parker, CO 80138, USA
    >


  • 5.  Technology-driven change

    Posted 02-25-2000 21:52
    I am working on a "transformation" team that has me wondering ... and I'd
    appreciate some outside thoughts. Your description of the consultant as the
    tactical service focus might be alongs the lines of what I am thinking.

    The project is designed to take the current environment and "transform" the
    organization to the common operating environment that is supposed (I'll
    debate this) to be a global "best practice."

    My issue is that as I do discovery of current "as is" processes I am finding
    what I suspect are local "best practices" that I would hate to lose by
    imposing a global process.

    So, are common operating environments technological/tactical .. but not
    strategic (as I think Nolan suggests in his 1979 study).

    ----- Original Message -----
    From: "Dr. Gary Lundquist" <garyl@MARKET-ENGINEERING.COM>
    To: <MG-ED-DV@MAELSTROM.STJOHNS.EDU>
    Sent: Friday, February 25, 2000 2:45 PM
    Subject: Re: Technology-driven change


    > Colleagues,
    >
    > Steve Harper asks if there is room for change management in consulting.
    > Here are results of studies I've done:
    >
    > Change is the single most important factor in business today.
    > ? Every business is an ongoing source of change.
    > ? Every professional discipline is a process of change.
    > ? Every fundamental business principle directs us to change.
    > ? Every market force (customers, competitors, technology,
    > regulations, distribution channels, suppliers, allies,
    subsidiaries,
    > corporate parents, and more) creates change that forces
    > our change in response.
    > ? Globalization of markets demands globalization of businesses.
    >
    > We are all agents of change.
    > ? Change-agent skills are as important to our success
    > as are our professional discipline skills.
    > ? The purpose of our jobs is to change what is possible,
    > as companies and as individuals, by adding value every day.
    >
    > To answer your questions directly,
    >
    > 1. Every consultant is an agent of change. That is our job. As agents
    of
    > change, we need to balance the technical side (new equipment) with the
    > skills side (technical training) and the emotional side (overcoming
    > resistance to change). That's our job.
    >
    > 2. Change is the single most sought after subject when hiring
    professional
    > speakers. There is lots of room for specialists in change management.
    >
    > 3. I've redefined my marketing consulting as "strategic change
    leadership".
    > I use the same tools, but keep much more focused on real client needs.
    They
    > don't need new brochures. They do need faster, more effective market
    > penetration.
    > By thinking of myself as a change leader, I work better with their
    > business leaders.
    > By working at strategic levels, I become a more powerful strategy for
    > achieving their goals. (Yes, consultants are strategies used by clients
    to
    > achieve desired results.)
    >
    > Steve, you are beginning a transition that will separate you from your
    > peers. I may miss the precise pattern of growth, but I suspect your path
    > will be something like:
    > Engineer (technology focus)
    > Consultant (tactical service focus)
    > Change agent (strategic service focus)
    > Corporate Leader (strategic leadership focus)
    > Visionary (inspirational focus)
    >
    > Enjoy your trip. It's all about change. Most people never know the
    > options.
    >
    > Gary
    > ----------------------------
    > Dr. Gary Lundquist -- The Scientist-Marketer
    > Author of: TECHNOLOGY AND THE AGENTS OF CHANGE
    > The power of marketing to change companies and change lives
    > Garyl@market-engineering.com
    > Market Engineering International, Inc.
    > The Bridge Between Science and Marketing
    > www.market-engineering.com
    > 303-840-9929, FAX: 303-841-6636
    > 12006 N. Antelope Trail, Parker, CO 80138, USA
    >


  • 6.  Technology-driven change

    Posted 02-26-2000 08:24
    Re the thread started by Steve Harper's inquiry about change management and
    including Jack Ring's somewhat acerbic comment about ERP in general (which
    was raised by Steve).

    We are in the midst of a PeopleSoft introduction at my "day job" as I call
    it (I'm an executive director at Educational Testing Service). Please know
    that I have no intention of airing any dirty laundry in that area, however,
    Steve's inquiry and Jack's comments do bring to mind some observations I've
    made over the years about the many ways in which the introduction of
    technology-driven changes go awry. Many of them can be summed up in a
    single statement: "Failure to lay the groundwork."

    Nowhere is this more glaringly apparent than in ERP installations. "My
    way or the highway" comes immediately to mind. I can't think of a tactic
    more likely to raise resentment and encourage hostility than a complete
    disregard for the interests and concerns of the users. Yet, ERP
    installations seem marked by exactly that kind of dismissive treatment of
    the users. It might indeed be the case that ERP packages are fixed and
    immutable in both form and function but that's no excuse for failing to
    consult with the users and to do so in a way that guarantees that their
    concerns are heard and addressed (even if addressing them doesn't entail
    modifying the ERP package).

    The foundation for a successful change is a receptive audience. A
    high-handed approach blows up in the faces of those who use it when things
    don't go well (and they almost never go smoothly). Instead of being
    greeted with understanding and tolerance, the slightest misstep is seized
    upon as evidence that the whole change effort was a mistake. Howls of
    derision and glee can be heard in the wings. The system being introduced
    will be subjected to a never-ending string of criticisms and
    complaints. Wait long enough and some enterprising corporate politician
    will see an opportunity and the offending system will be targeted for
    replacement with another. Sadly, the same mistakes made in introducing the
    first system will likely be repeated in the course of introducing this one.

    I used to be involved quite regularly with system introductions and spent
    a lot of time thinking about the following kinds of questions:

    Who are the user communities?
    Where are they? (Physically and organizationally)
    How are they organized?
    Who are their leaders?
    Who are the quiet influencers?
    What are their concerns?
    What is their power base?
    How can we enlist their support?
    How can we involve them in truly meaningful ways?
    How do we keep them in the loop?
    How will missteps be handled?

    I'm sure others on the list can add questions of equal or greater utility.

    There is a human side to system introductions yet it rarely gets
    addressed. Consequently, the very people who should care most about the
    new system don't care about it at all -- except as an object of scorn or
    ridicule. And the high costs of a people-centric introduction get shifted
    to the post-introduction area where, I suspect, they are greater than if
    they had been properly tended to up front.

    All this, I suspect, is a rather longish way of saying that, in most system
    introductions, the system is the center of attention. The people take a
    back seat. I think that's the wrong way to go. The center of attention
    during introduction should be the organizational units and processes the
    system will impact and the people who populate those units and
    processes. Once it has been successfully installed the system can become
    the center of attention.
    Fred Nickols
    The Distance Consulting Company
    "Assistance at A Distance"
    http://home.att.net/~nickols/distance.htm
    nickols@worldnet.att.net
    (609) 490-0095


  • 7.  Technology-driven change

    Posted 02-26-2000 09:51
    I would only add to Fred's valuable check list the continuing fear that IS
    installations have raised since the "punch card" days--the fear of
    substitution. The reality that information technology can perform
    many of the functions of the incumbent faster and more accurately
    clouds the opportunity for individuals to focus on their personal value to
    the organization.

    This is very evident in the slow pace of faculty to leverage Internet
    resources to enhance their course delivery. The mythology that "distance
    learning" will replace bricks and mortar continues to inhibit
    the use of these rich resources. Fred's check list would be invaluable for
    college administrators frustrated by faculty resistance to IT.

    Chuck Morrissey
    Pepperdine


  • 8.  Technology-driven change

    Posted 02-26-2000 10:37
    > Fred's check list would be invaluable for
    >college administrators frustrated by faculty resistance to IT.

    Faculty resistance?

    1. The local IT dept. at my university refuses to allow faculty to put their
    notes on the Web for fear of ???

    2. Some of the students here (and at other universities where I've taught)
    say they paid good money to see faculty in person, and, while some find the
    web resources helpful, many prefer to sit and have the material presented to
    them by a live faculty member. At one of the most wired universities, in an
    experiment with streaming technology, students preferred the in-class
    lectures to be presented with chalk, as well as being taped and made
    available on the Web.

    The second problem does not preclude faculty from making both resources
    available to students; however, the first one does.

    Interestingly, the administration here says that they want faculty to move
    to the Web, and blame the faculty for not doing so, in spite of the fact
    that it is the IT resistance that limits the move.


  • 9.  Technology-driven change

    Posted 02-26-2000 11:26
    Colleagues,

    Fred Nickols said: "The foundation for a successful change is a receptive
    audience."

    Right on.

    Let me introduce a bit of language: We can be self-centered, or customer
    centered. The ERP installers Fred mentions are acting self centered. They
    seem to believe that ERP is the important thing. Wrong.

    ERP is just a tool. An expensive, complex tool. The real issue is how the
    company works, and the company still works around people.

    Using Fred's questions helps develop a customer center. All of my
    consulting is based on questions, because asking and answering those
    questions forces me and my clients to see the world from a customer
    viewpoint.

    I lost a great software company in 1989 because we thought the software was
    the important thing. Our true job was to empower our customers to make
    better decisions. We went out selling software, not the benefits of better
    decisions. Toward the end, we began asking the right questions, but it was
    too little, too late. We couldn't turn around the company culture fast
    enough.

    Take a good look at Fred's questions and add your own.
    Who are the user communities?
    Where are they? (Physically and organizationally)
    How are they organized?
    Who are their leaders?
    Who are the quiet influencers?
    What are their concerns?
    What is their power base?
    How can we enlist their support?
    How can we involve them in truly meaningful ways?
    How do we keep them in the loop?
    How will missteps be handled?

    If you want to know some of my questions, I'll send you an article. (Please
    make these requests off the listserv.)

    Gary
    ----------------------------
    Dr. Gary Lundquist -- The Scientist-Marketer
    Author of: TECHNOLOGY AND THE AGENTS OF CHANGE
    The power of marketing to change companies and change lives
    Garyl@market-engineering.com
    Market Engineering International, Inc.
    The Bridge Between Science and Marketing
    www.market-engineering.com
    303-840-9929, FAX: 303-841-6636
    12006 N. Antelope Trail, Parker, CO 80138, USA


  • 10.  Technology-driven change

    Posted 02-26-2000 14:48
    And, what would be for you the ideal model of training leaders, encompassing
    technology?

    Sylvie

    On Sat, 26 Feb 2000, Michael Wolfe wrote:

    > > Fred's check list would be invaluable for
    > >college administrators frustrated by faculty resistance to IT.
    >
    > Faculty resistance?
    >
    > 1. The local IT dept. at my university refuses to allow faculty to put their
    > notes on the Web for fear of ???
    >
    > 2. Some of the students here (and at other universities where I've taught)
    > say they paid good money to see faculty in person, and, while some find the
    > web resources helpful, many prefer to sit and have the material presented to
    > them by a live faculty member. At one of the most wired universities, in an
    > experiment with streaming technology, students preferred the in-class
    > lectures to be presented with chalk, as well as being taped and made
    > available on the Web.
    >
    > The second problem does not preclude faculty from making both resources
    > available to students; however, the first one does.
    >
    > Interestingly, the administration here says that they want faculty to move
    > to the Web, and blame the faculty for not doing so, in spite of the fact
    > that it is the IT resistance that limits the move.
    >


  • 11.  Technology-driven change

    Posted 02-26-2000 14:51
    Here here! and a well said, too!

    I am facing an ERP introduction and once again I am reminded that people use
    tools....

    The ERP community seems to think that the tool uses the people and the tool
    (and its processes) should drive the change. I saw this dramatically
    presented at the Academy of Management in Chicago at an OCIS presentation on
    ERP that had all the requirements and choices done very early and at the
    corporate level ... not a single user or even user manager with input as to
    what the system would need to be able to do. The model called for the
    alienation of the users as an anticipated step in the program!!

    In my student's reports on ERP in their businesses I hear it over and over
    again. Projects that don't work because no one ever bothered to find out
    what the people who really do the work really needed in a product. Whole
    payroll systems outsourced, because the ERP product couldn't handle the
    special commission needs of this industry. Millions spent after the fact
    "fixing" what didn't work in the ERP.

    Conna Condon
    PC Specialists
    DBA Candidate Nova SEU.


    ----- Original Message -----
    From: "Fred Nickols" <nickols@WORLDNET.ATT.NET>
    To: <MG-ED-DV@MAELSTROM.STJOHNS.EDU>
    Sent: Saturday, February 26, 2000 5:24 AM
    Subject: Re: Technology-driven change


    > Re the thread started by Steve Harper's inquiry about change management
    and
    > including Jack Ring's somewhat acerbic comment about ERP in general (which
    > was raised by Steve).
    >
    > We are in the midst of a PeopleSoft introduction at my "day job" as I call
    > it (I'm an executive director at Educational Testing Service). Please
    know
    > that I have no intention of airing any dirty laundry in that area,
    however,
    > Steve's inquiry and Jack's comments do bring to mind some observations
    I've
    > made over the years about the many ways in which the introduction of
    > technology-driven changes go awry. Many of them can be summed up in a
    > single statement: "Failure to lay the groundwork."
    >
    > Nowhere is this more glaringly apparent than in ERP installations. "My
    > way or the highway" comes immediately to mind. I can't think of a tactic
    > more likely to raise resentment and encourage hostility than a complete
    > disregard for the interests and concerns of the users. Yet, ERP
    > installations seem marked by exactly that kind of dismissive treatment of
    > the users. It might indeed be the case that ERP packages are fixed and
    > immutable in both form and function but that's no excuse for failing to
    > consult with the users and to do so in a way that guarantees that their
    > concerns are heard and addressed (even if addressing them doesn't entail
    > modifying the ERP package).
    >
    > The foundation for a successful change is a receptive audience. A
    > high-handed approach blows up in the faces of those who use it when things
    > don't go well (and they almost never go smoothly). Instead of being
    > greeted with understanding and tolerance, the slightest misstep is seized
    > upon as evidence that the whole change effort was a mistake. Howls of
    > derision and glee can be heard in the wings. The system being introduced
    > will be subjected to a never-ending string of criticisms and
    > complaints. Wait long enough and some enterprising corporate politician
    > will see an opportunity and the offending system will be targeted for
    > replacement with another. Sadly, the same mistakes made in introducing
    the
    > first system will likely be repeated in the course of introducing this
    one.
    >
    > I used to be involved quite regularly with system introductions and spent
    > a lot of time thinking about the following kinds of questions:
    >
    > Who are the user communities?
    > Where are they? (Physically and organizationally)
    > How are they organized?
    > Who are their leaders?
    > Who are the quiet influencers?
    > What are their concerns?
    > What is their power base?
    > How can we enlist their support?
    > How can we involve them in truly meaningful ways?
    > How do we keep them in the loop?
    > How will missteps be handled?
    >
    > I'm sure others on the list can add questions of equal or greater utility.
    >
    > There is a human side to system introductions yet it rarely gets
    > addressed. Consequently, the very people who should care most about the
    > new system don't care about it at all -- except as an object of scorn or
    > ridicule. And the high costs of a people-centric introduction get shifted
    > to the post-introduction area where, I suspect, they are greater than if
    > they had been properly tended to up front.
    >
    > All this, I suspect, is a rather longish way of saying that, in most
    system
    > introductions, the system is the center of attention. The people take a
    > back seat. I think that's the wrong way to go. The center of attention
    > during introduction should be the organizational units and processes the
    > system will impact and the people who populate those units and
    > processes. Once it has been successfully installed the system can become
    > the center of attention.
    > Fred Nickols
    > The Distance Consulting Company
    > "Assistance at A Distance"
    > http://home.att.net/~nickols/distance.htm
    > nickols@worldnet.att.net
    > (609) 490-0095
    >


  • 12.  Technology-driven change

    Posted 02-26-2000 16:52
    I agree with many of the comments made concerning ERP. The forced
    introduction of new systems based on the perceived needs (or ego) of the
    "leadership" is a recipe for ensured disaster! Fred's summation that many
    of the problems start from "Failure to lay the groundwork." is certainly
    true. In my experience I have found that some of the key groundwork
    questions that companies undertaking ERP fail to ask are:

    1) What are the business strategies we are trying to support? Are they
    supportable through new technology? Do we even have a defined set of
    strategies?
    2) What are the business problems we are trying to solve? Are they
    strategic, tactical, or operational? (The different levels require
    different solutions -- both managerial and technological.)
    3) If the problems are operational, have we worked with the front-line
    people to solve them within our current technological framework?
    (Unexploited functionality of current systems is a BIG problem in many
    organizations.)
    4) Have the front-line people and first level managers (the primary user
    community) been intimately involved in defining requirements?

    Frequently large-scale ERP projects are undertaken "because that is what
    everyone is doing" rather than through a careful analysis and understanding
    of the true business needs of the organization. The result is that the
    implementation fails because it quickly reveals the lack of adequate
    groundwork.

    Steve

    =================================
    PRAGMATEK Consulting Group, Ltd.
    Web: www.PRAGMATEK.com
    Email: Steve.Harper@pragmatek.com
    -----------------------------------------------------------------
    "Many are stubborn in pursuit of the path
    they have chosen, few in pursuit of the goal."
    -- Friedrich Nietzsche
    ================================


  • 13.  Technology-driven change

    Posted 02-27-2000 01:15
    As I listen to CEO's and Capital Q Quality people talk about 'best
    practices,' I hear a disturbing sense coming through. It sounds as if
    'best practices' is something we can locate, go out, study, buy, and put
    into our own operation, like a new engine in a car.

    We all know that what works in Japan may or may not (usually not) work
    in the USA. The society culture & corporate culture are different. But
    what works well for L. L. Bean, may not work for General Hardware Sales
    in Oshkosh. Certainly, I wouldn't bet on it.

    What constitutes best practices, it seems to me, often includes some
    strong intangibles. Call it corporate culture or what you like. People
    who advocate adoption of best practices, do they identify these
    intangibles and include them in the implementation in the other
    companies? Do we also get the correct bolts and engine oil for the new
    engine we are going to put into our car? Do they bring along the
    details of how the driver presses the gas pedal?

    If Ms. Condon can see some valuable parts of her company system, and
    these parts do not damage something else, are they not valuable in
    themselves? Maybe more so than a foreign 'best practices'? But to
    recognize and retain them is going to take more thinking than grafting
    something else into place.

    Jay

    Conna Condon wrote:

    > I am working on a "transformation" team that has me wondering ... and
    > I'd
    > appreciate some outside thoughts. Your description of the consultant
    > as the
    > tactical service focus might be alongs the lines of what I am
    > thinking.
    >
    > The project is designed to take the current environment and
    > "transform" the
    > organization to the common operating environment that is supposed
    > (I'll
    > debate this) to be a global "best practice."
    >
    > My issue is that as I do discovery of current "as is" processes I am
    > finding
    > what I suspect are local "best practices" that I would hate to lose by
    >
    > imposing a global process.
    >
    > So, are common operating environments technological/tactical .. but
    > not
    > strategic (as I think Nolan suggests in his 1979 study).
    >
    > [snip]


    --
    Jay Warner
    Principal Scientist
    Warner Consulting, Inc.
    4444 North Green Bay Road
    Racine, WI 53404-1216
    USA

    Ph: (262) 634-9100
    FAX: (262) 681-1133
    email: quality@a2q.com
    web: http://www.a2q.com

    The A2Q Method (tm). What do you want to improve today?


  • 14.  Technology-driven change

    Posted 02-28-2000 01:36
    Great post, Jay. I completely agree.

    On 27 Feb 00, at 0:15, Jay Warner wrote:

    > What constitutes best practices, it seems to me, often includes some
    > strong intangibles. Call it corporate culture or what you like. People
    > who advocate adoption of best practices, do they identify these
    > intangibles and include them in the implementation in the other companies?
    > Do we also get the correct bolts and engine oil for the new engine we are
    > going to put into our car? Do they bring along the details of how the
    > driver presses the gas pedal?

    I think you have this dead on, and it's also one reason why
    management "fads" come and go. My primary field is performance
    management, and as an author of a book on the subject, I get to
    attend conferences on the topic, all of which include presenters
    from major companies talking about their best practice successes.

    But the problem is they only supply what is a very superficial set of
    information about their context. The truth is we don't KNOW where
    to look for all the intangibles, and they aren't reported.

    So, the audience sits there, hears all kinds of success claims
    (which may or may not be accurate), then collectively nod their
    heads as if they have been handed the new scrolls.

    Then they go out and fail.

    One of the things I try to get across in my area is that a good
    manager will make almost any performance management system
    work, not matter how bad. A poor manager will not be able to get
    the best possible performance management system to work.

    What does that say about the best practices in performance
    management? It says they mean little. Now, if we all got a chance
    to hang out for a few months and watch the successful managers
    work (and knew what to look for), we would indeed find the
    intangibles.

    But most presenters of best practices don't invite everyone down to
    visit for a few months!


    Visit the work911.com supersite at http://www.work911.com
    for work related articles, or to find almost anything including
    book reviews and suggestions, discussion lists and more.