In last week’s Tip, the first in our Dreamforce Tips series, I let Sondheim do the talking on taking a phased approach to system building. This week’s tip goes hand in hand with that. So you’ve worked hard, built a solid foundation, planned appropriately, and created a state of the art new Salesforce org. You can’t wait for your team to start using it. But when you try and roll it out, things start falling apart, your team isn’t adopting it, and you’re starting to realize there’s a bigger learning curve than you thought. This seems unavoidable and insurmountable, but believe it or not, there’s a solution! It’s called planning for rollout.
This was the second most repeated tip I got from the Salesforce team at Dreamforce this year. It doesn’t matter how methodically and carefully you work to build a new system if your rollout falls apart. A little planning ahead can go a long way. Just like we recommended you build bit by bit, rolling your system out to your team should go the same way. Pick the quick wins first, things that will really get your team excited by saving them time and helping them do their job with less stress. As they gain confidence and see value, they’ll be motivated to spend more energy learning and be less stressed when a bug crops up. It may take a little time to get everything out to your team, but everyone from executives to sales assistants will thank you later.
-Jared and the Salesforce Guys
Dreamforce Sock Update:
The Dreamforce Socks are making amazing progress! I’m about almost to the heels, and I hope they’ll be turned by the end of next week. Wish me luck!