If you’re a leader trying to improve CRM adoption, you’ve probably wondered:

Can I force people to use Salesforce?

It’s a common question, especially after a company has invested heavily in the platform and leadership still isn’t seeing the results they expected.

Unfortunately, the honest answer is no, you cannot realistically force people to use Salesforce.

You can require data entry.

You can create policies.

You can even threaten consequences.

But none of those things actually create adoption.

What they usually create instead is resentment, workarounds, and employees quietly disengaging from the system.

The real issue is almost never that people simply refuse to use Salesforce. In most organizations, the deeper problem is that the system isn’t actually helping them do their job better.

Understanding that difference is the first step to fixing adoption problems.

Why Leaders Try to Force People to Use Salesforce

 

When leaders ask whether they can force people to use Salesforce, it usually comes from frustration.

They’ve approved a large CRM investment.

They’re seeing invoices.

But they aren’t seeing the operational improvements they expected.

So naturally the question becomes:

“Why aren’t people using the system?”

 

At that point, some leaders conclude the issue is discipline.

Maybe employees just need to be told more firmly.

Maybe stricter rules will solve the problem.

That approach can work temporarily, but over time it often creates a different issue: resentment.

People begin complying just enough to avoid trouble, while quietly leaning out of the system whenever possible.

That’s not adoption. That’s obligation.

People Resist Systems That Don’t Help Them

 

One of the most important things to understand about CRM adoption is this:

People usually don’t resist Salesforce itself.

They resist systems that slow them down or make their job harder.

Salespeople want to sell.

Managers want insight into the business.

Operations teams want clean processes.

If Salesforce helps them accomplish those things, adoption tends to happen naturally.

But when Salesforce is implemented in a way that adds friction (more fields, more clicks, more reporting requirements) without improving their daily work, people start finding ways around it.

Sometimes this happens because the system was designed without the actual users in the room.

Leadership defines what they want.

Consultants design the system.

But the people who actually have to live inside the CRM every day were never part of the conversation.

That’s where problems start.

Why Trying to Force People to Use Salesforce Usually Backfires

 

This is why the idea that you can force people to use Salesforce usually doesn’t work.

If the system doesn’t genuinely help people do their jobs, forcing compliance simply creates new problems:

• ~ People enter the minimum data required

• ~ Records get updated late or inaccurately

• ~ Work happens outside the CRM

• ~ Trust in the system declines

 

Eventually the system becomes something employees interact with because they have to, not because it helps them succeed.

That’s the opposite of what a CRM is supposed to do.

The “Customization Fever” Problem

 

There’s another issue that often contributes to adoption problems: customization fever.

Salesforce is an incredibly flexible platform.

You can customize almost anything.

That power is exciting, but it can also lead to a dangerous pattern.

Teams start adding:

• ~ New fields

• ~ New automation

• ~ New workflows

• ~ New reporting requirements

 

because they sound like good ideas.

Over time the CRM fills up with dozens of well-intentioned features.

But no one stops to ask an important question:

Does this actually help people do their jobs better?

 

You can easily end up with a CRM full of “good ideas” that nobody uses.

Before you assume employees are refusing to adopt Salesforce, it’s worth asking whether the system has become overloaded with unnecessary complexity.

A Better Way to Evaluate Your Salesforce System

 

If you want to understand whether adoption problems are a people problem or a system problem, there’s a useful framework borrowed from Lean thinking.

The idea is simple.

Every activity inside your CRM should fall into one of three categories.

Value Add (VA)

 

These activities create meaningful value for the business.

If they stopped happening, leadership would lose critical insight into the business.

Examples might include:

• ~ Accurate deal tracking

• ~ Pipeline reporting

• ~ Revenue forecasting

• ~ Key customer data

 

These activities should absolutely remain in the system.

Non-Value Add (NVA)

 

These activities do not meaningfully contribute to the business.

If they stopped today, the organization would see little or no impact.

Many CRM systems accumulate tasks like this over time:

• ~ Duplicate fields

• ~ Unnecessary status updates

• ~ Reporting data no one uses

 

These should  be eliminated.

Non-Value Add Required (NVAR)

 

These activities may not directly help the user, but the business still requires them.

Examples might include:

• ~ Compliance documentation

• ~ Certain financial tracking fields

• ~ Regulatory reporting

 

These should be reduced or automated whenever possible.

How This Framework Improves CRM Adoption

 

Once you categorize Salesforce activities into these buckets, the path forward becomes clearer.

Value Add (VA)

Keep these tasks and reinforce their importance.

Non-Value Add (NVA)

Eliminate them completely.

Non-Value Add Required (NVAR)

Reduce the effort required or automate them whenever possible.

When users see that the system focuses on high-value activities, adoption improves dramatically.

Instead of asking whether you can force people to use Salesforce, the conversation changes to:

“Does this system actually help our team succeed?”

That’s a much healthier place to start.

Salesforce Adoption Is a Two-Way Street

 

It’s easy to assume adoption problems come from employees refusing to cooperate.

But in reality, CRM adoption is a two-way relationship.

Leadership has to ensure the system:

• ~ Supports real business processes

• ~ Removes unnecessary complexity

• ~ Focuses on valuable activities

 

Users, in turn, need to engage with the system consistently.

When both sides hold up their end of the relationship, Salesforce becomes what it was always meant to be:

A tool that helps the business operate more effectively.

Not a system people feel forced to use.

 

Final Thoughts

 

So can you force people to use Salesforce?

Technically you can require compliance.

But true adoption doesn’t come from pressure.

It comes from building a system that genuinely helps people succeed.

If your team isn’t using Salesforce the way you expected, the solution usually isn’t stricter rules.

It’s stepping back and asking whether the system is focused on the work that actually matters.

When Salesforce becomes valuable to the people using it, adoption tends to take care of itself.

If you would like help applying the framework mentioned to your business let us know.