The latest SF Ben Salesforce Admin Survey reveals a pattern that should concern every organization running Salesforce: Complexity is increasing. Expectations are rising. Risk is accumulating.
According to the survey, 58.6% of respondents agree that Salesforce is becoming increasingly complex to work with, while 53.1% believe too much is being expected of Salesforce Admins. At the same time, 22.3% of Admins report being less satisfied in their role compared to 12 months ago.
These are not isolated frustrations. They are symptoms of broader trends that are reshaping how Salesforce teams operate. The danger is that many of these issues develop gradually. Technical debt builds one shortcut at a time. Security gaps emerge through years of permission changes. Admin overload becomes normalised. By the time the impact is visible, the cost of fixing it is often far greater than the cost of prevention.
Here are five of the most dangerous trends currently affecting Salesforce organizations, why they happen, and the warning signs you should be paying attention to.
1. Technical Debt Is Becoming Everyone’s Problem
Technical debt remains the number one challenge facing Salesforce Admins, with 56.3% of our survey respondents identifying it as their most difficult task.
While many organizations acknowledge the problem, very few appear to have it under control. Nearly half of respondents (47%) describe technical debt as moderate and manageable, but a further 31% report high or very high levels that regularly slow down or materially impact their work. Only 2% consider their org clean and well-maintained.
That statistic alone should be a wake-up call. Technical debt is often viewed as a purely technical issue, but in reality, it is an organizational risk. Every undocumented automation, redundant field, abandoned integration, and rushed implementation makes future change harder, slower, and more expensive.
Larger organizations appear to be carrying the heaviest burden. Enterprise and mid-market companies report the highest levels of severe technical debt, reflecting years of accumulated complexity and historical decisions.
Perhaps most concerning is the confidence gap. While 44% of advanced admins feel fully confident identifying and addressing technical debt, only 13% of entry-level admins feel the same. More than 40% of newer admins either lack confidence or are unsure of their ability to tackle debt effectively.
This creates a dangerous cycle. The people most likely to inherit technical debt are often the least empowered to challenge or resolve it.
Early Warning Signs
- Changes are taking longer to deliver than expected.
- Teams are afraid to touch existing automations.
- Documentation is outdated or non-existent.
- Similar functionality exists in multiple places.
- Every new project begins with weeks of investigation to understand existing configurations and dependencies.
Why It Happens
Technical debt rarely appears because teams do not know what needs fixing. In fact, respondents overwhelmingly identified dedicated cleanup and refactoring time (62.17%) as the biggest factor that would help reduce debt.
The issue is prioritization. Organizations continuously fund new features while postponing maintenance. Eventually, the maintenance bill arrives anyway.
2. Security Is Still Being Treated as Someone Else’s Responsibility
Security management emerged as one of the most significant capability gaps across the Salesforce Admin ecosystem.
What makes this trend particularly dangerous is that it is not limited to inexperienced admins. The survey shows substantial representation from both intermediate and advanced admins, suggesting security remains a cross-experience blind spot.
This matters because Salesforce increasingly stores some of an organization’s most sensitive customer, operational, and commercial data. As organizations grow, permission sprawl becomes almost inevitable. Users accumulate access over time through new roles, profiles, permission sets, and custom configurations. The result is often over-permissioning without anyone realizing it.
Awareness of Salesforce’s Shared Responsibility Model remains surprisingly low. Although awareness has improved compared to previous years, 53.8% of respondents still report being unfamiliar with it.
This is significant because the model makes a clear distinction: Salesforce secures the platform, while customers are responsible for securing their data, access controls, and configurations. When something goes wrong, accountability does not sit with Salesforce.
The survey also revealed weaknesses around both the Principle of Least Privilege (PoLP) and broader modern security practices. Only 20% of respondents report enforcing PoLP very effectively, while more than one-third either enforce it only partially, provide broader access than necessary, or are unsure of their approach.
Awareness of Zero Trust security is similarly limited. While 16.7% of respondents describe themselves as very familiar with the model and 30.8% are somewhat familiar, more than half either have not applied it in practice (25.5%) or are not familiar with it at all (27%). Together, these findings suggest that many organizations are still relying on traditional access models despite growing complexity and increasingly sophisticated security threats.
Early Warning Signs
- Users have access “just in case.”
- Permission reviews happen only after incidents occur.
- No one can confidently explain who has access to what.
- Security ownership is unclear.
- Former project permissions are never removed.
Why It Happens
Security governance often loses out to speed and convenience. When a user needs access urgently, granting broader permissions is usually faster than carefully applying least-privilege principles and dealing with the inevitable follow-up requests.
Individually, these decisions seem harmless. Collectively, they create permission sprawl, where users accumulate access over time, and few people have a clear picture of who can see what. By the time an audit, compliance review, or security incident exposes the issue, the cleanup effort is often substantial.
3. AI Adoption Is Moving Faster Than Trust
AI is rapidly becoming part of the Salesforce conversation, but the survey suggests many organizations are not fully comfortable with the pace of adoption.
Security concerns are widespread, with 58% of admins expressing serious concerns about AI-related risks.
Perhaps more revealing is the biggest barrier to successful AI adoption: trust.
Twenty-nine percent of respondents identified trust as the primary obstacle, ahead of skills and knowledge (23%), capacity and resources (17%), and cost (16%).
This finding highlights an important reality. The challenge is no longer access to AI tools. The challenge is confidence.
Organizations want to know how data is being used, how outputs are generated, who is accountable for decisions, and what governance frameworks need to be in place.
Interestingly, trust concerns appear consistently across organizations of all sizes. This is not a small-business problem or an enterprise problem. It is a universal challenge.
Early Warning Signs
- AI tools are being used without formal governance.
- Teams cannot explain where AI-generated outputs come from.
- Data access policies have not been updated for AI use cases.
- Employees are experimenting with AI without clear guidance.
- Leadership enthusiasm exceeds organizational readiness.
Why It Happens
Technology adoption is often treated as a technical initiative. AI is different.
Successful adoption depends just as heavily on people, processes, governance, and education as it does on the technology itself. Organizations focusing exclusively on tooling may find themselves introducing risk faster than they create value.
4. The Salesforce Admin Role Is Becoming Unsustainably Broad
For years, Salesforce Admins have been described as wearing many hats. The survey suggests those hats may now be turning into an entire wardrobe.
When asked which responsibilities should be shifted away from Salesforce Administrators, respondents most frequently identified business analysis (44.2%), followed by project management (40.4%) and user training and documentation (37.3%).
The message is clear: many admins feel responsible for work that extends far beyond platform administration.
At the same time, the technical expectations placed on admins continue to rise. Modern Salesforce Administrators are increasingly expected to understand software engineering principles, build and maintain complex Flow automations, troubleshoot integrations, participate in release management processes, and, in some organizations, even understand or work alongside code. As Salesforce evolves, the gap between what many organizations think an admin does and what the role actually requires continues to widen.
This trend aligns closely with the finding that 53.1% of respondents believe too much is being expected of Salesforce Admins.
The survey also reveals where teams feel the pressure most acutely. When asked what role they would hire first if budget were available, the most common answer was a developer (25.11%). This suggests many organizations are already feeling the strain of asking admins to fill technical capability gaps that would traditionally sit elsewhere in a delivery team.
The result is predictable – admins spend more time context-switching between competing responsibilities, strategic work gets pushed aside by operational demands, and job satisfaction suffers. It is perhaps no surprise that 22.3% of respondents report being less satisfied in their role than they were 12 months ago.
Early Warning Signs
- Admins are acting as project managers, trainers, analysts, and support teams simultaneously.
- Strategic work is constantly interrupted by operational requests.
- Backlogs continue growing despite increased effort.
- Platform improvement work is repeatedly postponed.
- Hiring requests consistently focus on filling gaps around the admin role.
Why It Happens
Many organizations still view Salesforce Administration as a single-person function rather than a team capability. At the same time, the Salesforce platform itself has continued to evolve at pace. What was once a relatively contained CRM administration role now spans a rapidly expanding ecosystem of automation tools, integrations, development patterns, and AI-driven features. In practical terms, Salesforce today is significantly more complex than it was even 10 years ago.
The result is an environment where responsibility grows faster than support structures, leaving admins to absorb increasing technical and operational load without a clear redistribution of work or investment in additional specialist roles.
5. DevOps Maturity Is Not Keeping Pace With Platform Complexity
Despite years of discussion around DevOps, many Salesforce organizations remain heavily reliant on traditional deployment methods.
Change Sets continue to dominate, with 41.6% of respondents using them as their primary deployment mechanism.
More mature approaches remain comparatively limited. Third-party DevOps tools account for 21.6% of respondents, while only 12.7% use SFDX with CI/CD pipelines. Adoption of DevOps Center remains low at 4.5%.
The risk is not simply about tooling. It is about operational resilience.
Modern Salesforce environments contain increasingly interconnected automations, integrations, metadata dependencies, and AI-powered functionality. As complexity grows, deployment practices that once felt sufficient become increasingly fragile.
The survey also revealed that 10% of respondents still make changes directly in production!
While newer admins are most likely to engage in this behaviour, the fact that it still exists at all highlights ongoing governance challenges.
Early Warning Signs
- Production fixes are common.
- Deployments require manual validation every time.
- Rollbacks are difficult or impossible.
- Teams avoid deployments because they feel risky.
- Changes depend on individual knowledge rather than documented processes.
Why It Happens
The biggest barrier to DevOps adoption is not resistance, but capability.
Nearly two-thirds of respondents (64.1%) cite a lack of formal DevOps training or experience as the primary obstacle. Tool access and Salesforce metadata complexity follow closely behind.
Organizations often expect DevOps outcomes without investing in the skills needed to achieve them.
A Simple Prioritization Framework
Not all of these risks will present themselves equally in every Salesforce organization. The challenge is that most teams are dealing with all of them at once, often with limited capacity and competing priorities.
A more practical way to approach prioritisation is to evaluate each risk through three lenses: impact, trajectory, and constraint.
1. Where Is the Risk Already Causing Business Impact?
Security gaps, technical debt, and deployment instability tend to sit at the top of this list because they directly affect data integrity, delivery speed, and operational continuity. If a problem is already slowing delivery or increasing operational risk, it cannot remain a background task.
2. Which Risk Is Accelerating the Fastest?
Some issues do not stay static. Technical debt accumulates with every release cycle. Permission sprawl expands as teams grow. Admin overload increases as more responsibility is layered onto the same role. These are compounding problems, not linear ones, and delaying action typically increases remediation costs.
3. What Is Actively Blocking Future Capability?
This is where strategic initiatives often stall. AI adoption, for example, is already constrained by trust, skills, and governance gaps in the ecosystem. Similarly, outdated deployment approaches or unclear ownership models can become structural blockers to DevOps maturity and scalable delivery.
When viewed together, these three dimensions help distinguish between issues that are merely inconvenient and those that will materially limit the organisation’s ability to scale Salesforce effectively. In most cases, the highest priority sits at the intersection of immediate impact, rapid deterioration, and strategic blockage.
Final Thoughts
None of these trends emerged overnight. They are the result of years of platform growth, expanding business reliance on Salesforce, and evolving expectations of the professionals who support it.
The encouraging news is that the survey data also shows that most admins understand the problems. They know technical debt requires dedicated cleanup time. They recognize the need for stronger security governance. They understand the importance of role clarity and better deployment practices.
The challenge is not awareness. The challenge is creating enough organizational support, capacity, and prioritization to address the risks before they become crises.
The most dangerous trends in Salesforce are rarely the ones everyone is talking about. They are the ones organizations have quietly learned to live with.
For more insights into the Salesforce Admin role, check out my top 10 insights from the survey or download the full survey now!
