Want to come and play? Remember being a kid when things were simpler. A friend called out to come and play and you just went. No thinking about it. No second guessing the why. You just went.
As adults, we have much more complex lives and our time has many more demands, so when we are asked to do something, we tend to ask why and how rather than just do. This is where scenario-based training makes the difference. When people understand the why; when they can make that connection to how new technology will affect them in real time, you get a much greater uptake in adoption. And that is the end game. The way to get true value or return on investment is to ensure people are actually using the new system or new process the way it was intended and not reverting back to old systems or processes.When people understand how new technology will positively impact THEIR work, you get a much better adoption outcomes Click To Tweet
But how do we make it real? We simply tell the story.
We use our own war stories that we have learnt along the way. Or we talk to people within your organisation and find out how they are facing day to day technology challenges. We build the scenarios that will help people see how it will affect them. And when we make it real and relevant, it is much easier for people to see why to get on board. Why they should take the time out of their busy days to learn the new process or adopt the new technology. But it doesn’t happen immediately. It takes time to build, to discover, to plan, to launch and to grow that knowledge. But if the foundations are solid, it is easy to build on.
When doing standard ‘Instructor Lead’ training, we often have people from the same team, who deal with the same type of work, therefore their experiences are often similar. So, when we start chatting about how they could use a technology or function, we allow that conversation to grow and expand right there in the room. The pros and cons come out quickly, but by having an experienced facilitator in the room, it is still an efficient process for finding the right tool for the right job. It’s all about keeping the content real and relevant and not making it about the 500 product functions that they could use. These “on the go” conversations become the scenarios that are real to a team. How to make the technology or function work for them. They get excited about a new way of working because it resolves a problem. They feel involved and part of the solution. And when people are onboard and excited, they share their knowledge with others.
I love the moment when I see a light bulb go off in someone’s eyes. That moment when they see the potential, even if they haven’t worked out every step that they have to take to get there. When they see that they could save themselves time with some email management or track team tasks using Planner. Or when they see the benefits of connecting to others outside their immediate network with the help from Yammer.
My favourite part of what I do is coaching. Sitting with individuals or small groups and nutting out the plan and process to solve their challenges. Whether that is helping a busy EA work out the best way to distribute 30-50 documents to 15-20 executives for board papers on a fortnightly basis using a shared OneNote notebook or perhaps helping teams become more connected using Skype for Business Video conferencing. When we can demonstrate how a technology will save real time, and provide real value to an individual or team, using real-life examples and scenarios, we grow that adoption across the organisation, piece by piece.
I love it more when I see people timidly coming into a room because they didn’t feel confident about technology, leave the room and start sharing the knowledge with other team members. Because it was real. Because it solved their problems. Because we took the time to make it relevant to them.
We simply start the conversations and watch it ignite from there.
So by simply giving the why and the how, behind a new process and system, your users will be able to understand it in their world and therefore be more open to using the product and therefore resulting in greater user adoption.
It all starts with a simple why.
Read more Understanding your workforce for roll-out success