Salesforce implementations are often framed as digital transformation initiatives. The language focuses on platforms, integrations, dashboards, AI and automation. Yet when Salesforce deployments struggle to deliver value, the cause is rarely technical. The real issue is usually that organisations have not defined what the future workforce is meant to look like before locking that future into a system.
After more than 23 years working across 32 plus countries on workforce strategy, systems change and capability development, this pattern is consistent. Salesforce works best when organisations treat it as a workforce transformation project that happens to be enabled by technology.
This is exactly why the Know what you want step sits early in my TAKE ACTION system. It exists because organisations repeatedly skip the hard work of defining their future workforce before they build the system that will shape how work is done.
Field service examples show the workforce issue clearly
Salesforce itself acknowledges that workforce planning is critical to Field Service success. Its Future Workforce Planning content highlights labour availability, skills gaps and job design as major constraints on performance, even when the technology is sound
https://www.salesforce.com/in/service/field-service-management/future-workforce-planning/
Real world examples reinforce this. APA Group, a major Australian energy infrastructure organisation, deployed Salesforce Field Service across hundreds of field workers. This was not treated as a simple mobile rollout. APA redesigned technician roles so senior staff focused on complex work while digital tools supported junior technicians. The organisation reduced unnecessary site visits by approximately 12,000 per year and achieved a reported 15 percent return on investment. Salesforce worked because the workforce model was deliberately redesigned to match the system
https://www.salesforce.com/au/blog/ai-makes-field-service-better/
Contrast this with a home automation and safety services company that implemented Salesforce Field Service Lightning to standardise operations. The CRM build assumed a future state where technicians captured data consistently and followed structured workflows. In practice, adoption lagged early on because technician roles, responsibilities and performance expectations had not been updated beforehand. Salesforce surfaced workforce misalignment that had previously been hidden in manual processes
https://cloudbelive.com/case-study-salesforce-field-service-lightning-for-a-home-automation-safety-services-company/
A further Australian example comes from Girikon’s Salesforce Field Service customisation for an insurance restoration firm. The organisation had Salesforce in place but relied heavily on manual workarounds. Automation only delivered value once responsibilities for data quality, case ownership and technician input were clarified. Salesforce did not solve the workforce problem. It made it visible
https://www.girikon.com.au/blog/casesstudy/salesforce-field-service-customisation-case-study/
Retail CRM examples reveal role design gaps
Retail Salesforce implementations frequently promise better customer insight and sales performance. What they actually expose is whether frontline roles have evolved to match those expectations.
Pletatech’s Salesforce retail implementation case studies show that retailers struggled when store teams were expected to act on CRM insights while still being measured on transaction speed and volume. Where retailers redefined roles, updated KPIs and invested in capability development, Salesforce adoption improved markedly
https://pletratech.com/salesforce-implementation-case-studies-for-retail/
Salesforce partner case studies collected through Featured Customers show a similar pattern. Organisations that treated CRM as an extension of existing job design saw limited uplift. Those that used Salesforce as a catalyst to redefine frontline work reported stronger engagement and measurable outcomes
https://www.featuredcustomers.com/vendor/salesforce/case-studies
Not for profit and community services examples make the workforce reality unavoidable
Salesforce Marketing Cloud implementations in non-profit organisations highlight workforce planning challenges because resource constraints leave little room for inefficiency.
Datamatics’ Salesforce Marketing Cloud implementation for a non-profit organisation demonstrates this clearly. Success depended on defining who owned communications strategy, who executed campaigns and who interpreted insights. Salesforce enabled scale only after roles and decision rights were clarified
https://www.datamatics.com/resources/case-studies/salesforce-marketing-cloud-implementation-for-non-profit-organization
Broader Salesforce government and community service case studies in the Asia Pacific region show similar dynamics. CRM platforms that span case management, citizen services and reporting require clarity between case workers, service agents and policy teams. Without workforce redesign, automation increases workload rather than reducing it
https://gpscasestudies.salesforce.com/regions/apac
In the United States, AnaVation, a government contractor operating on Salesforce’s secure platform, used Salesforce to redesign how program teams collaborated and managed compliance. The platform removed repetitive manual work, but only because workforce responsibilities were reshaped to focus on higher value activities
https://www.salesforce.com/customer-success-stories/anavation/
Professional services CRM implementations surface hidden assumptions
Custom Salesforce CRM implementations in professional services frequently reveal overlapping roles and unclear accountability.
Daffodil Software’s custom Salesforce CRM case study shows how automation stalled until leadership clarified account ownership and process responsibility. Salesforce exposed workforce ambiguity that technology alone could not resolve
https://www.daffodilsw.com/case-study/custom-saleforce-crm-implementation/
Penrod’s Salesforce case studies consistently reference organisational alignment and operating model clarity as prerequisites for CRM success, reinforcing that workforce design decisions must precede configuration
https://penrod.co/resources/salesforce-case-studies/
Why ‘Know what you want’ is a hard capability
In the TAKE ACTION system, Know what you want is not just a visioning exercise. It is a key step in the strategic workforce planning discipline.
It requires organisations to define their future preferred workforce picture in practical terms. Which functions and roles will grow or decline. What skills and capabilities will matter in three to five years. How work will be shared between people, platforms and automation. Without this clarity, Salesforce implementations hard code outdated assumptions into digital systems.
Strategic foresight strengthens this step by testing workforce assumptions against plausible futures. Skills shortages, AI augmentation and changing customer expectations all shape whether today’s role design will still work tomorrow.
Research into skills based workforce planning shows that organisations using foresight informed approaches are more resilient and adaptive:
https://inop.ai/real-world-case-studies-of-skills-based-workforce-planning-success/
McKinsey’s work on superagency reinforces that digital tools only unlock value when people are enabled to make better decisions:
https://www.mckinsey.com/capabilities/tech-and-ai/our-insights/superagency-in-the-workplace-empowering-people-to-unlock-ais-full-potential-at-work
The real output is a Strategic Workforce Plan
The tangible outcome of TAKE ACTION should be a Strategic Workforce Plan that informs Salesforce design decisions.
This plan defines future workforce structure, capability priorities by function, workforce risks and transition pathways. When it exists, Salesforce becomes an accelerator. When it does not, training and change management are expected to compensate for structural issues technology cannot fix.
Salesforce does not fail organisations. It reflects them.
It reveals unclear roles, misaligned incentives and outdated workforce assumptions. The TAKE ACTION system exists to ensure organisations are ready for that reflection.
Know what you want is not optional. It is the capability that turns Salesforce from a system into a strategy.