Sometimes it’s helpful to see things from another perspective.
Here are a few ways to certainly not help your end users and avoid adoption in a Salesforce project.
Don’t understand their current process
Before starting to build, you should have a good understanding of your client’s current process. The high-level steps performed by each role should be documented.
Failing to do this will result in creating processes from scratch, and forcing users to use the system in the way you think they should.
Only talk to management
Management knows best right? I mean, the Sales Manager should know the in’s and out’s of the system, and is the single source of truth for their sales team, right?
Um, no. Please don’t do this. It takes an army to build a good Salesforce solution, and part of that army includes your client’s lieutenants and soldiers. You need to know what they need to do.
Build in a silo
“Once the design is complete and you’re ready to build, turn off your email notifications and start building!” said no one ever.
The more of the build you share early on, the more people will be able to provide feedback and guide you to a “good enough” outcome.
The takeaway
There are certainly many ways to set up your Salesforce project for adoption failure. Avoid these three at all costs.