The Real Question
A question recently came through to us that I thought was very interesting:
How do companies keep Sales Cloud training fresh when new features roll out 3 times a year?
It’s a reasonable question.
After all, Salesforce releases major updates three times every year:
- Spring Release
- Summer Release
- Winter Release
If you’re paying for Salesforce, it’s easy to assume you should be keeping up with everything.
The problem is that assumption is surprisingly expensive.
Salesforce Feature Rollouts: The Direct Answer
You really shouldn’t be trying to keep up with every Salesforce feature rollout.
That might sound strange coming from a Salesforce consulting company, but it’s true.
Salesforce features are rolled out by a massive product department.
The Salesforce product team is responsible for building functionality that serves hundreds of thousands of organizations across countless industries.
Your company is responsible for helping a specific group of people do specific work.
Those are not the same objective.
Trying to synchronize your business with Salesforce’s release calendar is recipe for unnecessary cost, unnecessary complexity, and unnecessary disruption.
The Difference Between Awareness and Training
One of the biggest mistakes companies make is confusing awareness with training.
A healthy Salesforce environment should absolutely have someone paying attention to release notes.
Someone should understand what Salesforce is releasing. Someone should evaluate whether those changes matter.
That doesn’t mean everyone in the company needs training every time Salesforce introduces a new feature.
In fact, most users are happily immune to the vast majority of Salesforce releases.
Most salespeople don’t wake up wondering what was included in the Summer Release.
Most service teams aren’t anxiously awaiting new platform functionality.
They simply want tools that help them do their jobs.
A company should be aware of Salesforce releases.
That is very different from assuming every release requires adoption (or anything at all).
The Hidden Cost Formula
Before deciding whether a new Salesforce feature is worth rolling out, calculate the hidden cost.
A simple formula looks like this:
Hidden Cost
Training Cost + Process Change Cost + Administration Cost + Productivity Loss + Ongoing Support Cost
At first glance, most people focus on the feature itself.
What they miss is everything surrounding the feature.
Documentation updates.
Training sessions.
Questions.
Support tickets.
Configuration changes.
Process changes.
Follow-up conversations.
Additional customization.
The feature may be free.
Adoption is not.
What Actually Drives Cost
Several factors influence the true cost of Salesforce Feature Rollouts.
Number of People Affected
Every additional user increases the amount of communication, training, and support required.
Complexity of Your Current Environment
The more customized Salesforce becomes, the harder it is to evaluate how new functionality fits into existing processes.
Time Required for Adoption
People need time to learn.
People need time to practice.
People need time to adjust.
That time comes from somewhere.
Feature Creep
This is where things get interesting.
A new feature often leads to a discussion about another feature.
Then another.
Then another.
Eventually the organization begins chasing Salesforce functionality rather than solving business problems.
This is closely related to the fear of underutilizing Salesforce.
Opportunity Cost
Every hour spent evaluating, training, configuring, and supporting a feature is an hour not spent on something else.
Most organizations ignore this entirely.
What Makes Cost Blow Up
The hidden cost starts to explode when feature adoption becomes a goal.
The moment someone says “We should use this because Salesforce gave it to us” you are in trouble.
Now every release becomes:
- Another meeting
- Another training session
- Another configuration effort
- Another support issue
- Another adoption initiative
Instead of focusing on work, people begin focusing on Salesforce.
That sounds harmless until you realize Salesforce is supposed to support work, not become the work.
The organizations that struggle most with Salesforce Feature Rollouts are usually the ones trying to consume everything Salesforce produces.
That’s simply not a realistic (or useful) strategy.
When A New Salesforce Feature Is Worth It
There is a simple way to evaluate whether a new feature deserves attention.
Feature ROI Formula
Expected Business Benefit > Hidden Cost
That’s it.
If the expected business benefit exceeds the hidden cost, the feature deserves consideration.
Business benefits might include:
- Increased revenue
- Better forecasting
- Reduced manual work
- Improved customer experience
- Reduced risk
- Better reporting visibility
- Higher productivity
If a feature creates one or more of those outcomes at a meaningful level, it’s worth investigating.
Not because Salesforce released it, not because it’s cool.
Because it helps your business.
When It’s Not Worth It
The opposite is also true.
A feature is not worth implementing when the hidden cost exceeds the expected benefit.
This is where many companies get themselves into trouble.
They start with the assumption that they should be using what they paid for.
The logic sounds reasonable.
Unfortunately, it often leads to unnecessary complexity.
You don’t buy an iPhone and use every feature.
You don’t buy a vehicle and use every capability.
You don’t install a home security system and activate every possible setting.
You don’t purchase a streaming platform and watch every show.
You use what creates value.
Salesforce should be treated exactly the same way.
The Common Mistake
The common mistake is assuming Salesforce utilization is the goal.
It isn’t. Business performance is the goal.
The reason I never see successful organizations obsessing over Salesforce Feature Rollouts is because they’re focused somewhere else.
They’re focused on:
- Revenue
- Customer experience
- Efficiency
- Forecasting
- Service delivery
Salesforce is simply a tool that supports those outcomes.
The people who obsess over feature releases are disconnected from the people who actually need to get work done.
The closer someone gets to frontline operations, the less they tend to care about Salesforce release calendars.
What Good Looks Like Instead
Healthy organizations typically follow a much simpler process.
1. Stay Aware Of Releases
Someone should review release notes.
2. Evaluate Relevance
Determine whether the feature solves a real business problem.
3. Calculate Hidden Cost
Use the formula above and be honest.
4. Estimate Business Benefit
What measurable outcome will improve?
5. Roll Out Selectively
Implement only the features that materially improve how people work.
Everything else should be ignored.
Closing Thought
It’s very tempting to start with the idea that you need to be using everything you paid for in Salesforce.
I understand the instinct.
But that’s rarely how successful companies operate.
Trying to keep up with every Salesforce Feature Rollout creates the same problem.
You end up investing time, energy, attention, and money into functionality that may never improve the business.
Eventually you wind up with a bunch of features turned on that don’t directly help people work, create value, or move the company forward.
Quite frankly, nobody wants that.
If you’re trying to determine whether a new Salesforce feature is worth the investment—or you’re struggling with an environment that’s become overly complicated from years of chasing functionality—we’d be happy to help.
We’ll help you evaluate what actually matters, what doesn’t, and where your organization can get the greatest return on its Salesforce investment.