Keeping it Simple
Updated: Jan 15
I am going to talk about how to keep it simple. Salesforce implementations don’t need to be over complicated.
The main reasons why you may hear that they are because
The stakeholders don’t know what they want
No internal processes have been set up or implemented
No business analysing process and middle man communication to CRM development team
No internal ownership of the CRM implementation project
No subject matter expert appointed
Believe me, developers do take anything you say as a literal. Not many would ever come up for air and see how this may affect your future business goals and strategy or your Salesforce road map for that matter – for example turning on Lightning User Interface…
When considering how to take on your CRM project think about what you currently have, and what you want in there, is there any historical data you’d like to move into the new CRM and who will champion the whole process and be realistic about the resources available to manage this.
How do you want the sales users and the key data entry users to engage and adopt your CRM? The data quality will only be as good as that that goes in so you must think about they key things you want to be inputted. This in turn will be your output of reports and fancy dashboards.
Keeping page layout configurations to a minimum. Trust me, once you use Salesforce or any other CRM it’s only after having used it and coming up against lots of different use case scenarios, that you will really realise what you do and don’t use and why waste an implementation budget?
There are great little audit tricks and reports you can do to gain better insight! But, from my experience user testing periods won’t ever be long enough because you may go live at a time of a new release of Salesforce.
So, book in a review date with your CRM Champion or yourself, where you can analyse what was best adopted, and even better, implement a user testing focus group to begin with and get feedback.
Once you are actually using the product you will then see where some complexities like integrations may be a viable investment, then you can consider to bring in a implementation partner that is specialised in that area!
My advice, don’t complicate it, multi phasing every step of the way as your org grows and use the out of the box functionality – that’s what it’s there for!