Salesforce User Adoption, Part II: Improving Salesforce User Adoption
Creating a great Salesforce app for your team is only part of the solution; the other part is getting your team to use the app. The best tool in the world is useless if it's not used! You've seen plenty of tips about signs your team has bought into using Salesforce. Your next step is improving Salesforce user adoption, and communication, training, and continuous refinement are the keys.
It's easy to assume that someone needing user support is not using the application correctly. What if there really is a bug?
We've all seen the acronyms from user support techs: ID-10-T errors, PICNIC, PEBKAC, and so on.
On the one hand, they're pretty mean-spirited (but kinda funny). On the other hand, who can blame user support techs for being exasperated when rude, frustrated users scream at them to solve problems that aren't their fault. Yes, some support techs really do have to walk users through the most basic of operations. REALLY basic, like making sure the computer and monitor are plugged in and powered on. On the OTHER other hand, it is the job of support techs to bridge that knowledge gap.
As consultants, we are often called upon to support our own or someone else's software. We have to be the opposite of that acronymic stereotype. Users aren't idiots; they're experts in something we are not proficient in and vice versa.
Once in a while, we are on the receiving end of user support, and these experiences can be real eye-openers. I remember one instance where we found an undocumented limitation of a mature third-party application.