Client snapshot
A fast-growing aviation services provider supporting major regional carriers across passenger services, baggage handling, and operations support. New to the ServiceNow platform. Sponsor: VP of IT Operations, with executive visibility on customer experience outcomes.
The trigger
The business was scaling faster than its operational backbone. Passenger volumes were climbing, regulator scrutiny was tightening, and the customer experience moments that mattered most — a passenger whose bag didn’t arrive, a traveler stranded by a delay, a booking that broke at the worst possible moment — were being handled by a patchwork of email, spreadsheets, and tribal knowledge.
The VP of IT Ops saw what was coming: at the next level of scale, that patchwork wouldn’t just be inefficient — it would be visible to passengers, to airline partners, and eventually to regulators. They needed a platform foundation that could carry the company through the next phase of growth, not just patch the current one.
ServiceNow was selected. The hard question wasn’t whether — it was where to start.
What we found
The instinct in most greenfield ServiceNow programs is to do everything at once. The platform sells well as a portfolio, and executive sponsors often want to see CMDB, GRC, and customer service modules light up in parallel.
We pushed back on that approach.
What we saw was an organization with no shared system of record for IT, no trustworthy CMDB, and no formal control framework — and a customer-experience problem that needed a visible win in months, not years. Trying to deliver CSDM and GRC simultaneously, with no operational discipline underneath, would have produced two half-built modules and a credibility problem with the executive team.
The diagnosis: ITSM had to come first — not because it was the most strategic, but because it was the only foundation on which the rest could be built honestly. Without disciplined incident, request, and problem management, there would be nothing for CSDM to map and nothing for GRC to govern.
Approach: a deliberately sequenced program
We structured the program in three building blocks, each delivering standalone value while setting up the next:
Phase 1 — ITSM as the operational backbone
We started with the customer-visible processes: incident, request, and problem management, scoped tightly around the moments that mattered to passengers — baggage incidents, flight disruption response, booking system issues. Rather than boiling the ocean, we built ITSM around the handful of services the business cared most about and made sure those services worked end-to-end before expanding scope.
Phase 2 — CSDM as the trust layer
With ITSM live and generating clean operational data, we layered in CSDM. We deliberately avoided the most common failure mode of CMDB programs — starting with discovery and trying to inventory everything. Instead, we worked top-down from business services, mapped the application services and infrastructure that supported the customer-facing capabilities ITSM was already managing, and built the CMDB out from there.
This sequencing meant the CMDB was useful from day one — every CI in it was tied to a service the business already cared about, and every incident routed through ITSM was now enriched with service context.
Phase 3 — GRC built on a foundation it could trust
Only once CSDM was producing reliable service and CI data did we move into GRC. The control framework was designed against real services, real owners, and real CIs — not against a theoretical inventory. Risk and compliance work that would have been spreadsheet-driven and unauditable a year earlier was now native to the platform, traceable, and defensible.
The throughline across all three phases: everything tied back to customer experience. Every process improvement, every CI mapped, every control implemented had a line of sight to a passenger outcome.
The value case we built
Before delivery, we worked with the client to model the projected business value of the program. The case was built bottom-up — service by service, process by process — with each projection grounded in the client’s own baseline data and validated against industry benchmarks.
Projected operational outcomes:
- ~42% reduction in baggage-incident resolution time, driven by centralized service ownership and automated routing
- ~48% MTTR reduction across critical operational systems including gate management, baggage handling, and crew scheduling
- ~33% improvement in service desk first-call resolution through knowledge-driven workflows
Projected governance outcomes:
- ~65% reduction in audit preparation effort through centralized evidence collection and automated control tracking
- Policy exception approval cycles compressed from 14 days to under 48 hours
Projected financial and strategic outcomes:
- Annual operational value modeled in the range of $4.8M–$7.2M through service consolidation, automation, and reduced disruption costs
- Merger integration readiness accelerated by an estimated 9 months through standardized service models and governance frameworks
Following Phase 1 delivery, the program was scoped to expand into integrated risk management, operational resilience, vendor risk governance, and AI-assisted disruption management.
What we’d tell someone facing the same thing
Three things we’d say to any IT leader walking into a greenfield ServiceNow program at a fast-scaling company:
- Sequence ruthlessly. The platform can do everything. That doesn’t mean you should try to do everything at once. Pick the foundation that earns the right to do the next thing.
- Tie every phase to a customer outcome the business already cares about. It keeps sponsorship strong, justifies investment at every stage gate, and prevents the program from drifting into IT-for-IT’s-sake.
- CSDM and GRC depend on disciplined ITSM underneath. You can shortcut this and many programs try. The shortcuts always cost more later than the discipline costs upfront.
Want help thinking through the same problem?
If you’re standing up ServiceNow for the first time — or trying to recover a program that started too broad too fast — we offer a ServiceNow Foundation Review: a focused 60-minute working session where we look at your current state, your sequencing plan, and the three highest-leverage moves to make in your next two quarters. No pitch, no obligation.