In the Webex adoption methodology we have business drivers, the five pillars of success (leadership; technical readiness; use cases; communications; champions), and the measurement components. When you are driving change in your organization - which one is your powerhouse MUST have to ensure success?
What resources do you use?
Don't be shy on details! Tell us the story of how you were successful.
For me it is Technical Readiness, as an implementer of the new technology, to plan and prepare , specially for the technically challenged, is one of the keys to success. There are all sort of customers/clients, some would be more savvy than others, if we plan and prepare for an easy transition or new tool, the better we are prepare to tackle the questions/issues from new users , the smoother and friendly the technology will be for them all.
Use cases and recruiting champions within the different business units has been successful for us. When we hold trainings on Webex, I like to bring up the various use cases on how using Webex Meetings or Webex Teams can benefit a particular business unit. Also staying in touch with a champion can help accelerate adoption across the various business units.
Leadership buy-in is critical. Choosing a sponsor/champion with influence that is also an early adopter is a great help to getting additional buy-in at the upper levels, as well as helping to smooth over any issues at the upper levels. Once the upper levels buy-in, the trickle down effect is real. Users at the lower levels will have to adopt the new technology to continue working with their managers.
Technical Readiness was the key. We did the calling integration with our local gateway so every coworker able to make a phonecall from webex app thru our local infra.
Here is the config example:
alignment of your adoption strategy with the overall culture of the company is the key and there is no silver bullet. The “powerhouse” may be different each time.
Use people as your best resource. The help build your adoption strategy that is inclusive of the entire global collaboration strategy, by understanding a day in their life and highlight the use cases for each team/department. Don’t paint the world with the same paint brush.
Communications and Technical Readiness are our key drivers for adoption. We have a website available with documentation personalized with our company logo and system settings. It includes a Quick Reference guide and short, topic specific videos for common questions and tasks. It also has links to online resources like the Cisco training portal, the Webex Help Center and other online references. Having this resource available for staff and keeping it updated helped with adoption since they were able to do self-service for most of their questions.
We also provided classes about every 2 weeks for the first couple of months where we covered the Webex Basics as well as new features that were added. During the class we demonstrated features and also had time for attendees to ask questions and practice using features.
I have also have had luck with use cases.
When we opened a new building the strategy we took to get people to try out the use cases and receive some training was to gamify the experience. We made a passport for them get stamped as they moved around to a couple different rooms where we had staff showing quick 5 minute or less use case demonstrations. We had the rooms available for a couple days to allow people plenty of freedom to just quickly drop in whenever worked for them and even pop back in if they had follow up questions. We had snacks and drinks available to entice them in and of course those who completed the passports were entered into raffles to win larger prizes.
We had great participation from our associates and saw much better than expected metrics of our users adopting some of the "advanced" features of the rooms that we covered in our use cases. So we were very pleased and will be using this approach again in the future.
I'll go first.
Use cases are the most critical part of the adoption methodology for me. When I start with the people that are actually using Webex and make it crystal clear how I can help them - I can drive success for THEM. If I can craft a really specific story for them and show how we can save them time, energy, how this fits into their current systems - they will want to use the solution. I like to start with who are the people, and what the heck are they trying to do? This might be reworded as "what is the job to be done?" From your people it might sounds like, "Ugh! Don't tell me everything, I just need to ".
My awesome use cases make sure my communications are specific, tell my folks exactly what they need to know (and nothing they don't) and will land with my audience. It makes me ensure my technical readiness will support any integrations that are required. It helps me build the business case, then I have a way to measure the results too! And of course - if I know the use case - I can find champions to help evangelize it.
Here's an example.
Job to be done:
I'm Molly. I hold a meeting three times a month with an international group of collaborators and I just need to make sure everyone's voice is included, and everyone can participate.
Cool. We got you.
Webex Meetings with Webex Assistant can help you do that!
My training, communications, and help guides will all support this specific use case. I don't just say "Webex will make your meetings more inclusive!" Show me - don't tell me. In a normal person's language.
I love the idea of fleshing out multiple use cases with a tactic we lovingly call "We feed you; you feedback". Hold a Webex session, have snacks delivered to your attendees (8 or less) and pick their brain on what their problems are. Use your favorite online visual collaboration platform for teamwork and a mountain of e-stickie notes to get that ideation flowing.