Marion's Weblog
My name is Marion Vermazen. I worked at Sun Microsystems up until June 3, 2005. I worked on the IT aspects of Sun's work from anywhere program, iWork. I was also the team lead for the Java Desktop and Solaris 10 at Sun Change Acceptance team.

20041007 Thursday October 07, 2004

JDS Change Acceptance Lessons Learned - Part 2

In an earlier Blog entry I started to talk about the lessons I have learned from the project I am leading to build acceptance across Sun for the Java Desktop System. Tonight IT Operations will begin to install the JDS Preview on our SunRay servers. We are testing a few sites this week and next and then the following week we are planning to install it on SunRay servers world wide. That's thousands of desktops. CDE users will be impacted by the change when we change the default desktop to JDS Preview a few weeks after that.

Building acceptance for this change is a big project but we are making progress. Here are a few more of the things I have learned as we go through his process. The first 5 are described in my blog entry.

CAP Lessons Learned
  1. It is hard work
  2. It is about the conversation
  3. Don't assume that people understand the product and the details of the change
  4. Segment the user base
  5. Regular Change Acceptance Reviews are imperative.
  6. The work of change isn't about the tools. Just as using the tools in Norm Abram's workshop isn't the same as building a piece of furniture so using the powerful set of tools provided as a part of our Sun Change Acceptance Process isn't the same as doing the change work necessary to move people from resisters to active supporters. The kind of work we have been doing includes things like getting JDS Preview running in our Global Resolution Center, Meeting with Sys admins to understand their concerns about the change, and calling executives to make sure they know what is happening and are talking to their people about it.
  7. Understand the behavior you want. We are asking our users what category they consider themselves in. An active supporter is running JDS on their laptop and JDS preview on their SunRay, they are urging others to convert. A passive supporter agrees with JDS in principal but is skeptical about whether it will work for them. The neutral and negative categories are fairly self evident. It helped our team a lot to understand exactly what we were trying to achieve - We are trying to move people to active supporters . It also helps with getting people to change when we can tell them what we want them to do and ask them why they are not an active supporter.

    That is enough for today – More another day

    (2004-10-07 17:27:11.0) Permalink


archives
links
referers