User Adoption Insights From Tri Tuns

User Adoption Insight Over Margaritas


This far into spring many Seattleites are more than ready for the first glimpses of that odd, warmish bright thing in the sky. When I lived back east we called it “the sun”. But sometimes, like this last Tuesday, we have to pretend and somehow manufacture our own sunshine.

Which is how a group of friends and I found ourselves at our neighborhood’s most brightly painted Mexican place. It was with near-salivating anticipation for our dry, near-perfect summers we ordered our pitcher of margaritas. Or…ok, maybe it had just been a long day for each of us.

Being the most technically-inclined person of the group – to the extent that I’m the only one with an iPod even – I try to be the one who kicks off our usual how-was-your-day round-robin with the briefest description of what I did, just to get my IT-related day behind us so we can talk about things that are common to the whole group. That day, I’d designed a Power Point presentation for an upcoming conference on user adoption in the cloud. When the conversation turned to the cloud my dear friend Jane, an office manager, recalled how just hours before her bosses sprung a new cloud-based Power Point-like software on her, telling her their whole organization was moving to it and she needed to learn it. Oh, and while she’s at it, convert all the other slide decks their office regularly uses too.

“It seems to me we’re always upgrading or switching to something totally new and the technology changes so fast, no one can keep up.  It’s like technology’s moving so fast, we’re just running along behind doing our best to catch up, but we can’t. None of us can. It just moves that fast and changes that often. It’s not the technology’s fault. It’s just that as humans, we can’t change as fast as it does.”

Despite my best efforts, I couldn’t help but grin over my salted rim and say, “Precisely. And that’s where user adoption consulting comes in. We’re the ones you bring in to help you navigate through all those changes, with all those personalities and competing interests, and we set you up for the long-term. Because you know it’s going to change again. ”

Curt, a school counselor, looked at me and said, “So…it’s not the technology. It actually has nothing to do with the technology…it’s all about the people…and how they manage and get through the change, as individuals, as departments, as whole organizations.”

And it was like the sun came out right there at the table: the heretofore somewhat abstract notion of “user adoption” finally made sense to everyone at the table. Here was a real-life example they each could relate to; they’d heard it from someone going through it and heads nodded in recognition.

So while this last Tuesday afternoon didn’t set records for instant sunlight over Seattle, having my friends see a real-world example of what I do on a daily basis was definitely something to toast to.

Quick Subcribe:  User Adoption Quick Tips & Insights Newsletter

Get even more User Adoption tips & insights sent to your email.

        

 Insights Newsletter                                         User Adoption Quick Tips 


‘Set It and Forget It’ is a Recipe for IT Disaster


IF ONLY IT IMPLEMENTATIONS WERE JUST THIS EASY

In the days of yore, Ron Popeil, infomercial pioneer, made it look easy.

He invented a kitchen gadget to make our lives easier, and the only direction he gave was ‘set it and forget it’. One step to make a “delicious six lb. chicken!” or “not one but two delicious rotisserie chickens!” How much simpler is that than the way our moms and grandmothers cooked chicken?

If only the rest of life were that easy.

Especially new software systems.

In an ideal world, your IT team would come in, install the new software, and it would be such an great experience they’d just magically sit down and start using not only because it’s easy to use but because they want to use it. This scenario is as likely to fool the seasoned implementation manager about as well as Hair in a Can spray dispelled notions of impending baldness.

So what are you to do when – as typically happens – you introduce a new system, everyone’s excited at launch time and then several weeks (years) later you look at the usage statistics and you’re disappointed. What happened? Looks like you set it and forget it.

But people were trained, you say. We worked for months to convince them this change was a good thing, you insist. They were even kind of excited, you protest. On top of that, they’d had no choice but to use this new system and things still aren’t working out as you’d hoped. Now what?

CONSIDER THIS

Fundamentally, IT systems and user adoption are not set it and forget it kind of things.

Typically IT implementations follow a simple formula: go-live and go home. But the users don’t go home and they are what makes -- or breaks -- any IT investment.

In today’s world everyone needs to maximize the ROI of any IT investment, and the only way to realize that ROI is by holistically taking care of the people who use it.

It’s not traditional thinking but after go-live, users need constant care and feeding, no matter the system, no matter the type of implementation, no matter the organization. 

So what do you do? You need to do something, you know this. But what?

    1. Assess the situation for your user

    2. Develop a plan accordingly

    3. Assign someone responsibility for executing that plan

    4. Create the infrastructure so that person, and the plan – and your users – will succeed

The fact of the matter is, an IT implementation doesn’t end at go-live, but rather it begins there. The world –inside your organization and with your competitors’-- is constantly changing. People will always need new and different information, there will always be turnover, and you will need specific people focused on getting the value you need from this investment. Only when people use the technology will you get the value you want.

WHAT IT MEANS FOR YOU

‘Set it and forget it’ is how implementations used to be delivered. But the world has changed. These days you need to build a flexible, scalable and sustainable user adoption strategy before you implement your system. You need to map out the necessary efforts and actions your organization will take so it can extract the maximum business value from your investment. Comparatively, the technology side is easy; it’s all 1s and 0s and it does what you tell it to do. It’s the human element that complicates matters and requires you to focus more on the people and the organization than on the technology and the tools.

THINGS TO THINK ABOUT

  • How do you do implementations? Do you typically take a holistic approach, or do you set it and forget it? What have you experienced?

  • Whose job is it to make sure this happens? Do they have the skills?

  • Do you have the organizational capacity and willingness to carry out a sustainable user-focused program?

  • Does your internal team have the skills and experience to address these issues?

  • Do you have the infrastructure to achieve this in a fast, flexible and affordable way?

And if you’re not sure how your project may be affected take the challenge. After all, saying they have no choice but to use it is ultimately counter-productive when you have the choice to be proactively motivating people to use it.

RELATED RESOURCES

  • Schedule a demo of Tri Tuns' "My User Adoption Plan" portal to see how it can provide a comprehensive infrastructure for ensuring effective stakeholder engagement & communications over the life of your system.

TELL US WHAT YOU THINK

Was this information helpful?  What did you learn?  We want to hear from you - please add a comment below.

Quick Subcribe:  User Adoption Quick Tips & Insights Newsletter

Get even more User Adoption tips & insights sent to your email.

        

 Insights Newsletter                                         User Adoption Quick Tips 


Don’t sell your employees on the system. Fulfill their needs!


OBSERVATION

A common practice – and TRAP – of change management is to attempt to convince (“sell”) end-users that the new IT system is beneficial to them.  Change management teams spend several hours trying to “spin” their communications to attain this goal. The fallacy is spending time “selling” the benefits of the system without first understanding the end-users’ actual needs to properly use the system.  This pitfall is grossly overlooked.

CONSIDER THIS

Change management teams often defend their approach, stating they apply due diligence by defining technical requirements.  The problem is the technical requirements assume alignment to the daily practices of end-users.  Often we find the architectural design does not compliment the practical application. As a different approach, User Adoption strategy consultants capture the most effective means of utilizing the system through interviews and observation of end-user behavior; this is done in concert with requirements definitions.  The goal is not to ignore technical requirements, but to ensure the system technical requirements actually meet the end-user needs. This user adoption approach prevents the temptation to “sell” benefits to end-users, because their needs have already been identified and properly met.

THINGS TO THINK ABOUT

When you are about to develop a new IT system, seek out the actual needs (both business and technical) of your end-users.  Then you will spend less time “selling” end-users, and more time satisfying their needs.

RELATED RESOURCES

Check out these other resources for more information related to this topic:
Quick Subcribe:  User Adoption Quick Tips & Insights Newsletter

Get even more User Adoption tips & insights sent to your email.

        

 Insights Newsletter                                         User Adoption Quick Tips 


Book it! Scheduling User Adoption activities is a must to ensure long-term IT success.


OBSERVATION

We have all experienced this:  a round of discussions generating wonderful ideas, with a promise to reconvene and determine next action items.  The problem is those action items rarely become a reality, because there was never a sufficient amount of follow-through to act on those ideas. We know that user adoption (UA) of IT systems does not occur without deliberate action items.  Since the goal is to conduct specific activities that encourage end-users to engage your IT system as designed, we need to move from mere discussions and ideas to committed actions that promote user adoption. In order to maintain both focus and follow-through of user adoption plans, it is recommended to reconstruct your project team meetings in a way that generates ideas and creates specific follow-up actions.

CONSIDER THIS

For each strategy phase of the user adoption (UA) plan (e.g. analysis, engagement, learning, support, etc.) create two separate meeting times and agendas:
  1. “Brainstorming Session”
  2. “Implementation Planning”
Brainstorming Session:
  • Ascertain and list the relevant topics for that phase of the UA plan (rely not only on the project plan and initial team discussions but also on your UA consultant/expert).
  • Organize each agenda topic in a logical sequence to create a seamless and singular focus throughout the session.
  • Place specific time limits for each discussion topic, and be realistic as to what can be accomplished, as brainstorming/discussions can take longer than expected.  Therefore do not attempt to overload the meeting agenda with too many topics. If needed, consider more than one brainstorming session vs. one long session.
  • During the brainstorming session, ALWAYS include the predicted impacts to user adoption of each idea.
  • Assign specific assignments to session participants with the due date set for the following meeting: “Implementation Planning”.  Typically, these assignments are data gathering/research in nature, which shall help the team determine the implementation plan.
Implementation Planning:
  • Revisit each discussion topic in the same sequence from the brainstorming session.
  • Address the findings from the various assignments in order to decide how to best proceed.  Again, validate each decision based on predicted impact to user adoption.
  • Agree to a specific series of implementation activities to enact your team’s decisions.  This must include primary ownership and enactors of activities, time-frames, resources required, leadership endorsement and support.

THINGS TO THINK ABOUT

As you plan for your next UA meetings, remember what the overarching goal is:  to enact specific actions that will create user adoption of your IT system.  Using the above steps can help you and your team follow-through on your user adoption ideas to create long lasting results.

RELATED RESOURCES

Check out these other resources for more information related to this topic:
Quick Subcribe:  User Adoption Quick Tips & Insights Newsletter

Get even more User Adoption tips & insights sent to your email.

        

 Insights Newsletter                                         User Adoption Quick Tips 


Design the right metrics to improve user adoption


OBSERVATION

Have you noticed that you spend a large amount of time documenting process flows but fail to measure their IT implementation? How do you know if the end-users are enacting the system as designed and contributing to the business goals? We know that process documentation is necessary to ultimately guide system end-users once an implementation is complete. However, many fail to realize that metrics need to be prepared to adequately determine if the new process flows are followed by system end-users. User Adoption metrics is the link between the new process design and the organizational change effort.

CONSIDER THIS

When determining which particular metrics to focus on, it is critical to consider user behaviors that both follow the new process design as well as behaviors that deviate from your intended process. Important user adoption metrics determine how much deviation there is between end-user behavior and the intended new process. Knowing these levels of deviation will help you determine how to influence and guide end-users toward the new process. The right metrics don’t necessarily need to be complex or sophisticated to provide accurate insight into the impact of current business processes (e.g. how long it takes to perform a particular process).

THINGS TO THINK ABOUT

Brainstorm both intended and unintended behaviors and outcomes during implementation in order to create the proper user adoption metrics. Here are some examples of insightful metrics: • How many resources touch a process from beginning to end? • List which resources touch that process. • What is the scope of the process activities performed by each resource? • Are there fewer or more resources (or handoffs) required due to automation? Remember, when planning user adoption metrics, determine what is valuable to know about a particular process. Metrics must be designed to ensure that the behavior of the new processes deliver the intended results. With proper metrics and planning, you will have the insight needed to reinforce desired behavior.

RELATED RESOURCES

Check out these other resources for more information related to this topic:

Quick Subcribe:  User Adoption Quick Tips & Insights Newsletter

Get even more User Adoption tips & insights sent to your email.

        

 Insights Newsletter                                         User Adoption Quick Tips 


What’s wrong with my questions? How IT projects typically fail to ask questions pertinent to long-term user adoption.


OBSERVATION

Does your IT implementation plan include a Change Management (CM) effort?  It probably does.  Does this CM effort include attaining information about the user community’s needs, in preparation for an IT build?  Again, your answer may typically be yes. So what could possibly be missing?  The answer lies in what you are not asking about your client.  Most often, consulting firms and IT implementation teams only seek information about the technical requirements to an IT build.  What they forget to determine are the organizational impacts and barriers to actually using the new IT system. Once the IT system is built and installed, it is a fallacy to assume the user community (system end-users) will adopt the new system fully and as designed (known as User Adoption).  Therefore is imperative to determine factors beyond technical requirements that can positively and negatively affect system usage.

CONSIDER THIS

Below are just a couple of example questions one may ask the user community, in order to determine both organizational impacts and barriers to using a new IT system:
  1. In addition to technical system training (e.g. classroom, reference guides), what other support mechanisms or skill set needs would help you operate the new IT system as designed (e.g. scenario process steps, vehicle for sharing best practices, etc.)?
  2. What support would you like to see your managers provide to assist you in delivering quality services regarding the use of the new IT system?
  3. Who will be responsible for the ongoing assessment and management of user adoption?  How will you adjust their current roles & responsibilities to handle the added role?

THINGS TO THINK ABOUT

As you plan to implement a new IT system, include assessments in your project plan that will address issues that will foster user adoption.  Identifying user adoption issues during the project will better prepare the user community for both initial go-live of the system as well as long-term system usage.

RELATED RESOURCES

Check out these other resources for more information related to this topic:
Quick Subcribe:  User Adoption Quick Tips & Insights Newsletter

Get even more User Adoption tips & insights sent to your email.

        

 Insights Newsletter                                         User Adoption Quick Tips 



Copyright © Tri Tuns, LLC 2011. All Rights Reserved.