User Adoption Insights From Tri Tuns

‘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 


Is Your IT Systems a Dreamliner?


The 787 SHOWS US THAT NEW TECHNOLOGY BRINGS NEW RISKS 


REPORTED

The Boeing 787 Dreamliner has been hailed as a revolutionary advance in technology that will provide the greatest advance in air travel since the Concorde.  The Dreamliner uses new materials and technology and promises to cut 15% off its weight, dramatically lowering fuel consumption and costs.  It’s obvious why airlines are salivating to get their hands on it.

However, like all new technologies, great advances come with great risks and lots of “unknowns”.   The Daily Mail cites a recent GAO report that states while the Dreamliner is safe, it has introduced new risks and even the inspectors don’t know how to manage the new technology or how the risks change over time.


“U.S. inspectors said they do not know what to look for when the new composite [plastic wings & fuselage] starts to fail. …The report said it is unclear how the 787 will become damaged over time and it is not known what the damage to the composite will look like.”

Daily mail, 03NOV11


NEW RISKS & YOUR IT SYSTEM

Can you image what will happen to Boeing if in a few years some problem is discovered with their new materials and/or design results in repeated 787 crashes?  Or if the new composite materials turn out to have a lifespan that is only half of that of traditional materials? Lawsuits could fly and demand could be wiped out overnight.   Do you think Boeing is going to monitor these risks and take action to mitigate them?  You bet they are. 

Just like with the Dreamliner, introducing new technology systems into your organization can provide revolutionary advances in capacity and benefits.  The problem is, it also introduces revolutionary advances in risks as well.  Unfortunately, many organizations get seduced by the potential benefits while ignoring the risks.  And they do so at their peril.  Are you going to make this mistake?


CONSIDER THIS

When implementing new IT systems, many organizations focus on getting the system live, but ignore what happens once it is in production.  The value of your system – and the risks – only get introduced after the system is live.  And they continue over the life of the system.  This means that you need to manage the value creation and risk mitigation over the life system.

  • The FAA inspectors said they don’t even know what to look for to identify emerging problems with their technology.  Will your staff know how to identify and manage the new risks (and opportunities) that your new IT system will introduce?  How do you know?
  • The report indicated that it is unclear how the 787 will become damaged over time and what it will look like.  If left unattended, do you know all the ways in which new IT systems can damage your organization?


WHAT IT MEANS FOR YOU

When dealing with the “unknowns” of IT systems, you cannot prevent emerging issues, you can only respond to them.  The best course of action is to develop the infrastructure and capacity necessary to identify emerging issues (and opportunities) and to quickly respond to them.

This means that you need to have:

  • Clearly defined and assigned the roles and responsibilities for ensuring your IT system is adopted in such a way that it is delivering value and not introducing unnecessary risks and exposure to your organization.  This needs to continue over the life of your system.

  • Developed the tools, metrics, and reporting to give you visibility to emerging risks and opportunities.  You need to identify risks and opportunities as early as possible.
  • Establish communication processes and tools that allow you to have 2-way communication with all stakeholders.  This allows you to identify issues and respond back to them.


HOW TO DO IT

If your organization is like most, you probably agree that you need to do this, but you are not sure how.  Tri Tuns can help.  

We work with organizations to develop the infrastructure you need to manage risks and maximize the value of your IT systems.

With our new User Adoption Portal, MyUserAdoptionPlan.com, we help you drive effective user and provide you the capabilities you need to respond to emerging risks, needs and opportunities.  And we can do it faster, cheaper, and easier than you probably thought possible.

In addition, with our expert services, we can provide the advanced knowledge and skills your team needs to make sure they identify risks before they become problems. 

Contact us to learn what we can do for you.



FIND OUT IF YOUR PROJECT IS AT RISK



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 


Johnny Dangerously on Effective User Adoption Communications



Is the Grapevine Killing Your  User Adoption Communications?


Ensure Your Communications Are Accurate and Effective 

In the clip below, Lil is trying to get a critical message to Johnny Dangerously, who is locked up in jail.  It is a matter of life or death - Johnny must get accurate information about the threat to his brother's life.  We see how easily the message gets mangled as it passes from person to person, until the final message that gets delivered is nothing like the original.  Have you had a similar experience with communications in your organization?  






Apply What You Learned:  Carefully Manage All Communications & Beware of the Grapevine!

Accurate, timely and effective communications are critical to successful User Adoption programs.  Make sure you have carefully develop appropriate communication channels and ensure that all stakeholders receive accurate information.  This involves a variety of steps including setting up communication teams, developing multiple communication channels (live events, email, web sites, blogs, forums, webinars, various social media, etc.), developing a communication strategy, developing communication collateral, and then actually communicating with end users.  It also involves carefully defining the roles and responsibilities for all parties involved in developing, approving, and delivering communications.





Best Practices & Key Questions

  • Develop a comprehensive communication strategy for your user adoption program.  This includes:
      • Create a solid infrastructure for ensuring effective 2-way communications.
      • Define a communication strategy for each phase of your project.
      • Assign specific roles and responsibilities for all aspects of your communication program.
      • Provide for as much active engagement and participation of stakeholders in communication activities as possible.  
  • Beware of the Grapevine!
      • Take steps to ensure that all stakeholders have easy access to accurate and timely communications.   Don't let rumors or inaccurate information sabotage your communication efforts.
      • Ensure communications continue over the life of your system.  Many organizations stop communications once the system goes live, at which point the grapevine takes over.  You need on-going communication efforts to make sure new stakeholders receive accurate information and to respond to evolving communication needs.
      • Proactively ask people what they are hearing on the grapevine and then respond as necessary to squash rumors and inaccurate information.
  • What steps do you take to make sure that all of your communications are accurately conveyed to their intended audience?  How are grapevine communications impacting your User Adoption program?  What can you do to manage the grapevine in your organization?



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 a "teachable moment" for you?  What did you learn?  What else can this clip teach us about improving user adoption?  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 


Creating ownership teams to instill User Adoption


OBSERVATION

User Adoption (UA) is all about creating an infrastructure and support system that promotes end-users to enact the IT system as it was designed.  At the end of the day, however, one can never force workers to perform exactly how you would want; neither can one monitor every behavior that occurs in the workplace.  There must be some way then to ensure users enact the system as designed. Employees who perform best are professionals who can problem-solve on their own while receiving freedom and opportunity to do so.  When system end-users are most engaged in problem-solving the system’s usage, they have a sense of ownership in determining the system’s success.

CONSIDER THIS

One way to encourage ownership is to seek volunteers for special projects (which I call “UA ownership teams”).  These teams can take ownership in helping the organization to remove barriers to user adoption.  Each team member can fulfill a duty, such as:
  • Review inputted data to ensure accuracy of data by all end-users.
  • Mentor less-tenured employees on proper system usage to develop skill set of employee base.
  • Identify best practices among end-users to enact new procedures.
One note of caution: make sure the projects have short timespans and are not overly taxing.  Usually these team members must still complete their normal assignments (even if you temporarily scaled back the amount of work).  If each project commands too much time and effort, you have taken away your best end-users from their normal work duties.

THINGS TO THINK ABOUT

As you plan to implement your next IT system, or are currently experiencing low adoption, consider incorporating end-users as part of your ownership teams.

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 


Retain User Adoption consultants beyond the initial contract to sustain ROI


OBSERVATION

You are responsible for ensuring end-user adoption of the IT system in your organization.  To ensure this occurs, you retained consulting services unique to user adoption, such as Tri Tuns.  Now that the contract is near completion, you are worried that you may see a drop in employees using the system as designed – and hence a decrease in ROI. The one truism of user adoption (UA) is it must be proactively fostered throughout the life of the IT system.  Therefore, creating a new statement of work for the UA consultants may be worthwhile, in order to build a long-lasting UA program.

CONSIDER THIS

As part of a new statement of work, UA consultants will provide a User Adoption program that extends beyond the go-live period.  One key area that UA consultants can help is to establish an internal UA team (made up of client employees).  You may already have an implementation team, but may not have specific assignments to foster user adoption long-term. UA consultants can help to:
  1. Determine the right staff members become UA team members.  Not always should the same people from the implementation team be a part of the UA team.  That is because implementation team members are typically project managers and technical experts, where as long-term user adoption requires a team made up of system end-users and support staff. 
  2. Create solutions that will promote user adoption throughout the life of the IT system.  One such example is creating data quality protocols with methods for monitoring and evaluating the accuracy of data input by end-users.
  3. Develop a schedule for enacting each UA phase that minimizes disruption of pre-existing responsibilities for UA team members.  Team members will undoubtedly have pre-existing workloads; therefore it is crucial to set a UA schedule that does not jeopardize any other responsibilities.

THINGS TO THINK ABOUT

As you plan for the completion of the initial consulting contract, think about how you can leverage additional services that will sustain end-user adoption.

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 


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 



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