Key takeaways
- Reps skip the CRM when it costs them time and gives nothing back. Fix both sides of that trade.
- Cut layouts down to the fields that matter at each stage, and capture emails and meetings automatically.
- Make Salesforce the place where pipeline reviews happen, so updating it has a visible purpose.
- Measure adoption with a few simple numbers and review them monthly.
Every sales leader has heard it: "I'll update Salesforce later." Later becomes Friday afternoon, and Friday becomes never. The pipeline report goes stale and the forecast becomes guesswork.
Our team has spent years in sales operations supporting reps who didn't want to use the CRM. In almost every case the reasons were practical, not lazy. Here is what usually goes wrong and how to fix it.
Why reps avoid the CRM
It takes too long. An opportunity page with 60 fields and three required sections feels like admin work, not selling.
They get nothing back. If the CRM doesn't help a rep plan their day or close a deal, it's a reporting tool for someone else.
Duplicate effort. Notes in a notebook, emails in Outlook, deals in a spreadsheet for the manager, then the same again in Salesforce.
Nobody uses the data. If pipeline reviews happen from a slide deck, updating Salesforce has no visible purpose.
They were never shown how. A one-hour training at onboarding is quickly forgotten.
8 fixes that work
1. Simplify the page layout
Show only the fields that matter at the current stage. Dynamic forms in Lightning let you display fields based on stage, so early-stage deals show qualification fields and late-stage deals show contract details. Aim for fewer than 15 visible fields per stage.
2. Capture activity automatically
Tools such as Einstein Activity Capture sync emails and meetings from Gmail or Outlook, so reps don't log them by hand. Check your edition and privacy settings first, and agree which data is captured.
3. Use the path component for guidance
The path at the top of an opportunity can show key fields and short guidance for each stage. Reps see what's expected without opening a manual.
4. Make the home page useful
Put each rep's own numbers on their home page: deals closing this month, overdue tasks, attainment. When Salesforce helps plan the day, people open it.
5. Run pipeline reviews from Salesforce
This is the single most effective change. When managers review deals directly from Salesforce dashboards and list views, every rep learns that the record is the truth. A deal that isn't updated isn't discussed.
6. Automate the boring parts
Follow-up tasks, renewal opportunities and handovers can be created by Flow. Every automated step is one less reason to avoid the system. See 10 Flow automations for small teams for ideas.
7. Train little and often
Replace one long session with short, role-specific sessions and two-minute videos. Run a feedback session after each change to hear what still slows people down.
8. Measure and share adoption
Build a simple adoption dashboard and review it monthly with managers. Recognise improvements rather than only calling out gaps.
Adoption metrics to track
| Metric | Why it matters |
|---|---|
| Weekly logins per user | Shows whether Salesforce is part of the routine |
| Opportunities updated in the last 7 days | Shows whether the pipeline is current |
| Opportunities with a next step and future close date | Shows forecast reliability |
| Activities logged per rep | Shows whether customer contact is visible |
Change management matters as much as configuration
The best layouts fail if they arrive without explanation. Tell reps why a change helps them, involve one or two respected reps in testing, and fix their feedback quickly. When people see their requests turn into improvements, they start suggesting more.
If adoption is your biggest Salesforce problem, the training and adoption service combines layout simplification, short training and an adoption dashboard.
Frequently asked questions
How do you measure Salesforce adoption?
Track a handful of numbers per user: logins per week, opportunities updated in the last 7 days, activities logged, and the share of open opportunities with a next step and a future close date. Trends matter more than absolute values.
Should we make more fields required to force reps to fill them in?
Use required fields sparingly and at the right stage. Too many required fields lead to placeholder values, such as a single dot, which is worse than an empty field because it looks complete.