How Healthy Is Your Salesforce Implementation?


No matter how good, or thorough your original implementation of Salesforce was, it will from time to time need maintenance or even periodically an overhaul. The good news is because it’s a cloud-based solution, Salesforce has your hardware health monitoring and maintenance covered for you. But you are not off the hook for everything:

●  Data quality, duplicates and other small errors can creep into the best designed systems.
●  Depending on the original architecture significate increases in data can start to create performance issues.
●  Salesforce has three upgrades a year that bring new features and subtle changes to the platform that should be reviewed.
●  Your business is constantly evolving and so requirements and business processes will change.
●  Incremental additions such as record types, validation rules, etc. can quickly get out of hand. It is not uncommon to want to rethink the overall architecture of your system based on changes in your business.

Constant tweaks, field additions, workflows and approval process modifications added by the day to day administration for the system means the tool evolves away from its original implementation specification. Salesforce, like everything else unfortunately abides by the 2nd law of thermodynamics – everything tends toward disorder.

There is perhaps a temptation to follow the adage “if it ain’t broke don’t fix it” or let your Salesforce implementation alone unless it starts to have issues. But this would be at the risk of ignoring another law that we all have experienced at some point, Finagle’s law of dynamic negatives, also known as Finagle’s corollary to Murphy’s law – anything that can go wrong will go wrong and always at the worst or most inconvenient moment.

If your business depends on Salesforce then the last thing you want is to be caught by surprise when it starts to yield anomalies or errors that prevent you from running your business.

Just as you should get your car serviced, or see your doctor once a year, so too should you have a strategy in place to give your Salesforce implementation a periodic health check. Some of these checks can be in the form of well-designed audit reports that can be run at set intervals to look for early warning signs of trouble. But eventually a full system check that reviews the entire implementation is wise because of:

●  The impact of increasing number of records (code that used to work can create errors later).
●  Salesforce governor limits – how close are you to exceeding them?
●  Salesforce release features.
●  Salesforce critical update implications.
●  Your organization’s current structure.
●  Your organization’s current business process requirements.
●  Security needs and it’s ever changing best practice.

Some organizations may have the skill sets in-house to do such a review but many would be best served turning to specialists to complete such a task. It is the combination of skills required that makes this sort of task better suited to external help. No matter how accomplished your Salesforce internal team is, an independent and unbiased health check-up should be on your Salesforce to do list. Inaction will most assuredly lead to trouble. Proactive preventions will always be the more cost effective strategy so if you need any advice or help, give us a call.


View More of David's Posts