Design Ways to Help Field Service Workers Love Their Jobs More
![To represent Field Service workers: Illustration of man gripping a laptop in one hand and a large red heart floating above his other outstretched arm. Background includes floating tiles representing data, calendar, email, text.](https://www.salesforce.com/blog/wp-content/uploads/sites/2/2023/03/field_service_happy.png?w=889)
Here are 5 tips for how privacy, inclusion, safety, and autonomy can improve job satisfaction for field service workers.
There are about 23.5 million field service workers worldwide, and 86% of decision makers at firms with a field service team say it’s critical to scaling their business. And yet, even among high performing organizations, only 57% of field service workers say the technology they use drives job satisfaction.
With this data from the field service trend report in mind, we wanted to understand what was missing — and how design choices could help close the gap. To find out, we interviewed 12 field service experts and 10 field service workers and managers. It turns out that job satisfaction is tied to four indicators: privacy, inclusion, safety, and autonomy.
Innovate with intention
Technology has the power to transform our world for the better. We believe ethical and inclusive design, development, and use of technology is a core business imperative. Let’s build this world together.
![](https://www.salesforce.com/blog/wp-content/themes/salesforce-blog/dist/images/offer-block/offer-illustration-layout-one.png)
![](https://www.salesforce.com/blog/wp-content/themes/salesforce-blog/dist/images/offer-block/offer-accent-layout-one.png)
![](https://www.salesforce.com/blog/wp-content/themes/salesforce-blog/dist/images/offer-block/offer-cloud-layout-one.png)
Practice inclusive design in field service management
Based on these findings, we drafted five principles to help guide how Salesforce designs and deploys our software. These principles also provide a roadmap for how organizations can practice ethical and inclusive field service management by making strategic design choices:
1. Prioritize safety for every stakeholder
Leaders are deeply concerned about the physical safety of their field service workers – whether a job site is to code or the worker has sufficient personal protective equipment (PPE), for example. But are you considering the psychological safety of your workers and customers?
One technician told us that she’d walked into a home where drug paraphernalia was exposed, and the resident was inebriated. It turns out that a prior technician had noted a similar situation, but that information wasn’t relayed to the new technician until she checked in at the job site.
Design strategy considerations:
- Give technicians access to notes and warnings from prior appointments ahead of time.
- Provide a mechanism field service workers can use to flag that they’re in a potentially unsafe situation.
- Post-appointment, reward workers for documenting information. Safety implications — limited cell signal or the presence of a guard dog, for example – are important to note. Allow them to request to not be sent to that location in the future.
- Consider asking customers if they’d be happy to be matched with that tech in the future.
2. Respect worker mastery and autonomy
Field service workers, more than any other service worker, report a sense of accountability to customer satisfaction. They also deeply value the flexibility and autonomy of field work. Being over-prescriptive in how they do their work, or withholding important information about a job or their schedule has a negative effect. It increases the risk of attrition.
Design strategy considerations:
- Recognize field service workers for who they are: customer-facing representatives of your organization at the doorstep.
- Consider giving your field workers the opportunity to “score” flexibility points that let them bypass workflows, update knowledge articles, and see more of their schedules (if you drip feed schedules).
- Limit the use of tools that lead to micromanagement and undermine worker autonomy.
3. Ensure your metrics are meaningful and reasonable
Customer satisfaction scores (CSAT) is a tidy metric for field service leaders. But most of the workers we spoke with said that it’s negligible since so few end customers respond to surveys. They also told us they spend significant time researching and prepping for appointments, and documenting appointment outcomes, but often feel this work “doesn’t count.”
Design strategy considerations:
- Find ways to reward the ancillary tasks that don’t show up in traditional metrics.
- Recognize and incentivize – it needn’t be monetary! – the time field service workers spend upskilling and training their colleagues.
- Routinely evaluate what you measure and why, and include technician perspectives when designing new metrics and dashboards.
4. Deploy technology to meet your field service workers’ needs
The mobile workers we spoke to said the most important tool they need is the right information at the right time. That may mean knowing what assets are available and in what location. It could be access to knowledge articles about a particular site or project. Regardless, the goal should be to reduce friction and increase efficiency for your workforce.
Design strategy considerations:
- Provide a “single source of truth” that displays the right information at the right time can help technicians complete their jobs smoothly. That leads to greater job satisfaction.
- Design a knowledge base that’s easy to access and easy to create. Tools like Virtual Remote Assistant can aid knowledge transfer between established workers and newer ones.
- As you begin to deploy automated worker assignments, be sure to test your deployment for unintentional biases and risks to upskilling opportunities.
5. Protect privacy and personal data at the source
Field service leaders shared that if their crew or the union thought they were tracking them, they’d all leave tomorrow. The technicians we spoke to said they don’t mind location tracking. But they want to know when it’s happening and that it’s not a form of micromanagement. Customers have expectations of privacy when a technician is on site, too.
Design strategy considerations:
- Consider what’s necessary for workers to get the job done. For example, do customers need an en-route technician’s precise location or would a 500-meter radius be sufficient?
- Be transparent about when and why you’re logging technician location. Consider automated status changes to reduce tracking while helping to protect worker safety.
- Limit the customer data you collect, and apply data retention policies to sensitive information such as gate codes and signatures.
Explore AI for Field Service
AI has the potential to optimize a wide variety of field service tasks from knowledge and asset management to scheduling.
![](https://www.salesforce.com/blog/wp-content/themes/salesforce-blog/dist/images/offer-block/offer-illustration-layout-one.png)
![](https://www.salesforce.com/blog/wp-content/themes/salesforce-blog/dist/images/offer-block/offer-accent-layout-one.png)
![](https://www.salesforce.com/blog/wp-content/themes/salesforce-blog/dist/images/offer-block/offer-cloud-layout-one.png)
Designing your field service organization for trust and transparency – and to drive greater worker happiness – will improve job performance. It will also accelerate the value of every field service worker’s frontline interaction with customers. Plus, you’ll be prepared to navigate market challenges, like demographic shifts and emerging trends in field service. No matter what comes your way, you have a process that you know works – for workers, for consumers, and for your business.
With contributions from Kim Campbell and Ananya Karthik.