Admins / Career

Most Salesforce Requests Aren’t Salesforce Problems

Henry Martin

By Henry Martin

Someone reports that Salesforce isn’t working; a stakeholder requests a new feature; a manager complains that a report isn’t giving them the numbers they expected. 

Salesforce Admins will be familiar with these complaints, and the natural response might be to investigate the org and find out what needs changing. But the problem might not be Salesforce at all. From conflicting definitions to poor data ownership, some of the biggest challenges facing admins today need more than just a clever configuration fix. 

Resist the Urge to Find Salesforce Solutions

In Salesforce’s own words, the advancement of AI means that admins are not just system builders, but “relationship builders and governors of behavior”.

Kate Lessard, Lead Admin Evangelist at Salesforce, wrote in a March 2026 blog that an ideal admin/stakeholder relationship consists of stakeholders: 

  • Knowing that you understand their work.
  • Feel heard before solutions are proposed.
  • Trust your execution and your recommendations.
  • See you as a true strategic partner.

In order to achieve these “lofty goals”, she recommends putting demos aside and asking questions so you can better understand processes and reveal pain points, so you can find quick wins and build trust.

READ MORE: Connected App Warnings Return as Salesforce Disables Two Integrations

“As admins, it’s really easy for us to see a problem and inherently know how we would fix it through configuration, so this step can be challenging,” she says. “It isn’t about us solving the problem – it’s about listening and collaborating to achieve the desired end state or dream solution!”

Kate says that, as you discover, you should resist the temptation to find a Salesforce solution to something, and instead be mindful of turning technical language into business outcomes. 

“Since admins sit between technology and business, an essential way to build trust is to build understanding by mapping business goals to Salesforce configuration. Trust grows when everyone has a mutual level of understanding,” she said.

Kate also recommends getting experience by shadowing users as they work, through the SABWA (Salesforce Administration By Walking Around) method. 

Last year, Salesforce MVP Steve Molis, aka “Steve Mo,” told SF Ben about ‘SABWA’ – a phrase coined by Mike Gerholdt, from the ButtonClick Admin blog. Steve told us at the time how the term shows the importance of interacting with your stakeholders who are experiencing firsthand the system you are administering. 

He also said it was important for any admin to speak with their users, to find out what their pain points are – and what their likes and dislikes are.

Not a Salesforce Problem, But Still an Admin Problem

What happens when an admin gets a vague report request from different teams that define the same metric differently? If a decision is made and the results are questioned, the issue becomes the admin’s problem. 

Admins aren’t supposed to be the ones deciding which department’s definition of a business metric is the right one, but they do have a responsibility to spot ambiguities before reports are released. 

Founder of RevOps Brief, Israel Akinfenwa, wrote in a March 2026 blog that every CRM he ever inherited had the same problem: Multiple fields that seem to track the same thing. 

READ MORE: Salesforce Launches AI Skills in Agentforce Coworker

Lead Status, Lifecycle Stage, and Contact Status would be three separate fields with three different owners and three different definitions – “none of them agreed upon” – while reps develop personal interpretations and managers run reports from different fields. 

Akinfenwa proposes an annual field audit, along with other measures, to avoid this happening – but the post raises an interesting point for our purposes. Field proliferation can be a problem, but not necessarily a Salesforce one. Fragmented decision-making across departments led to this, and it’s now somehow the admin’s issue to fix. 

A June 2026 article from Gemstone, looking at the IT landscape more broadly, argues that modern reporting tools like Tableau are not the primary obstacle in most projects, but problems like businesses not settling metric definitions, source-system authority, or who is responsible for resolving discrepancies.

Data Quality Requires Data Accountability 

Salesforce’s own material on data cleanliness explicitly connects data quality to ownership and accountability, and advises that keeping things tidy needs to be an ongoing practice, rather than a one-time thing. 

Bearing that in mind, it’s worth considering that a request to fix supposedly unreliable Salesforce data could really just be a request to fix an organizational gap in accountability. A Salesforce request to fix a non-Salesforce problem. 

A Salesforce Admin can implement validation and deduplication, but it needs to be decided what the correct values are and who is looking after them. A one-off clean-up simply won’t fix the problem when the underlying process remains the problem. 

An admin’s technical responsibility for maintaining the platform needs to be distinguished from a business’s responsibility for ensuring accurate data – which is a collective responsibility. You own the controls which protect data quality, but that doesn’t make you the business owner of every last bit of information kept in Salesforce. 

Salesforce professional Alyssa Lefebrve-Beucsher earlier this year told SF Ben about how frustrating it was to get a vague support request. “The messages from users saying ‘Salesforce is broken’ without a screenshot or any steps to replicate kill every admin’s soul!” she said. “Users think we somehow just know what’s going on in the org at all times.”

Her frustrations speak to a broader problem in the Salesforce ecosystem, highlighted in our recent SF Ben Admin Survey. More than half of respondents (53.1%) agreed that too much is expected of Salesforce Admins, while 58.6% said Salesforce itself is becoming increasingly complex to work with.

Admins are becoming the default owners of operational problems, but just because a problem is taking place in Salesforce, that doesn’t mean it’s a Salesforce problem. 

Final Thoughts

Salesforce Admins are problem solvers, and that’s part of what makes them valuable. But being good at fixing things doesn’t necessarily mean it’s your problem to fix. 

Yes, sometimes the right solution is a validation rule, a better data model, or a redesigned workflow – but sometimes it’s getting two departments together in a room so they can agree on what a metric actually means, or who owns a certain process. Knowing the difference will help admins who are expected to configure their way out of problems that the wider business needs to take responsibility for. 

The Author

Henry Martin

Henry Martin

Henry is a Tech Reporter at Salesforce Ben.

Leave a Reply