A mobile program is one of the few things in a company that three different functions all touch and none of them fully owns. IT configures the devices and hands them out. Finance pays the carrier. HR controls the events — hires, role changes, departures — that should drive every change to a device or a line. Each function does its own piece well. The trouble lives in the spaces between them, and those spaces have a name the org chart never quite assigns: mobile program ownership.
That sounds like an abstraction, but it shows up as very concrete money. The surprise line item, the inactive lines you’re still paying for, the new hire waiting two weeks for a phone, the acquired company whose fleet is a black box — most of these aren’t failures of effort inside any one team. They’re failures of the handoffs between teams that each assume someone else is watching.
This is the deeper look behind the cross-functional onboarding and offboarding checkpoint in our 7-Point Mobility Program Health Check — why a program with three capable owners can still fall through the gaps, and what it takes to close them.
If you asked three people at your company “who owns mobility here?” and got three different answers — or three shrugs — you’ve found the problem in a single question. None of the three would be wrong, exactly. IT really does own the devices. Finance really does own the bill. HR really does own the people whose status drives every change. Each owns a genuine slice.
But a fleet isn’t a stack of slices; it’s a continuous system, where a change in one function is supposed to trigger an action in another. When ownership is divided up by function, every seam between those functions belongs to no one — and the seams are exactly where things go wrong.
The gap between IT and Finance is where the clearest money leaks, in two specific ways.
The tell is a sentence you’ve probably heard: “our bill went up and no one’s quite sure why.” That’s an ownership problem wearing a cost problem’s clothes — the dollars are just where it surfaces.
Layer onto that gap the thing that makes it relentless: the fleet is always in motion. Every hire, role change, transfer, leave, and termination should trigger an action on a device or a line. Those events start in HR — the one function most companies don’t think of as part of “mobility” at all. When HR’s events aren’t wired to IT’s and Finance’s actions, changes get missed at volume: lines for people who left stay open, new hires wait, and an acquired company shows up as a fleet nobody has mapped.
The faster the churn, the worse it gets. High-turnover operations — drivers, retail floors, seasonal crews — and acquisitions turn a steady drip into a flood. The early warning signs are simple: if you can’t say how many lines you have, or your HR system isn’t connected to anything mobility-related, the events are already getting past you.
The natural reaction is to tell IT — or Finance — to be more careful. It doesn’t work, because the gaps aren’t a diligence problem. Each function is already doing its own job correctly; the failure is in the space between the jobs, and you can’t assign a seam to someone who only ever sees one side of it. More effort inside a slice doesn’t close the gap between slices. The fix isn’t trying harder. It’s deciding who owns the whole.
This is an operating-model fix, not a heroics fix, and it has four parts:
Put the four together and the model changes shape. Someone owns the whole; the functions share one process; HR events drive mobility actions automatically; and the group reviews the same data on a cadence. None of it requires a reorg or new headcount — it requires naming an owner and connecting three functions that are already doing their parts well in isolation.
Here’s why it matters beyond tidiness: most of the specific problems a mobility program runs into — runaway carrier cost, security gaps, slow device provisioning, lost asset value — are downstream of this one. They’re the symptoms; unclear ownership is the cause. Where the ownership exists, the seams close and the symptoms stop recurring. Where it doesn’t, the program keeps falling through the gaps between the people who each almost own it.
If “who owns mobility here?” doesn’t have a one-name answer, that’s the first thing worth fixing — and a surprising amount of the cost, security, fulfillment, and asset trouble that shows up downstream traces straight back to it. A managed approach gives the program a single point of accountability and one shared process across IT, Finance, and HR — built into our Carrier Connectivity & Optimization capability and delivered as an ongoing managed service.
Contact us to schedule a conversation, or download our whitepaper, Best Practices for an Effective Enterprise Mobility Program, for the governance model behind this and the rest of the program.
