Introducing New Technology To Your Team

Teamwork Solved > Optimisation  > Introducing New Technology To Your Team

Introducing New Technology To Your Team

Many managers are all too familiar with the range of reasons their team members have for not wanting to adopt a new system. Reasons range from “The system is too slow” or “the data is junk”, all the way to “my boss doesn’t use it, so why should I”, and “I never got proper training!”


If you find yourself struggling with user adoption you are certainly not alone. User adoption can be a difficult task on the best of days. Most of us are naturally hesitant to change, which means that successfully getting your team to use a new system/software requires a number of tactics and a solid user adoption strategy.


Here at the Teamwork Solved, we have a few tricks and tips that we have gleaned over the years as we have helped companies successfully navigate moving their teams from one system to another. Here are our starting 9 (in no particular order) to help improve your user adoption rate right out of the gate.


9 Tips for Increasing User Adoption.

  1. As a leader, take ownership and responsibility for your team adopting the new system. Your team will be looking to you to set the tone and direction for the new system you are introducing.
  2. Communicate to your team a clear vision for why adopting the new system is important and critical, not only for the success of the company but to each team member’s individual success. Highlight the problems that the team members have, and how the system will solve them.
  3. Simplify the process of getting up an running in the system by starting to use it for your high value tasks first. This will help everyone not feel as overwhelmed by the process of getting everything into the system.
  4. Give the team ownership in adoption by asking for feedback on the layout and process.
  5. Make sure the platform mimics your business processes instead of trying to change your business processes to match the out of the box platform capabilities.
  6. Follow up consistently with users: Schedule time in meetings, set 10 minutes aside during a weekly or monthly meeting to discuss the system. Address any issues or concerns and provide tips how to use the system better.
  7. Train your team in how you will be using the system. Not only showing them the how-to basics, but make an effort to show them how “This will make  my job easier”.
  8. Training scenarios are great, but whenever possible, use real world ideas. Use a current project that your team is working on, and familiar with to foster greater understanding amongst your team
  9. Schedule follow-up training. Remember it is not a “one and done” thing.  3 days, 3 weeks, 3 months after training, have follow-up or review sessions to see what questions come up, what users want to know more about or are struggling to understand, etc. Don’t forget your new hires. Often times when a company launches a new system the entire team gets trained, then new people come on board but get the abbreviated version. Ongoing training will not only help your experienced users, but ensure your new users are not left to fend for themselves.


There you have it! Nine easy tips to help your team embrace change and get set up for success in their new system.


We use cookies to give you the best online experience. By agreeing you accept the use of cookies in accordance with our cookie policy.

Privacy Settings saved!
Privacy Settings

When you visit any web site, it may store or retrieve information on your browser, mostly in the form of cookies. Control your personal Cookie Services here.

These cookies are necessary for the website to function and cannot be switched off in our systems.

In order to use this website we use the following technically required cookies
  • wordpress_test_cookie
  • wordpress_logged_in_
  • wordpress_sec

For perfomance reasons we use Cloudflare as a CDN network. This saves a cookie "__cfduid" to apply security settings on a per-client basis. This cookie is strictly necessary for Cloudflare's security features and cannot be turned off.
  • __cfduid

Decline all Services
Accept all Services