Take Strategic Sourcing Adoption Step-by-Step

For Best Strategic Sourcing Results, Take Your Users on a Step-by-Step Journey

Thursday, August 13, 2015
BY: Ole Nielsen, Chairman and Founder

When you’re getting started with a new TV, all you really want is Power, Volume and Channels…

More than that, you just end up with confusion, frustration, and poor business results. Once you have the basics down, then you can move on to DVR recording, satellites and multiple video feeds.

The same holds true for the software platforms you use to run your business. The challenge comes when the system has so much functionality and complexity that users get confused before they can get comfortable with what they need to get started.

When we started Scanmarket in 1999, it was founded on several core principles:

  • Software only creates value if people actually use it
  • Ease of use and ease of adoption trumps advanced functionality
  • Access to advanced functionality only when your people are ready for it


To that end, we created an approach to give your users the functionality they need in the increments they need it. 

Scanmarket was purposefully architected to provide your program the best opportunity to succeed, while giving your user community a structured on-ramp to increase capabilities as they get more comfortable. 

We recommend the following:

  • Three tiers for new (Novice), experienced (Pro) and expert (Super User) users
  • Set predefined toll gates for “promoting” a user from one tier to the next
  • Set specific functionalities within each tier that are tailored to your business (e.g. if you run lots of auctions, go heavy on those from the start)
  • Keep flexibility to make changes as needed 


Additionally, it provides for opportunities to create competition and recognition among your team as they move up the achievement ladder. You can even create a video game-like system where your people receive points toward “wizard” status. There’s no reason not to create a little fun in your program.

Scanmarket grows with the user instead of the other way around. This leads to deeper and faster adoption. It also lessens the learning curve for your users. This delivers better overall results for your program.