Every Salesforce implementation deserves to be re-evaluated and re-examined. It is an especially expensive investment and it’s reassuring to know that the investment is paying off – that the system is still solving the problems it set out to solve and that users are readily and happily adopting it.

Unfortunately, no Salesforce implementation is protected from the effect of general wear and tear that evolving business processes,requirements and organizational changes can have.

Yes, it can be costly to continually keep up, but not keeping an eye out for these 4 symptoms could result in a much larger, much more expensive problem down the line!

The Symptoms:

Objects and Fields that No One Uses

It’s a fact of development that the way things are designed won’t necessarily be the way things are used. Only time and the user will tell. However, if you’re noticing several fields in your implementation that do not serve a function other than being used as holding areas for miscellaneous notes and comments, it could lead to inconsistent data, bad reporting, and further confusion down the line. Deleting these fields and objects is no easy job. Usually fields are being used by other integrations or processes and may contain valuable data (at least to someone). The proper data validation, extraction, and impact analysis is usually required before acting.

Non-Salesforce Workarounds

Are your users turning to systems outside of Salesforce to get what they need done? Is it easier to extract a report from Salesforce and run a pivot table to present during meetings? Are sales users keeping tasks and notes in excel files? These can be signs of a more serious syndrome called low-adoption-itus (LAI) and may be caused by a mismatch of functionality and practicality. If processes are not defined and trained, and data is not easily accessible to those who need it – users will begin leaving any CRM to get what they need.

Low Code Coverage

Are you passing production validation by the hair of your chinny, chin, chin? That’s not going to be sustainable for long, especially with a big, important deployment. Sometimes you know something works – but you don’t want to be bothered writing the extra test methods to get the code coverage. It’s kind of like playing who will finally take out the trash with your college roommates until trash spills all over the floor and the apartment smells for 3 months straight. Side effects of Low Code Coverage may include: acute anxiety about deployment.

A Broken Security Model

Do more people have Admin access than don’t? That’s not a good thing, but easy to understand – a specific security model was designed, and access was slowly granted to specific fields, then specific records, then specific objects… until caving in and just giving everyone access. It can prove detrimental due to increased risk of internal data compromises which can damage client relationships or violate regulations. Salesforce offers a wide range of tools to properly grant access at the necessary levels, so take advantage of them!

Treatment

What is the best thing to do if yours or a loved one’s Salesforce Implementation is suffering from one or more of these symptoms? Reach out to your Salesforce professional immediately – grant.ongstad@theofficegentleman.com or visit www.officegentleman.com to learn more..

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s