Your pipeline review starts the same way most weeks. You pull up Salesforce, scan the open deals, and notice half of them haven’t been touched in three weeks. One opportunity that closed last month is still sitting in “Prospecting.” A rep mentions a deal that isn’t in the system at all, because “it’s early” or “I’ve just been tracking it myself.”
You’ve seen this before. The instinct is to tighten the screws: make more fields required, tie commission to data completeness, schedule another training session. It feels like the responsible move. It’s also usually the wrong one.
The real problem isn’t compliance
Reps who avoid Salesforce aren’t confused about how to use it, and in most cases they aren’t being careless either. They’re behaving rationally inside a system that doesn’t help them do their job. If updating Salesforce costs a rep time and gives nothing back, they’ll do the minimum required to avoid getting flagged, and they’ll keep their real deal tracking somewhere else.
Reps don’t ignore Salesforce because they’re careless. They ignore it because it doesn’t help them do their job.
That’s the pattern we see across sales organizations struggling with adoption. The CRM is technically “adopted.” Licenses are assigned, logins happen, fields get filled in right before the deal review. But the actual selling work runs somewhere else.
Forrester’s research on CRM adoption backs this up: organizations report broad CRM adoption across functions, but satisfaction with what that CRM actually delivers stays low. Being logged in isn’t the same as getting value.
Why more training doesn’t fix it
Training answers the wrong question. It assumes reps don’t know how to log an activity or update a stage. Most of the time, they do. What they don’t have is a reason to believe it’s worth the extra clicks.
If a rep already knows how to use Salesforce and chooses not to, another walkthrough of the interface won’t change their calculus. The fix has to change what happens after they update the record, not how well they understand the button. Training teaches people to use a system that already creates value. It can’t manufacture value that isn’t there.
Leadership sets the real rules
Adoption is shaped less by policy than by what leadership actually references in front of the team. If your Monday pipeline review runs off a spreadsheet someone rebuilds by hand every week, that spreadsheet is the real system of record, whatever the CRM policy says.
Reps notice this fast. If a manager opens a personal tracker instead of Salesforce during a deal review, or asks a rep to “just send me the numbers” separately, the message lands clearly: Salesforce is where data goes to satisfy IT, not where decisions actually get made.
If your deal reviews run off a spreadsheet, your spreadsheet is the real system of record, whatever the CRM policy says.
Ask what your own team actually opens during a forecast call. If it isn’t Salesforce, that’s the first thing to fix, before you touch a single field or add a single validation rule.
What’s actually breaking adoption
Here’s a composite example based on patterns we see across mid-market sales teams. It isn’t one specific client, just a familiar shape.
A regional sales team of a dozen reps has a Salesforce opportunity layout with more than 40 fields. Maybe six of those fields reflect anything a rep actually needs to track to close a deal. The rest exist for reporting that only leadership looks at. Meanwhile, the team’s real forecast lives in a shared spreadsheet that predates the CRM rollout, because it’s faster to update and it’s what actually gets reviewed every Friday.
Reps end up doing double entry. They update the spreadsheet first, because that’s what gets looked at. Then they update Salesforce, because compliance requires it. Neither update gets the rep anything back. No faster quote. No auto-filled proposal. No time saved anywhere in their week. Salesforce becomes overhead layered on top of the job, not part of it.
A few patterns show up over and over in orgs like this:
- Page layouts built for reporting, not selling. Most of the fields serve a dashboard, not a deal.
- Duplicate systems holding the “real” version of a deal. A spreadsheet, a notebook, a personal CRM inside someone’s inbox.
- Stages that don’t map to anything a rep actually does with a buyer. Movement between stages becomes guesswork dressed up to look tidy.
- No visible payoff for the rep. Only management gets something out of the data being there.
The cost of working around Salesforce
None of this stays contained to the CRM. When reps keep the real deal information somewhere else, forecasts drift from reality, because they’re built on whatever got typed into Salesforce last, not on what’s actually happening with the buyer. Leadership starts double-checking numbers against side conversations. Deals fall through in the handoff between reps, because the full context never made it into the system anyone else can see. And every quarter, someone asks why the CRM the company pays for doesn’t seem to reflect the business.
That question rarely has a training answer.
Run this diagnostic before you change anything
Before adding a field, a validation rule, or another training session, run this checklist against your own org:
- What does your team pull up during pipeline reviews? Salesforce, or something else?
- How many fields does a rep have to touch to log one call or move one deal forward?
- Does Salesforce save a rep time anywhere, or does it only take time?
- Is there a spreadsheet, notebook, or side tool holding the “real” version of any deal?
- Do your stages reflect something that actually happened with the buyer, or are they guesses updated to look tidy?
- When did rep feedback last change how Salesforce works, versus the last time a rep was told to comply with it?
If most of your answers point away from Salesforce, that’s your diagnosis. The system isn’t broken because reps won’t use it. Reps won’t use it because, as built, it isn’t helping them.
What to do next
Don’t start with a redesign. Start with a diagnosis. A rebuild aimed at the wrong problem just moves the friction somewhere new, and you’ll be back here again in a year with a longer list of required fields.
The free Org Health Scorecard is built for exactly this moment: a quick, structured way to see where your Salesforce org is actually creating friction, not just where it looks incomplete. It takes about three minutes and gives you a clearer starting point than another round of training or another required field.
Fix the reasons reps route around Salesforce, and you stop needing to enforce adoption. It becomes where the work already lives.