sarah.nicastro@ifs.com, Author at Future of Field Service

Successful field service management software selection should begin with sharp questions - about strategy, workflows, people, data, adoption, and the future of your service business.

The process of choosing field service management software should not begin with a feature checklist or end with a beauty contest of product demos. The better route to success is to ask sharper questions upfront about what your business is trying to achieve, what your customers expect, what your frontline teams need, and what kind of service operation you are building for the future.

Too often, organizations start the selection process by asking, 'Which platform has the most/newest/coolest features?' That question might serve some purpose, but as the North Star, it will almost always lead teams in the wrong direction. The real question is not whether a platform can do a long list of things; it is whether it can support the way you need to serve customers, enable employees, connect data, and scale over time.

When organizations get software selection wrong, it is rarely because they chose a platform without adequate capability. It is more often because they chose one without enough clarity on the business problems they were trying to solve, the processes they were willing to change, or the outcomes they expected to achieve. Before choosing your next field service management software, these are 15 questions well worth asking.

1. What business problem are we actually trying to solve?

This sounds obvious, but it is remarkable how often software selection starts without a shared answer. Is the primary issue missed SLAs, low technician productivity, poor visibility into work in progress, too much manual dispatching, slow invoice cycles, weak customer communication, or difficulty scaling service profitably? All of those may be true, but they are not equally urgent.

Without alignment on the problem, selection becomes vulnerable to demo theater. Every stakeholder starts looking for something different, and the decision gets driven by whichever feature appears most impressive in the moment. A better approach is to define the top three business outcomes the software must support. That shifts the conversation from 'What can the platform do?' to 'What do we need the platform to help us improve?'

2. Which workflows matter most to our customers and technicians?

Not all workflows are created equal. Some organizations focus heavily on back-office efficiency while underestimating the day-to-day experience of the people actually using the system in the field. Others focus on technician usability but fail to think through what customer communications, escalations, scheduling logic, or service handoffs need to look like.

Start by mapping the workflows that matter most from end to end: case creation, scheduling, dispatch, technician preparation, arrival, work execution, parts usage, documentation, customer sign-off, follow-up, and invoicing. Then ask where the most friction exists today. It’s a recipe for failure to simply digitize bad processes; the goal is to remove friction from the moments that most affect service quality, employee effort, and customer confidence.

3. How complex is our scheduling reality?

Many software decisions look good on paper but unravel when they collide with real-world scheduling complexity. Do you need to consider certifications, skills, territories, travel time, parts availability, customer preferences, entitlements, response windows, job duration variability, or subcontractor capacity? Do dispatchers need automation, optimization, or simply better visibility and control?

This question matters because 'scheduling' can mean very different things depending on the business (and solution). For one organization, it may be straightforward appointment booking. For another, it may be a constantly changing orchestration problem with dozens of constraints. The clearer you are about your actual scheduling reality, the better you can assess whether a platform is fit for your purpose and avoid paying for sophistication you will not use - or buying simplicity when your operation requires something more advanced.

4. What level of mobile and offline capability do our teams really need?

Field service software lives or dies in the field. If a technician has to fight the system to access asset history, capture work details, pull up manuals, record parts consumed, or complete a service report, adoption will suffer – and therefore ROI will miss – no matter how compelling the business case looked in the boardroom.

Ask what your technicians truly need in the moment of service. Do they work in low-connectivity environments? Do they need offline access? How easily can they complete checklists, attach photos, view knowledge, collect signatures, or update work in real time? A system that looks great in a desktop demo but feels clumsy on a mobile device creates immediate resistance - and once frontline trust is lost, transformation is an uphill battle.

5. How will this software help us improve the metrics that matter?

Software selection should be tied directly to measurable business value. Before making a decision, you need to define the metrics that matter most. That may include first-time fix rate, SLA attainment, technician utilization, mean time to repair, repeat visits, schedule compliance, parts consumption, invoice cycle time, or customer satisfaction.

Then ask how the platform will help improve those outcomes in practice. Can managers see where jobs are getting stuck? Can dispatchers intervene early enough to protect service levels? Can field leaders identify coaching needs? Can executives track improvements over time without waiting for a manual report to be assembled? If you cannot connect the software to operational and financial outcomes, it becomes much harder to build alignment and much easier for the investment to be judged on anecdote rather than impact.

In this article, Future of Field Service explores the question, Are We Measuring Today's Service Success on Yesteryear's Metrics?

6. What data do we need to trust - and where does it live today?

Field service depends on context, and context depends on data. Technicians need service history. Dispatchers need resource availability. Managers need performance visibility. Customers expect accurate updates. None of that works well if the data is fragmented, outdated, or buried in disconnected systems.

Before choosing software, get clear on which data is mission-critical. That may include install base details, asset history, warranties, entitlements, contracts, parts inventory, service manuals, customer notes, remote monitoring data, or billing information. Then ask where that data lives today and how reliable it is. A new platform can improve visibility and workflow, but it will not magically solve poor data discipline.

7. Which systems must this platform connect to from day one?

Integration is not a nice-to-have; it is often the difference between a connected service operation and a prettier silo. Common requirements include ERP, CRM, inventory systems, contact center platforms, enterprise asset management tools, billing systems, remote monitoring platforms, and learning or certification systems.

The key is to distinguish between what would be useful eventually and what is essential from the start. Too many implementations get overloaded by trying to connect everything at once without prioritization. Ask which integrations are truly critical to workflow continuity, data accuracy, and user adoption. And do not stop at asking whether integrations are possible. Ask how they are delivered, who owns them, how they are maintained, and how failure or latency is handled.

8. What service delivery model(s) do we need this solution to support?

Some organizations are selecting software to solve immediate dispatch and visibility problems. That is valid. But it is also worth asking whether you are buying only for the service model you have today. Will your business need stronger support for preventive maintenance, remote diagnostics, outcome-based service, condition-based interventions, self-service scheduling, proactive customer communication, or broader asset lifecycle visibility?

Even if those capabilities are not part of phase one, software selection should account for where the business is headed. The most expensive mistake is not always buying the wrong software for today; sometimes it is buying a platform that cannot evolve with the strategy you are already moving toward.

9. Have we involved the daily users of this system early enough?

It is astonishing how many software decisions are made with limited input from the people expected to live in the system every day. Dispatchers, field technicians, supervisors, service leaders, back-office teams, subcontractors, and in some cases even customers will all experience the impact differently. Their perspective matters – and not in the final phases!

One of the best questions a selection! team can ask is not simply, 'Do we like this platform?' but 'How will each user group experience this platform in practice?' Bring frontline voices into the process early. Ask technicians what slows them down today. Ask dispatchers where they need better control or visibility. Ask managers what they struggle to see. Often the most useful selection criteria come from the people closest to the work.

10. What is configurable versus customized?

This is one of the most important questions in any enterprise software decision because it affects flexibility, speed, cost, and long-term sustainability. Many organizations want the software to mirror every current process exactly. That can sound sensible, but it often leads to heavy customization that becomes expensive to maintain and difficult to upgrade – massive barriers to the level of agility most businesses need to maintain competitiveness in today’s landscape.

A healthier stance is to consider what you should adapt in your process and what truly needs to be adapted in the platform. Understand what can be configured by administrators, what requires technical effort, and what would demand custom development. The goal is not to avoid all customization at any cost, but to be intentional, because every custom decision becomes a future ownership decision as well.

11. How will AI and automation be used (and governed)?

AI in field service has moved from abstract buzz to active evaluation, experimentation, and deployment. But that does not mean every AI-driven feature deserves to be switched on simply because it exists. The right question is not, 'Does this platform have AI?' It is, 'Where would AI or automation actually create value in our operation?'

That might be intelligent triage, schedule recommendations, knowledge surfacing, service summaries, anomaly detection, parts suggestions, or next-best-action guidance. Some of those use cases can meaningfully reduce effort and improve consistency. Others may create unnecessary complexity or erode trust if they are poorly applied. It is equally important to ask about governance: where human oversight is required, how recommendations are explained, what data is used, and what guardrails are in place.

For a broader view of the opportunity and myths surrounding AI, see AI Isn’t A Strategy (and 6 Other Realities Service Leaders Shouldn’t Ignore).

12. What organizational change will this require?

Software selection is often treated as a technology project. In reality, it is almost always a change management project with a technology component. A new platform may require changes to dispatching logic, technician responsibilities, job documentation, exception handling, management routines, performance measurement, or customer communication. If those shifts are not anticipated, resistance builds quickly.

That is why it is important to ask early in the process what people and process changes this software will demand. What habits will need to change? What training will be needed? Where will managers need to coach differently? Who will champion the rollout? The strongest implementations happen when leaders are honest about the fact that software is not just being installed, a different way of working is being introduced.

And as Change Only Moves as Fast as Trust is Built makes clear, technology change stalls when trust, engagement, and leadership do not keep pace with the transformation plan.

13. How will we define success in the first 90 days, six months, and 12 months?

Long-term transformation matters, but early clarity matters too. One common mistake is describing success in broad terms while failing to define what progress should look like in practical stages. That makes it hard to generate momentum and easy for stakeholders to lose confidence.

Think in milestones. In the first 90 days after go-live, success may mean adoption, data capture discipline, schedule visibility, and fewer manual workarounds. By six months, the focus might shift to productivity, SLA performance, or work quality. By 12 months, the conversation may expand to customer experience, margin, and scalability. When teams know what near-term and mid-term wins look like, they are much better positioned to achieve them.

14. Can this platform support the service organization we aim to become?

Many service organizations are changing shape. They are expanding geographically, introducing new service offerings, relying on mixed workforces, integrating service more tightly with asset management, or trying to make service a stronger source of revenue and customer loyalty. The question, then, must not only be whether the platform can support today's operation but also whether it can support growth, diversification, and evolution without forcing a major rethink every time the business changes.

Software should enable your trajectory, not constrain it. If the platform fits your current state but creates friction every time your model evolves, the cost shows up later - often in more manual work, more brittle integrations, and a growing gap between strategy and execution.

15. Who will own the outcome internally?

This final question is often overlooked because teams assume ownership is obvious. It usually is not. Is this primarily an IT initiative, a service operations initiative, or a broader transformation initiative? Who is accountable for business outcomes, not just technical delivery? Who makes trade-off decisions? Who keeps the effort anchored to value when implementation details start to take over?

The most successful software decisions usually have clear executive sponsorship, a strong operational owner, and cross-functional alignment across service, IT, finance, and any other critical stakeholders. Choosing software is important, but owning the result is what determines whether that choice ultimately creates value.

Final Thought

Choosing field service management software is much more than searching for the platform with the most impressive demo. It’s an opportunity for a disciplined exercise in understanding your business, your customers, your workforce, your data, and your ambition.

The best decision does not come from asking, 'Which product looks strongest?' It comes from asking, ‘How well do we know our business’s identity, vision, and needs?' Organizations who take the time to answer those questions tend to choose better, implement better, adopt better, and realize value faster, because they have built the foundation for success before the software ever goes live.

While often referred to specifically from a software perspective, Field Service Management (FSM) is the combination of processes, operating models, and software that organizations use to coordinate work performed at customer locations, remote sites, or in the field. It covers everything from receiving a service request to dispatching the right technician, ensuring parts are available, completing the job safely and efficiently, and capturing the outcomes for billing and continuous improvement. Done well, FSM aligns people, processes, and technology so the right technician—with the right skills, parts, and context—arrives at the right place at the right time.

FSM is more than a scheduling function; it is an orchestrated discipline that connects strategy, execution, and data. This guide explains what FSM entails, how it delivers measurable value, common pitfalls to avoid, and practical steps to implement or upgrade your approach. It also highlights emerging trends shaping the next generation of field operations and answers frequently asked questions to help you build a strong business case and plan for change (which is a must).

What Is Field Service Management?

Field Service Management (FSM) is the end-to-end orchestration of off-site service work. It brings together strategy, standardized processes, and digital tools to manage the full lifecycle of field operations—request intake, triage and prioritization, work order creation, scheduling and dispatch, on-site execution, customer confirmation, and invoicing—along with the data and feedback loops needed to continuously improve performance. If you are asking what field service management is in practical terms, think of it as the operating system that keeps people, parts, assets, and commitments in sync across dispersed work.

Organizations in sectors such as utilities, telecommunications, manufacturing, medical devices, HVAC, building and facilities services, construction, energy, transportation, and the public sector rely on FSM because their core work happens at customer premises or distributed locations rather than a single facility or group of internal locations. In these dispersed and service-centric environments, visibility and coordination are paramount: every minute of technician time, every mile driven, and each part consumed affects customer experience, response times, and profitability.

Core Components of FSM

Work order management: Create, assign, track, and close jobs with clear scopes, entitlements, and documentation.
Scheduling and dispatch: Match skills, certifications, location, availability, SLAs, and parts readiness to demand in real time.
Mobile field applications: Provide technicians with offline-capable access to work details, manuals, checklists, and collaboration tools.
Inventory and parts: Manage van stock, depots, and reverse logistics to make sure the right parts are on hand and costs are controlled.
Asset and installed base management: Maintain accurate records of equipment, configurations, service history, and warranties.
Contracts, warranties, and entitlements: Enforce service terms, coverage, and billing rules to protect margins and ensure compliance.
Invoicing and field payments: Capture time, materials, and approvals to accelerate cash collection and reduce leakage.
Customer communications: Provide appointment confirmations, arrival notifications, and digital service reports for transparency.
Analytics and reporting: Track KPIs, identify bottlenecks, and guide decision-making with operational data and trend analysis.
Safety and compliance: Embed procedures, risk assessments, permits, and digital approvals to protect people and operations.

The scope of FSM extends beyond single visits to include preventive and predictive maintenance programs, recurring services, seasonal peaks, subcontractor coordination, and SLA management. Integration with ERP, CRM, supply chain, and enterprise asset management (EAM) systems is essential to keep data in sync and prevent handoff gaps. Often, FSM also connects to IoT sensors that flag anomalies or performance drift, enabling proactive interventions before failures occur.

How FSM Has Evolved

If you can believe it, field service once depended on paper forms, whiteboards, and phone or radio calls. That manual model made it difficult (sometimes impossible) to see technician status, track parts accurately, or consistently meet response times and first-time fix targets. As mobile devices, GPS, and cloud platforms matured, FSM shifted toward digital scheduling, route optimization, and electronic data capture. Today, intelligent scheduling engines, predictive analytics, and connected assets help organizations anticipate demand, allocate resources precisely, and deliver consistent service experiences across regions and teams that offer competitive differentiation and build brand loyalty.

For examples and perspectives on this evolution, explore articles and podcasts at Future of Field Service, such as How Field Service Management Has Evolved & What Comes Next.

Why Field Service Management Matters

Service has evolved and so too has modern FSM. It is more than dispatch; it is a lever for efficiency, responsiveness, and profitable growth. Organizations that standardize processes and deploy the right technology typically see higher technician productivity, faster response times, better on-time arrival rates, stronger first-time fix performance, and improved customer satisfaction—while reducing cost-to-serve.

FSM operationalizes these gains at scale through intelligent planning, guided execution, and accurate data capture. Moreover, it positions service organizations to keep pace with customer expectations, deliver more sophisticated service offerings, and recognize the full potential of what service can mean to the business in terms of revenue and profits.

Operational Efficiency and Productivity

Automated scheduling reduces manual effort and optimizes routes to cut travel time and fuel usage.
Skill- and parts-aware dispatch boosts first-time fix rates by ensuring technicians arrive prepared.
Digital workflows and checklists reduce errors and rework, and ensure regulatory and quality steps are followed.
Real-time coordination keeps dispatch, technicians, and customers aligned as conditions change.

Customer Experience and Retention

Accurate arrival windows, proactive notifications, and clear digital reports create transparency and trust.
Faster mean time to repair (MTTR) and consistent service quality support SLA attainment and loyalty.
Higher first-time fix rates reduce disruption for customers and cut the cost of return visits.

Financial Impact and Resource Optimization

Fewer truck rolls and optimized routes lower operating expenses.
Better inventory control reduces emergency orders, write-offs, and carrying costs.
Automated time capture and invoicing accelerate cash collection and reduce leakage.
Data-driven planning balances capacity with demand to scale without a proportional cost increase.

To learn how peers translate efficiency into competitive advantage, see community-driven insights such as Turning Field Data into Service Insight and A Field Service Home Run.

Common Challenges in Field Service Management

Despite the promise, FSM can be difficult to execute consistently across teams, regions, and partners. Many organizations grapple with fragmented tools, inconsistent data, and manual processes that introduce delays and blind spots. These are not only process issues—they are often symptoms of incomplete adoption of field services management software and unclear operating models.

People and Process Friction

Limited visibility into technician availability, skills, and certifications undermines scheduling decisions.
Balancing planned preventive work with reactive break-fix demands strains capacity and SLAs.
Coordinating subcontractors to the same standards as internal teams requires clear processes and shared KPIs.

Technology and Data Gaps

Paper forms or legacy systems impede real-time status updates and slow decision-making.
Disconnected ERP, CRM, inventory, and FSM systems cause parts inaccuracies and billing delays.
Lack of analytics makes it hard to pinpoint root causes of repeat visits or poor utilization.

Overcoming Obstacles

Define a clear operating model with standardized workflows and data governance.
Set KPIs such as first-time fix rate, on-time arrival, MTTR, utilization, and customer satisfaction to guide improvement.
Choose an FSM platform that integrates with core enterprise systems and supports mobile-first, offline-capable work.
Pilot in a focused region or service line, incorporate technician feedback, and iterate before scaling.
Invest in change management: role-based training, clear communications, and leadership sponsorship.

For pragmatic advice on change leadership and adoption, consider the article Leading Through Service Transformation or this podcast about A Tactic That Improves Change Management.

How Field Service Management Works Day to Day

FSM orchestrates a chain of events that starts with demand signals and ends with proven outcomes and financial closure. While every organization tailors the flow to its needs, most follow a common pattern. Under the hood, what is field service management software doing? It structures each step, enforces standards, and provides the data needed to make better decisions tomorrow than you did today.

Typical FSM Workflow

Service request intake: Requests arrive via phone, portal, email, connected devices, or CRM cases.
Triage and prioritization: Urgency, impact, SLAs, and entitlements determine response and coverage.
Work order creation: Scope, skills, parts, safety requirements, and site constraints are captured.
Scheduling and dispatch: Optimization engines assign the best-qualified technician and route.
On-site execution: The technician diagnoses, repairs, calibrates, or installs, following digital SOPs and checklists.
Completion and sign-off: Outcomes are recorded with photos and signatures, and warranties or SLAs are validated.
Invoicing and follow-up: Time and materials flow to billing; feedback, parts reconciliation, and knowledge updates close the loop.

Technology That Enables the Flow

Intelligent scheduling: Weighs skills, travel, SLAs, parts readiness, and customer preferences to optimize assignments and arrival windows.
Mobile apps: Provide job details, asset history, guided workflows, offline access, and collaboration with remote experts.
GPS and telematics: Support live tracking, route optimization, driver safety, and time-on-site verification.
Barcode/RFID scanning: Ensures accurate parts consumption and inventory updates.
IoT and analytics: Trigger predictive work orders and surface KPIs in real time to drive continuous improvement.

Integration Across the Business

ERP/supply chain: Parts availability, replenishment, and cost tracking.
CRM: Customer context, entitlements, and case histories.
HR and learning: Certifications, training records, and compliance enforcement.
EAM and project systems: Coordinating large installs, overhauls, and lifecycle maintenance.

For deeper dives on operational design, explore resources such as How Lean Methodology Impacts Service Transformation.

Implementing Field Service Management: A Practical Guide

Wherever you are on your FSM journey, success hinges on translating business goals into an operating model that your people and technology can execute consistently. The following phased approach helps manage risk and build momentum. Leaders benefit from a structured path that aligns strategy with action and ensures field services management software actually delivers on its promise.

1) Assess and Align

Baseline performance: Evaluate service demand patterns, response times, travel, first-time fix rates, utilization, and SLA performance.
Map systems: Understand current tools, data sources, integrations, and pain points across service, supply chain, finance, IT, and customer support.
Clarify objectives: Define measurable goals such as reducing MTTR, improving on-time arrival, increasing preventive maintenance, or accelerating cash collection.
Engage stakeholders: Align leadership and cross-functional teams on scope, priorities, and success criteria.

2) Design the Target Operating Model

Standardize workflows: Define processes for intake, triage, scheduling, parts, on-site execution, safety, documentation, and closeout.
Establish data standards: Create a common taxonomy for assets, parts, skills, service types, and locations.
Set KPIs and benchmarks: Select metric definitions and targets; ensure reporting can slice performance by region, team, and customer.
Plan change management: Outline training, communications, incentives, and field engagement to drive adoption.

3) Select the Right FSM Platform

Core capabilities: Intelligent scheduling, mobile apps with offline support, configurable workflows and checklists, parts control, asset and installed base management, contract and warranty handling, quoting and invoicing.
Integration readiness: Robust APIs and connectors for ERP, CRM, EAM, HR, and IoT platforms.
Usability and security: Intuitive interfaces for dispatchers and technicians, role-based access, and compliance features.
Scale and analytics: Support for multiple regions and languages, plus operational and customer-facing reporting.
Total cost of ownership: Evaluate licensing, implementation and integration costs, data migration, devices, training, and ongoing support.

4) Implement in Phases

Pilot: Start with a focused region or service line to validate workflows, data models, and scheduling rules.
Refine: Incorporate technician and dispatcher feedback to tune configuration and training.
Scale: Expand to additional regions, business units, or service types with a repeatable playbook.
Optimize: Layer on predictive maintenance, contractor management, and advanced analytics as adoption matures.

5) Enable the Workforce

Role-based training: Provide scenario-based learning for dispatchers, technicians, planners, and managers.
Modern devices: Equip field teams with reliable, ruggedized devices and connectivity options.
Support channels: Offer knowledge bases, in-app guidance, and remote expert assistance.
Continuous feedback: Use ride-alongs, retrospectives, and performance dashboards to spot gaps and celebrate wins.

Implementation Checklist

For lived experiences and tactical advice on implementation, check out resources such as Success Factors for Complex Service and Building a Service Business Case That Sticks.

Measuring Success: Field Service KPIs That Matter

Clear metrics keep teams focused and make it easier to identify where to invest. The most effective FSM programs measure a blend of productivity, customer experience, and financial outcomes. Pairing these measures with field services management software makes performance transparent and improvement repeatable.

First-time fix rate: Percentage of jobs resolved without a return visit. Indicates planning quality, parts readiness, and technician enablement.
On-time arrival rate: Percentage of appointments met within the promised window. Reflects scheduling accuracy and route efficiency.
Mean time to repair (MTTR): Average time from arrival to resolution. Tracks diagnostic efficiency and process friction.
Technician utilization: Productive time as a share of total hours. Highlights scheduling and travel optimization opportunities.
Service level attainment: Adherence to response and resolution SLAs, often by customer tier.
Work order cycle time: Time from request to closure, including handoffs and billing.
Parts usage accuracy: Alignment of planned versus consumed parts, and rate of returns.
Return visits and callbacks: Frequency of repeat work on the same issue within a defined period.
Customer satisfaction (CSAT) and NPS: Signal experience quality and loyalty.
Revenue and margin per job: Links operational performance to financial outcomes.

Use a balanced scorecard and review trends by region, customer, product line, and technician cohort. Combine quantitative KPIs with qualitative feedback from the field and customers to surface root causes and drive targeted improvements. Field service management software supports this rigor by standardizing data capture and surfacing insights in near real time.

For inspiration on assessing KPIs and measuring success, see Measuring What Matters in Service and Don’t Ignore the Green KPIs.

Working With Contractors and Partners

Most service organizations augment internal capacity with certified contractors, especially for seasonal surges, specialized skills, or geographic coverage. To maintain quality and protect the brand, FSM must extend governance and workflows to external partners. This is where field service management software can provide consistent standards and shared visibility across a mixed workforce.

Unified platform: Give contractors controlled access to scheduling, work orders, and documentation.
Shared standards: Apply the same checklists, safety gates, photo evidence, and sign-off requirements.
Credentialing: Validate certifications, training, and insurance before assignment and on a recurring basis.
Performance visibility: Track contractor KPIs alongside internal teams; use scorecards for continuous improvement.
Equitable routing: Factor contractor capacity and SLAs into the scheduling engine to meet commitments at lowest cost.

Explore best practices in articles like A Winning Mindset Around Independent Service Contractors and Partner Ecosystems in Service.

Future Trends in Field Service Management

Emerging technologies and shifting customer expectations are pushing field operations from reactive break-fix to proactive, outcome-oriented service. The most significant advances are coming from automation, AI, and connectivity. As you evaluate how field service management software will change next, focus on how these tools reshape workflows and decision-making rather than chasing features.

Automation and AI at the Core

AI-driven scheduling: Optimization engines weigh skills, travel, SLAs, parts, and customer preferences to improve on-time arrival and reduce costs.
Predictive service: Machine learning models, informed by IoT feeds and historical outcomes, forecast failures and recommend preemptive interventions.
Natural language interfaces: Conversational tools accelerate request intake and give technicians voice access to knowledge and checklists.

Extended Reality and Digital Twins

Augmented reality: Guided workflows and remote expert assistance help resolve complex issues faster, enabling newer technicians to perform advanced tasks under supervision.
Digital twins: Virtual replicas of assets allow teams to simulate repairs, plan interventions, and anticipate impacts before rolling a truck.
Computer vision: Automates routine inspections and quality checks using photos and video, improving consistency and speed.

Connectivity and Collaboration

5G and edge computing: Support richer data transfer—including live video—from remote locations and bandwidth-constrained sites.
Closed-loop service: IoT signals create work orders automatically; FSM orchestrates response; data flows back to design and maintenance strategies.

Business Model Shifts

Outcome-based contracts: Service commitments tied to uptime, throughput, or energy efficiency encourage proactive maintenance and continuous monitoring.
Sustainability metrics: Fewer truck rolls, optimized routing, and circular parts management become standard measures of performance.
Dynamic workforce models: Blended internal and contractor teams operate under unified governance and shared KPIs.

For forward-looking discussions, see Optimization Vs. Amplification and AI Isn’t A Strategy.

Building the Business Case for FSM Modernization

Investing in FSM pays back through cost savings, productivity gains, and stronger customer retention. A compelling business case quantifies improvements and aligns them to strategic priorities. When evaluating options, tie capabilities to specific KPIs and clear operational outcomes.

Quantify the Opportunity

Travel and routing: Estimate reduced miles and time per job; translate into fuel and labor savings.
First-time fix: Model the impact of increasing first-time fix on return visits, parts usage, and customer satisfaction.
Inventory: Project lower emergency orders, improved turns, and reduced write-offs from enhanced visibility.
Cash cycle: Calculate faster invoice creation and days sales outstanding (DSO) reduction from automated capture.
Capacity: Show how utilization improvements enable more jobs per day without additional headcount.

Map Costs and Risks

Software: Licensing or subscription fees and optional modules.
Implementation: Configuration, integrations, data cleansing, and migration.
Enablement: Devices, training, and change management.
Ongoing: Support, enhancements, and continuous improvement.

Tell the Story

Link metrics to business outcomes: Tie KPIs to revenue protection, customer retention, and service profitability.
Highlight compliance and risk reduction: Emphasize safety, audit readiness, and warranty protection.
Share peer benchmarks and case studies: Use credible, industry-relevant examples to build confidence.

For help framing value, explore Unlocking Service Growth and AI’s Impact on Service Value.

FSM FAQs

Here are some frequently asked questions about field service management:

How does FSM differ from Customer Relationship Management (CRM)?

CRM manages customer interactions, sales, marketing, and support cases. FSM executes the operational delivery of field work. While CRM tracks accounts, contacts, and service cases, FSM handles technician scheduling, work orders, parts, on-site workflows, and service completion. Integrated together, CRM provides customer context and entitlements, and FSM orchestrates the work in the field to fulfill those commitments.

Who uses Field Service Management?

Any organization that installs, maintains, repairs, or inspects equipment or facilities at customer locations or distributed sites. That includes utilities, telecom providers, manufacturers and OEMs, medical device companies, HVAC and energy services, building and facilities management, oil and gas, transportation, and public sector field operations.

What are the key metrics in FSM?

Common KPIs include first-time fix rate, technician utilization, on-time arrival rate, mean time to repair (MTTR), service level attainment, work order cycle time, parts usage accuracy, return visits, customer satisfaction (CSAT), net promoter score (NPS), and revenue and margin per job. Monitoring these metrics helps teams identify bottlenecks and target improvements.

Can small and mid-sized businesses benefit from FSM?

Yes. Cloud-based FSM solutions make advanced capabilities available without heavy infrastructure. SMBs benefit from optimized scheduling, digital work orders, mobile apps, and faster invoicing, which lead to more jobs per day, better cash flow, and improved customer experience. As needs grow, these platforms scale to support more users, regions, and features.

How does FSM support compliance and safety?

FSM platforms enforce standardized procedures with digital checklists, mandatory fields, and approval workflows. They can require up-to-date certifications, capture time- and location-stamped signatures, and attach photos for proof of work. Integration with environment, health, and safety systems and training records helps ensure only qualified personnel perform specific tasks and that safety steps are followed consistently.

What is the relationship between FSM and IoT?

IoT sensors provide real-time asset performance data and can trigger service events automatically when thresholds are exceeded. FSM uses these signals to create work orders, schedule the right technician, pre-stage parts, and provide guidance to the field. Over time, the combined data improves failure predictions, maintenance schedules, and equipment design.

How long does it take to implement an FSM solution?

Timelines depend on scope and complexity. A focused deployment for one region with standard workflows may take a few weeks to a few months, including configuration, integrations, data migration, training, and a pilot. Enterprise-wide programs with complex integrations and global processes can take several months to a year or more. Phased rollouts and strong change management accelerate adoption and value capture.

What is the total cost of ownership for FSM?

Total cost of ownership includes software subscriptions, implementation services, integrations, data migration, training, devices for technicians, and ongoing support. Savings typically come from reduced travel and fuel, fewer repeat visits, improved parts management, lower administrative overhead, and faster cash collection. A robust business case maps costs and benefits to specific KPIs and targets.

How do I choose between best-of-breed FSM and an integrated suite?

Consider the complexity of your service mix, the maturity of existing systems, and integration requirements. Best-of-breed tools may offer deeper capabilities for scheduling and mobility, while integrated suites can simplify data flows and governance. Prioritize fit for your operating model, integration readiness, usability for the field, and total cost of ownership.

What are first steps if we are still using paper and spreadsheets?

Start by standardizing basic workflows and data definitions, then pilot a mobile-first, cloud-based FSM for a specific region or team. Focus initial value on scheduling, route optimization, and digital work orders. Use early results to refine processes, build the business case, and expand.

For additional FAQs and practitioner tips, explore the community at Future of Field Service.

Putting It All Together

Field Service Management brings discipline and data to the edge of your business, where technicians represent your brand and outcomes determine loyalty. By aligning operating models with intelligent scheduling, mobile workflows, and integrated systems, organizations can reduce cost-to-serve, increase productivity, and elevate customer experience—while building a foundation for proactive, outcome-based service. For leaders navigating service transformation, the takeaway is straightforward: tools matter, but results come from how you design and run the operation every day.

The path forward is iterative: define standards, digitize workflows, connect data, empower the field, and measure relentlessly. As AI and IoT expand what is possible, the organizations that will excel are those that treat FSM as a strategic capability—one that coordinates people, processes, and technology to deliver results every day. Choosing the right field service management software is part of that journey, but so is governance, change leadership, and a culture that values evidence over assumption.

by Sarah Nicastro, Creator and Editor in Chief, Future of Field Service

Are you one for New Year’s resolutions? I think they can put a lot of pressure on us to feel we need to re-create ourselves and/or set us up to feel we’ve failed when we don’t succeed at the aggressive goals we set. I am a fan, however, of the process of reflecting and setting intentions.

Taking time to reflect allows us to identify what’s working well that we need to be intentional about continuing and making space for, and to define areas we need to focus more on incorporating or evolving. What keeps intentions manageable, I avoid setting too many at one time, I outline specific actions or practices that will help me make progress on each intention, and I allow for a lot of flexibility.

With that in mind, as I reflect on my many conversations with service leaders in 2025 and think about the New Year ahead, I’ve outlined below five intentions I believe service leaders would benefit from setting for 2026.

#1: Fiercely protect your time to think long-term.

The pace of change today is dizzying, and it’s only getting faster. Leaders who fall prey to the trap of constantly prioritizing daily fires over long-term strategy are destined to fail. How will you address your workforce needs for five, 10 years from today? What’s the next phase of your customer value proposition? Where do you need to invest in technology, training, or new talent to support these business shifts? All these questions and many more are ones you must make time to consider, investigate, and plan to address.

#2: Apply the art of storytelling to evangelize how crucial it is to eliminate technology debt and move thoughtfully into the AI era.

Only 28% of respondents from our soon-to-be released Stand Out Service Trends report said that their field service management platform is fully functional and future ready. Meanwhile, customer expectations continue to heighten based on consumer-centric experiences. A service management platform that’s ripe with inefficiencies, that is cumbersome to scale or change, or that is stitched together with functioning but fragile band-aids is not only a ticking time bomb – it’s preventing you from moving into the AI era in a cohesive, scalable manner.

90% of respondents from our Stand Out Service Trends report agree advanced AI will be critical to compete long-term. I cringe thinking about what will happen to the organizations that are too slow to modernize their core systems so that they can add layers of sophistication and automation that are sustainable and value-centered. Let 2026 be the year you apply the art of storytelling to articulate this need in terms that will resonate with your leadership.

#3: Identify how you can improve your 1-1 relationships with your team.

Nearly every leader I speak to is focused on improving how to attract, recruit, hire, and retain talent. And almost unanimously they agree there’s no substitute (and no shortcuts) to strong relationships with the leader they report to. So, in 2026, consider how you can improve the relationships you have with your team. Maybe you need to invest more time in face-to-face. Maybe you realize you should show appreciation more, or in a different way. Maybe you can own the fact that you need to work on listening more to input and acting on feedback. Whatever your specific opportunity is, find a way you know you could improve your 1-1 relationships and put in the effort – I don’t think you’ll regret it.

#4: Set specific goals for human connection (among employees and with customers).

In our busy, often chaotic, and very technology-driven world, we need to be conscious about maintaining human connection. Consider both your teams and the customers you serve – what goals can you set that are specific yet feel realistic to ensure your employees feel part of a team, a community; and that your customers feel seen, heard, and valued? Leaders I speak with agree that while it can be costly to bring together field teams for team building, it’s very worthwhile in their engagement. From a customer perspective, there’s more need than ever to reflect on the experience you’re providing and how you can keep the “people” focus that makes service special.

#5: Invest in yourself.

Last, but certainly not least, consider how you’ll invest in yourself this year. It could be personal growth or development, wellbeing, or just something to make you happy. It’s so easy to show up and give of ourselves, day after day, and (if you don’t hit a point of burnout) realize another year has flown by. Don’t let 2026 be that year – you deserve better (and what you invest in yourself will pay dividends to those around you). Maybe you’ve wanted to take a course but “haven’t had the time.” Maybe you’ve been curious about meditation. Maybe you would really love to take a walk every day at lunch. Maybe there’s a hobby you long ago left by the wayside and have missed ever since. It could be any number of things but do something for you.

By Sarah Nicastro, Founder and Editor in Chief, Future of Field Service

On August 9^th, after 91 years full of life, Dame Stephanie “Steve” Shirley passed away. The life Dame Stephanie led was not only inspiring but forged the future for all women in tech. I learned of Dame Stephanie just this past January, hearing Jake Humphrey of the High Performance podcast speak about her at an IFS event (their interview with her is a wonderful watch). What he shared moved me to order her memoir, Let It Go, on the spot. Reading her story left me moved, awed, and inspired – so much so that I wanted to honor her by sharing some of what stood out to me with you.

Dame Stephanie was a child refugee of the Holocaust – one of thousands of Jewish children fleeing the Nazis that came to Britain as part of the Kindertransport (a British rescue effort in the months preceding World War 2 ). At just five years old, she arrived in the UK and met her foster family. “I was five years old. My nine-year-old sister and I had been travelling for more than two days, on a grim, tearful journey from Vienna. We knew scarcely half a dozen words of English between us, and I, at least, had only the vaguest idea of where we were going and why,” she says in Let It Go. As she describes the impact her early start had on her, she goes on to say, “Without my being fully aware of what was going on or why, a large number of good-natured strangers took it upon themselves to save my life. It took me some years to digest this fact and its implications. But once I had, a simple resolution took root deep in my heart: I had to make sure that mine was a life that had been worth saving.”

I won’t use this space to attempt to retell her entire story; not only could I never do it justice, but it is well worth your time to read Let It Go yourself. But I’ll share just enough to illustrate that it’s evident how seriously she took her resolution. As a student, she showed an interest and promise in math that wasn’t “of the time,” and followed this passion ruthlessly until she fell in love with computers.

As a young adult, Stephanie continues to unfold her education and professional journey while in parallel grappling with the psychological impact of the early experiences of her life. All the while, with grit, she vied for roles that women typically wouldn’t/never had and she succeeds in breaking barriers. She says in Let It Go, “Perhaps my fractured upbringing had given me a sense that, if I wanted to make anything of my life, I needed to take control of it myself. It doesn’t surprise me at all, in retrospect, that some people saw me as pushy. A kinder analysis would be to say that, like all refugees, I had been forced to develop a strong sense of independence.”

Forging a Future for Women in Tech

At age 29, after earning her Master’s degree and marrying her husband, Derek, Stephanie decides to start her own software company. She says in Let It Go, “While I could hardly have been less qualified for the task, I did have the crucial asset of unlimited enthusiasm.” Her company, Freelance Programmers, and son, Giles, were born around the same time. It was shortly thereafter she adopted the moniker “Steve,” a suggestion from her husband since she was likely to get a better response to business outreach if people didn’t realize they were communicating with a woman.

Freelance Programmers (which was later known as FI Group and later still Xansa) was designed around providing jobs to women with children. Dame Stephanie pioneered remote work and flexible working practices, believing firmly that women not only have a place in IT, but don’t need to conform to “standard practices” (often impossible for mothers, especially in the 1960s) to add value or succeed.

Like many entrepreneurs, Dame Stephanie faced tumultuous times with Freelance Programmers but, like she did in all things, persevered. Over time, the company grew to employ 8,500 people and was ultimately valued at almost $3 billion.

As that journey was unfolding, so was Dame Stephanie’s journey of motherhood. Her son, Giles, was diagnosed with severe autism around age 3. She poured herself into understanding his diagnosis, determining how best to meet his needs, and finding him proper care. Sadly, Giles passed away at age 35. Throughout his life and beyond, Dame Stephanie championed and supported related causes, including being an early member of the National Autistic Society and funding many autism projects through her charity, the Shirley Foundation.

In fact, Philanthropy became a huge aspect of Dame Stephanie’s legacy. According to her website, “Dame Stephanie’s life has been dedicated to IT and autism, so it’s in these two specific areas that she chooses to invest her philanthropic energies. She has given away the majority of her wealth, nearly £70 million in total, causing her to be the first person to drop out of the Sunday Times Rich List as a result of her philanthropy.”

This short synopsis is a mere glimpse into her truly amazing story – if you’ve never read her book, Let It Go, I urge you to do so. Her willingness and ability to offer such self-reflection as she documents the different phases of her life, her wise words of advice, her at times unfathomable strength, all make not only a compelling read, but one that will leave a lasting impression on you.

Lessons from Let It Go

Here are a few of my personal favorite quotes from the book:

On selling service/power of listening: “The idea of a service industry – which is what we were – barely existed in those days…Jack Bungard taught me many things, the most important of which was how to sell. He taught me to rein back my instinctive desire to show off my insight and technical expertise and, instead, to listen.”
On flexible work: “We paid people for the work they accomplished rather than the hours they put in. Compared with a conventional company, we were treading our freelancers like adults: trusting them, as intelligent, motivated people, to make the best use of the time available to them in order to achieve the goals that had been set.”
On innovation: “I suspect, however, that the most important factor that shaped Freelance Programmers in its early years was, simply, my naivety. Deep down, I still didn’t know what I was doing. Not knowing what the rules were, I was free to innovate – as, indeed, was everyone else involved.”
On outside-in: “Because I was talking the clients’ language rather than ours, it formed me to see things from their point of view – something that the IT industry is notoriously bad at doing.”
On surrender: “I have struggled all my life with an instinct to hang on to the things that matter most to me, to control and protect them myself. Yet the art of surrender is, I am convinced, a key to many kinds of success- and fulfillment. And many lives are limited by a failure to master it.”
On leadership: “The older I get the clearer it becomes to me that empowerment is the key to business success...It is people, not assets, that make the modern business world go round. It is their creative drive that sparks new enterprise and innovation, their professionalism and dedication that ensures quality, their energy that makes things happen – and, always, it is teamwork that carries forward the vision. Yes, by all means lead from the front, if that is your style, but always remember that leadership is nothing unless those who are led give the best of themselves. Like love, leadership is, at its best, about giving, not taking.”

If I were able, I’d say: Thank you, Dame Stephanie, for your inspiration. For the hard work you tirelessly took on so that all the women who’ve come after you can walk a different path. For your generous giving. May you rest in peace knowing you most certainly lived the definition of a life worth saving.

Episode 320

In this episode of UNSCRIPTED, host Sarah Nicastro shares key takeaways from last week’s Future of Field Service Leaders Meetup and IFS Connect North America. The episode explores critical themes including balancing AI automation with employee empowerment, understanding regional customer value differences, and leveraging artificial intelligence for improved knowledge management with practical perspectives from industry leaders at TOMRA North America and Tampa Electric.

In this episode:

[00:00] Intro: Live from Nashville - Insights from Future of Field Service Meetup

[01:48] Building Community: The Power of Service Leadership Networks

[03:03] Balancing AI Automation with Employee Autonomy in Field Service

[06:26] Understanding Regional Customer Value: From Canada to US Service Preferences

[09:07] AI-Powered Knowledge Management: Revolutionizing Tech Training

[11:44] Developing Your Service Mantra: Creating a Compelling Value Proposition

[14:58] Service Industry Trends: Beyond Technology to Human-Centric Solutions

[17:02] TOMRA's Journey: Modernizing Service Platforms with an Evergreen Approach

[18:41] Data-Driven Excellence: Achieving 97% First-Time Fix Rate

If you enjoyed this episode, make sure to subscribe, rate, and review on Apple Podcasts or Spotify. Also, subscribe to our newsletter right here.

Watch on YouTube:

By Sarah Nicastro, Founder and Editor-in-Chief, Future of Field Service

Technical debt is an issue that is rapidly growing in importance – an issue that many businesses have avoided for far too long but must begin to reconcile. Gartner defines technical debt as “work that is ‘owed’ to an IT system when teams ‘borrow’ against long-term quality by making short-term sacrifices, taking short cuts, or using workarounds to meet delivery deadlines.”

MIT Sloan Management Review states that, “technical debt is an anchor, dragging down business leaders’ efforts to run a tight ship. The accumulated costs and effort from IT development shortcuts, outdated applications, and aging infrastructure sap a company’s ability to innovate, compete, and grow.” They point out that a degree of technical debt is inevitable, which I think is important to note – and possibly another challenge to overcome, in determining exactly when debt becomes “too much.”

Anecdotally, I’ve had numerous conversations with leaders who bemoan the situation of knowing their existing technology stack isn’t aligned with what their business needs. Many of these leaders feel they have no choice but to “make do” for now (and often now ends up being years).

While ripe with risk, technical debt exists for many reasons that are easy to understand – I’m sure each of you can imagine a handful of reasons the need to “make do” arises (and often persists). With the rapid evolution of the digital landscape that’s taken place over the last decade, many business – and even IT – leaders have been left, heads spinning, to digest the reality that world they once knew and loved – where systems could statically service their purpose for five, eight, even ten years – no longer exists.

The Realities of Today’s Digital Ecosystem

But not only has the reality of the digital ecosystem changed, the AI era that has taken the world by storm is creating a compound effect of technical debt. Technical debt forces a compromise of what’s most effective versus what “will do.” It means contorting what your business has become into the limitations of a system that was created for what your business was a handful of years ago, if not more. But moreover, if your business is inching by on a legacy foundation that should have been replaced by now, you are constricted in your ability to modernize at the pace innovation is demanding – you are not able to properly step into the AI era.

Now, many will try to force band-aids on the problem, versus addressing root cause – some of that is delusion, some born of necessity. But these band-aids are nothing more than more short-term solutions. To truly thrive not only in today’s landscape, but to be prepared for what comes next, you need to dig in and do the hard work of ensuring a strong, capable, modern foundation. Try as one might, there simply are no shortcuts or workarounds that will make an outdated platform fit for purpose in today’s fast-paced landscape – and layering even more passable-but-not-ideal solutions upon a shaky foundation is a recipe for disaster.

Meanwhile, the world isn’t waiting for you to catch up – your customers are already expecting you to somehow match the experiences they get from leading consumer brands. Many of your competitors are already delivering these experiences. Your employees are demanding a more modern employee value proposition, one that is nearly impossible to offer if their workdays are fraught with the burdens of outdated technology. And none of these variables are staying still, so it isn’t enough to catch up; you must determine how you modernize your systems, your processes, and your governance to be what today’s businesses have to be to succeed: agile.

U.S. Air Traffic Control Grapples with Technical Debt

A very real and especially scary example of technical debt is what’s currently happening as a result of the antiquated technology in use by the United States air traffic control. I flew through Newark earlier this month in the midst of its “multi-day meltdown,” and the far reaching and potentially detrimental impact of these issues weighed very heavy on my mind. While there are additional factors beyond the technology, the systems in place are decades old and rely on things like copper wires and floppy disks.

Transportation Secretary Sean Duffy has spoken to the fact that outdated technology is a major factor in the issues affecting the nation's air traffic control systems, saying “What we have right now is the old-school flip phone. You can't update the flip phone.” In the same article, Paul Rinaldi, Vice President of Safety and Operations at Airlines for America and a former traffic controller, agrees with Duffy, referring to the existing system as “archaic.”

Duffy has proposed a four-year plan, estimated to cost more than 12.5 billion, to modernize the nation’s air traffic control system. He says in this article that “A lot of people have said: This problem is too complicated, too expensive, too hard.” All adjectives that those grappling with extreme technical debt have likely felt the weight of.

While many of the reasons technical debt persist can be valid, the risk of continuing to delay addressing it is simply too significant. This Gartner article lends some further insight on how technical debt hinders an organization and advice for how to manage it. And this MIT Sloan Management Review piece calls attention more specifically to how technical debt prevents organizations from deploying AI solutions that could reshape how they compete and what do to about it.

If you have a story to share about how your organization has handled the management or reduction of technical debt, I’d love to hear from you!

by Sarah Nicastro, Creator, Future of Field Service

I’m just returning from a four-day retreat hosted by Natalie Kuhn at MEA outside of Santa Fe, New Mexico. MEA is a retreat center founded by Chip Conley, TED speaker and New York Times bestselling author of Wisdom at Work: The Making of a Modern Elder. The Santa Fe campus is on Rising Circle Ranch, a regenerative horse ranch that spans nearly 2,600 acres of wildlife, hiking trails, winding arroyos, ancient petroglyphs, and awe-inspiring beauty.

As part of the experience, we were ushered by the Ranch Manager, Lee Johnson, to an experience with the ranch’s horses. I have never spent a lot of time with horses, so I learned quite a bit throughout the afternoon and was struck by how much of what I was taking in correlates to today’s business landscape: what makes for an effective leader, how crucially important culture is, and the many forms resilience can take.

Lee and his colleague Maryann began by sharing some facts about horses, including that horses have existed for 56 million years, which is just incredible to ponder. They explained some of the facets that make it possible for a species of prey animals to have existed so long, one of which is the way horses herd. As they explained the relational nature of the herds, they shared that horses have a very specific culture that is centered around five key tenets:

Safety
Connection
Peace
Freedom
Joy

How incredible is it that horses find crucial these very things that we as humans do, too? Moreover, that these tenets have served as the foundation for how these herds have engaged and lived for millions of years. Learning about how central culture is to how horses live got me thinking quite a bit about the growing significance of company culture. When we consider resilience, whether of the horse species or of a business, having these core principles to anchor around is vital. But the principles can’t simply exist; they must be genuinely and consistently embodied. I know nearly every business today has cultural values they can point to on a wall or on their website, but I do question how many are weaving those values into the fabric of how the business is run and how its people are treated.

Leaders Create Power with Teams

Another very specific point I found powerful is when Lee shared that the herd leader, which is almost always a mare, focuses on creating power with – not over – the other members of the herd. If that doesn’t perfectly summarize what’s needed from leaders today, I don’t know what will. Gone are the days of command-and-control leaders; what’s required today are those who can expertly curate a team of diverse and well-honed skills and then empower that team to rally around the company’s values and objectives.

Finally, Lee spoke at length about the almost inconceivable perceptiveness of horses. He explained that when horses interact with humans, they don’t respond well to incongruence. Meaning, if you’re fearful of a horse, that’s OK – but if you’re pretending not to be, the horse senses that incongruence with unease. This brought to mind the importance of authenticity; leaders who create influence by being themselves and by connecting with their teams in a genuine manner are far more effective than those who are guarded, overly poised, or have thinly veiled motives.

During the retreat we not only spent time with the horses but also exploring the beautiful land of New Mexico and learning about its native people and rich history. While there’s certainly value in reading leadership books and attending seminars, it can also be quite profound to tap into some of these other sources of insight for not only leadership lessons, but really life lessons.

Taking the time away from my family and from work to attend this retreat reminded me of my recent conversation with Laurie Battaglia after her keynote at Field Service Palm Springs, driving home the importance of leading yourself first. It can be quite challenging to invest the time, but we need to nurture our inner selves if we want to create external energy that will benefit our loved ones and also our teams, our customers, and the wider communities beyond. Doing so is also key to resilience. However you disconnect, unplug, and reconnect with yourself, continue to invest in your peace and your perspective; it will pay dividends.

Episode 311

In this solo episode, Sarah provides a brief update on Future of Field Service events for 2025 plus a sneak peek into a few other exciting things in the works!

If you enjoyed this episode, make sure to subscribe, rate, and review on Apple Podcasts or Spotify. Also, subscribe to our newsletter right here.

Watch the episode here:

by Sarah Nicastro, Creator, Future of Field Service

In an era where innovation is consistently ranked as a top three priority by corporate leaders, would you be shocked to hear that 80-90% of innovation centers fail? As last week’s podcast guest, innovation expert Amer Iqbal, pointed out, this devastating success rate would be unthinkable in any other business function. “Imagine telling your sales team that a 10% success rate was acceptable – you'd be laughed out of the room,” he says – and he’s not wrong.

Amer founded 5 Ways to Innovate after earning some serious experience in roles such as Head of Digital Transformation for APAC at Meta and Director of Digital Strategy & Innovation at Deloitte Digital. In studying why companies with massive innovation ambitions consistently struggle to execute, Amer’s research, spanning 100 companies, reveals a fundamental truth: the gap between innovation ambition and execution isn't about ideas or investment – it's about systematic approach.

When it comes to one of the biggest missteps that large organizations make with innovation, it is to try to act like a startup. "I think when large companies try to be a startup, they're selling themselves short because large incumbent corporates have so many advantages that startups don't,” says Amer. “They're not scrapping for VC money, they have revenue models, they have strategic modes. They have partnerships, they have all of these capabilities in place that startups can't possibly compete with."

Amer suggests using "speedboat" initiatives like startup studios to explore new opportunities while the core "battleship" business maintains stability. Leaders can fund small, agile teams to test innovative approaches without disrupting established operations. This balanced approach allows organizations to benefit from startup-style innovation while maintaining their strategic advantages in scale, resources and established customer relationships.

Another issue contributing to the innovation execution gap is related to breadth. “Organizations put all their eggs in one basket instead of treating innovation as a portfolio,” explains Amer. “Innovation is not a project, it's a portfolio.” Depth also presents challenges, Amer points out, because often innovation success is measured by inputs (training programs completed, POCs launched) rather than outputs (actual business impact).

5 Approaches to Innovation

The research Amer has done has revealed that successful innovators use five common approaches to innovation. While it isn’t necessary to use all five approaches, the best success is achieved when a business is consistently implementing at least three of five fundamental approaches.

Upskilling with Purpose. Rather than generic innovation training, successful companies create structured programs aligned with specific business objectives. This isn't about checking boxes – it's about building practical capabilities that drive results.
Innovation Hubs That Actually Work. The key difference between successful innovation hubs and the 90% that fail? Integration with core business objectives and clear metrics for success. They're not innovation theaters – they're profit centers.
Startup Studios: The Internal Venture Builder. Think of this as "entrepreneurship as a service" within your organization. Amer shared how one bank successfully launched six simultaneous internal startups, each with blended teams of internal talent and external experts.
Strategic Incubators. Unlike internal startup studios, strategic incubators focus on external startups with minimal corporate interference. The goal? Let innovators innovate, then invest in what works.
Ecosystem Plays. This passive but powerful approach involves systematically scanning the startup ecosystem for partnership opportunities. It's about being a smart investor rather than trying to build everything in-house.

In addition to incorporating three of the five innovation approaches, Amer suggests companies consider the right mix of invested vs. divested approaches, emphasize the importance of clear metrics focused on outcomes vs. inputs, and moving beyond the familiar efficiency-only thinking.

Keep Innovation Customer-Centric

Amer and I also discussed the importance of outside-in innovation and some of the shortcomings that occur in companies with even the best of intentions around customer-centricity. “Too many businesses are still running their planning process inside-out,” he says. “This is what the business processes need to be, this is what the regulations are, this is what our business model is. And then right at the final point when it's time to launch a product, launch an app, or whatever it may be, that's when we go do some customer research."*

True customer-centric innovation requires integrating customer needs into products, business models, and user experience - not just the final interface. And companies must move beyond traditional customer feedback to understand unexpressed needs through observation and data analytics. "There's in-context inquiry where you're shadowing customers, you're observing, you're collecting data through digital platforms,” Amer says. “There are so many ways of understanding those latent customer needs that a customer may not express and sometimes may not even know themselves. That's how great companies actually do customer research."

As traditional industries face disruption from digital natives and AI-powered competitors, the ability to innovate systematically has become a make-or-break capability. If you’d like to hear more of Amer’s advice, you can listen to the full podcast conversation.

Episode 310

In this episode of UNSCRIPTED, host Sarah Nicastro welcomes Amer Iqbal, a sought-after speaker who has spent the last 20 years leading innovation at some of the world’s top companies including as the Head of Digital Transformation, APAC at Meta and Director of Digital Strategy & Innovation at Deloitte Digital. Amer joins Sarah to discuss some of the themes from his upcoming book, The 5 Ways to Innovate.

What You'll Learn:

- How the "Five Ways to Innovate" framework helps to systematically drive innovation success

- Why traditional companies should embrace startup methodologies while leveraging their established strengths

- The three-pillar approach to AI implementation: efficiency, growth, and transformation

- How to balance invested vs. divested innovation strategies based on organizational characteristics

- Why customer-centric innovation must extend beyond user experience to product development and business models

- The New York Times transformation case study: maintaining core values while revolutionizing delivery methods

- How to overcome the "we've always done it this way" mindset while respecting organizational legacy

- Why innovation success requires systematic approaches rather than isolated initiatives

This episode provides practical insights for service leaders looking to transform their organizations while maintaining their core strengths, with specific emphasis on balancing traditional business values with modern innovation approaches.

If you enjoyed this episode, make sure to subscribe, rate, and review on Apple Podcasts or Spotify. Also, subscribe to our newsletter right here.

15 Questions to Ask Before Choosing Field Service Management Software

15 Questions to Ask Before Choosing Field Service Management Software

Share

1. What business problem are we actually trying to solve?

2. Which workflows matter most to our customers and technicians?

3. How complex is our scheduling reality?

4. What level of mobile and offline capability do our teams really need?

5. How will this software help us improve the metrics that matter?

6. What data do we need to trust - and where does it live today?

7. Which systems must this platform connect to from day one?

8. What service delivery model(s) do we need this solution to support?

9. Have we involved the daily users of this system early enough?

10. What is configurable versus customized?

11. How will AI and automation be used (and governed)?

12. What organizational change will this require?

13. How will we define success in the first 90 days, six months, and 12 months?

14. Can this platform support the service organization we aim to become?

15. Who will own the outcome internally?

Final Thought

Stay Connected

Related Content

Service Organization vs. Service Business: The Mindset Distinction that Defines Opportunity

Why There Is No Silver Bullet in Asset Management: A Conversation with Johan Jansen van Rensburg, SAPPI

15 Questions to Ask Before Choosing Field Service Management Software

Most Recent

How Alfa Laval Has Brought Service into Focus

The Feminist Plumber Who’s Paying It Forward

Is Mentoring an Underutilized Aspect of Your Field Service Workforce Strategy?

What Is Field Service Management (FSM)? Definition, Benefits, and How to Get It Right

What Is Field Service Management (FSM)? Definition, Benefits, and How to Get It Right

Share

What Is Field Service Management?

Core Components of FSM

How FSM Has Evolved

Why Field Service Management Matters

Operational Efficiency and Productivity

Customer Experience and Retention

Financial Impact and Resource Optimization

Common Challenges in Field Service Management

People and Process Friction

Technology and Data Gaps

Overcoming Obstacles

How Field Service Management Works Day to Day

Typical FSM Workflow

Technology That Enables the Flow

Integration Across the Business

Implementing Field Service Management: A Practical Guide

1) Assess and Align

2) Design the Target Operating Model

3) Select the Right FSM Platform

4) Implement in Phases

5) Enable the Workforce

Implementation Checklist

Measuring Success: Field Service KPIs That Matter

Working With Contractors and Partners

Future Trends in Field Service Management

Automation and AI at the Core

Extended Reality and Digital Twins

Connectivity and Collaboration

Business Model Shifts

Building the Business Case for FSM Modernization

Quantify the Opportunity

Map Costs and Risks

Tell the Story

FSM FAQs

How does FSM differ from Customer Relationship Management (CRM)?

Who uses Field Service Management?

What are the key metrics in FSM?

Can small and mid-sized businesses benefit from FSM?

How does FSM support compliance and safety?

What is the relationship between FSM and IoT?

How long does it take to implement an FSM solution?

What is the total cost of ownership for FSM?

How do I choose between best-of-breed FSM and an integrated suite?

What are first steps if we are still using paper and spreadsheets?

Putting It All Together

Stay Connected

Related Content

TEST

What Is Field Service Management (FSM)? Definition, Benefits, and How to Get It Right