Forum Discussion
Teams adoption
romana240thanks for the message. Yes this is my background working in change management, adoption and learning and development. I work for a Microsoft partner calledhttp://www.adoptandembrace.com and this is exactly the type of work and typical of situations we come across on a daily basis. We help companies to look at ways to help, support, empower their workforce to use these tools within their daily work flow. It's not about forcing anyone to do anything - it's about an empathetic understanding of their business and how work flows between all the people, the systems they use, the processes they have, the knowledge, skills, capabilities and motivations of the workers to change and adopt to new system. It's also an awareness of the culture and political environment and sensitivities in the workplace. If you can identify a business case to pilot your product and evaluate it against some tangible business goals then you're more likely to see success - and support and sponsorship by business managers for it.
Hello romana240 how exciting that you've got a new messenger app and looking now to roll it out. I would say the first thing is to find a user case in the business first - and to pilot it with a small group of people who are willing experimenters. Consider some key business outcomes you want to achieve and measure these throughout your experiment. That is,
*how much time do you want to save and how does this translate to $ back to business?
* How easy is it to implement and how much does this translate to $ business?
* What new ideas and insights were formed (that spins off new business ideas, innovations, products or services?)
The experiment should last for a period of time where you can measure tangible outcomes. If they see the product working on business problems (solving, saving time, money, resources), then it would be easier to influence people to use it.
Morning Helen Blunden and thank you for your response.
I already have few colleagues that are strong supporters, but there is still a lot of work to be done in getting the rest of the team to join in. I am in the industry that is notorious for being hesitant when adopting a change :).
In your case, have you expanded beyond just internal users and if not, do you know if that is an option?
romana240thanks for the message. Yes this is my background working in change management, adoption and learning and development. I work for a Microsoft partner calledhttp://www.adoptandembrace.com and this is exactly the type of work and typical of situations we come across on a daily basis. We help companies to look at ways to help, support, empower their workforce to use these tools within their daily work flow. It's not about forcing anyone to do anything - it's about an empathetic understanding of their business and how work flows between all the people, the systems they use, the processes they have, the knowledge, skills, capabilities and motivations of the workers to change and adopt to new system. It's also an awareness of the culture and political environment and sensitivities in the workplace. If you can identify a business case to pilot your product and evaluate it against some tangible business goals then you're more likely to see success - and support and sponsorship by business managers for it.
