You spent six figures on Salesforce. The team uses it for about an hour a week, mostly to update the records their manager will ask about. The real pipeline lives in a spreadsheet. The forecast lives in someone's head. Sound familiar?
This is the most common Salesforce complaint we hear and it almost never gets diagnosed correctly. The standard reaction is "we need more training". It's not a training problem. It's a usability and trust problem, and training won't fix it.
Why people bypass Salesforce
In our experience, three root causes account for nearly every "team won't use Salesforce" engagement we've taken on:
1. The form is too long
Standard layouts ship with 40–80 fields visible on a single record. Sales reps look at that, decide they don't have time, and fill in the three fields the manager will ask about. Then nobody trusts the data because most of it is empty, so reports are unreliable, so reps trust them less, so they go to spreadsheets.
2. The process doesn't match how they actually sell
Pipeline stages designed by someone who read a methodology book don't match how a real deal moves. So reps either skip stages, lie about stages, or keep their real pipeline elsewhere and update Salesforce on a Friday for the manager.
3. It's slow and ugly
This sounds petty until you've watched a sales rep wait eleven seconds for a Lightning page to load eight times an afternoon. Performance and visual design are not vanity metrics — they directly drive whether people use the system in the moment they need it.
Why training doesn't fix it
Training fixes "they don't know how". Bypass behaviour is "they know how, but it's not worth it". Training someone harder on a tool that genuinely costs them ten minutes per record they didn't want to create doesn't change their incentives. It just creates a meeting they have to sit through.
The honest test: ask your team in a quiet 1:1 what they would do if Salesforce went offline tomorrow. If the answer is "carry on for two weeks before anyone noticed", the system isn't part of how they work. Training won't change that.
What does fix it
The fixes are unglamorous and they work:
- Strip the layouts. Cut the visible field count by 60–70%. Hide fields that are filled in less than 5% of the time. Move the "important to leadership" fields into a separate tab.
- Simplify the stages. Most B2B businesses need four or five pipeline stages. Six is the upper limit before reps start gaming them.
- Fix the speed. Audit Lightning page load times. Remove unused related lists, embedded charts and slow Apex callouts from the main record page.
- Automate the boring bits. Stage progression based on activity. Auto-population of fields from related records. Anything that removes typing.
- Make the dashboards useful. Reps will use Salesforce if it tells them something they didn't know — their own conversion rate, which deals are stuck, what the team average is.
Do these and adoption climbs without anyone running a training session. We've seen orgs go from 20% daily active rep usage to 80%+ inside two months by stripping the layout and fixing the dashboards. No new licences, no training course, no consultancy retainer.
Where to start
Start with the field audit. Pull a report of how often each field on the Opportunity object is populated. Anything under 10% is a candidate for the chop. Run it past the team, agree what to keep, ship the change. Watch what happens to the data quality on the fields that survive.
If you'd rather have someone outside the org do the audit, our Salesforce Health Check covers exactly this. The wider Salesforce services page covers what an engagement looks like beyond that.
The mistake to avoid: scheduling another training session and hoping. It hasn't worked the last three times and it won't work this time either.
Frequently Asked Questions
Isn't training the right answer for low Salesforce adoption?
Only if the genuine problem is that people don't know how to use it. In our experience that's rarely the real cause. People bypass Salesforce when the cost of using it outweighs the benefit, and training doesn't change that equation.
How many fields should be on a typical Opportunity layout?
For most B2B businesses, 12–20 visible fields on the main page is plenty. Anything beyond 30 starts to suppress data quality. The fields nobody fills should be hidden, not deleted.
How many pipeline stages are too many?
Six is the practical upper limit before reps start gaming them. Most businesses do better with four or five clearly distinct stages that reflect how deals actually move.
How long does it take to fix bypass behaviour?
Layout and stage simplifications usually show measurable adoption improvement within four to eight weeks. Performance fixes can be quicker. Cultural shift around "Salesforce is the source of truth" takes longer — three to six months.
Will simplifying the layouts mean we lose data?
Hiding a field doesn't delete it. The data is still there if you ever need to bring the field back. We never recommend deleting fields without a proper review.