Things are getting a little out of control.
Requests are piling up.
Different departments want different things.
People have started throwing around terms like:
“We need better oversight.”
“We need more structure.”
“Maybe we need a Salesforce Governance Committee.”
You’re wondering if a committee will solve your problems.
I’ll save you some time.
No.
A Salesforce Governance Committee is not likely to solve this problem.
In my experience it will reinforce politics, reward appeasement, and accelerate system bloat.
Salesforce Governance Committee: The Short Answer
Governance committees sound professional.
They sound responsible.
They sound like a way to create alignment.
Operationally they tend to become:
- Places to play nice
- Places where everyone gets heard
- Places where nobody says no
- Places where requests pile up
- Places where Salesforce slowly turns into clutter
The problem is simple. The only way to make everyone happy is to keep adding things.
CRMs do not become useful through addition, they become useful through prioritization.
Those are very different activities.
How Salesforce Governance Committees Actually Work
On the surface, governance committees provide oversight.
The theory looks good, everyone is represented.
Every department contributes.
Different viewpoints are considered.
The CRM evolves fairly.
Sounds great.
The problem starts when “fairness” becomes the operating principle.
Because fairness eventually turns into:
Sales → gets a field
Marketing → gets a field
Finance → gets a field
HR → gets a field
Leadership → gets a field
Operations → gets a field
Eventually everyone receives a souvenir, while the business does not receive prioritization.
This is how Salesforce becomes a feature factory instead of a useful work system.
Why Salesforce Governance Committees Exist In The First Place
Committees are formed because they feel like the mature way to solve chaos.
One day you wake up to a growing backlog, increasing complaints, and dropping adoption.
More oversight is the natural next step in that environment.
Gathering groups feels safe.
Consensus feels safe.
Participation feels safe.
The problem is that unstructured groups optimize for harmony not output.
That is not the same thing as creating a useful CRM.
A Salesforce Governance Committee becomes a socially acceptable way to avoid prioritization.
That sounds harsh.
I mean it.
Because prioritization requires discomfort:
- Saying no
- Delaying requests
- Removing things
- Upsetting departments
Committees tend to avoid discomfort.
Salesforce absorbs the cost instead.
Real Example: What A Salesforce Governance Committee Did To This CRM
This is not an extreme example.
It’s actually fairly common.
This was a growing company with 150 employees. They were moving from Dynamics to Salesforce.
Their committee had 13 members spanning the following departments:
- Sales
- Marketing
- Finance
- HR
- Operations
- Leadership
- C-Suite
They met monthly and there was no voting.
Everyone simply needed at least one request implemented.
Think about that for a second.
No final decision maker. No real prioritization.
No willingness to say no.
Just: “Everyone gets something”.
“Everyone gets something.”
Here’s the result.
- Opportunity Object – 350 fields with only 25 at meaningful utility (>10% Use)
- Lead Object – 115 Fields with only 15 at meaningful utility (>10% Use)
- Duplicate text fields collecting the same information
- Identical values tracked multiple ways because departments preferred different wording
- Aspirational fields users “should fill out”
- Context fields leadership thought would be useful later
Nobody used them.
People skipped everything non-required., like they always do.
When I looked at the org I knew immediately utility was low.
Not opinion, just operational fact.
The strangest part was that removing useless fields was a political land mine.
Leadership defended clutter because it honored the committee’s work.
The Pattern Behind It
Groups Protect Feelings Better Than Systems
That’s the pattern.
Committees optimize for fairness, participation, and avoiding friction.
Useful CRMs optimize for simplicity, speed, adoption, and prioritization.
Those incentives clash heavily.
The Common Mistake
Mistaking Participation For Progress
This is the mistake.
People believe that more involvement creates better outcomes.
It sounds reasonable.
In reality more involvement produces slower systems and worse decisions.
The committee leaves feeling productive.
Workers inherit complexity.
What Smart Buyers Do Instead
Your CRM absolutely needs structure.
It just doesn’t need a standing committee whose primary function is avoiding uncomfortable prioritization.
Smart companies create lightweight systems:
- Structured Roadmap – Quarterly themes and known priorities.
- Objective Prioritization – Use scoring methods ($100 Test, RICE) that reduce subjectivity from the process.
- Use One Process For Requests – One place. One intake method. No side channels.
- Accept Prioritization – The uncomfortable part is that someone has to lose. If everything is a priority then nothing is.
Closing Thought
Salesforce Governance Committees do not produce useful systems.
At best they create a recurring schedule for introducing clutter.
At worst they become socially acceptable ways to avoid prioritization.
People leave feeling heard while the CRM becomes heavier and heavier.
If your Salesforce environment feels bloated, political, or impossible to simplify creating an unstructured governance committee will not help.
If you’re stuck in that cycle and want help untangling it, let’s talk.
We’re comfortable helping you flesh out what really matters.
Ironically, that’s usually where better systems start.