But there’s a pattern emerging among the most forward-thinking government IT shops: Once they get their ITSM house in order, they don’t stop at the IT department door.
They go enterprisewide.
Cities and counties across the country are quietly transforming how government works, not by launching headline-grabbing smart city initiatives, but by doing something more fundamental: applying the discipline, structure and efficiency of IT service management (ITSM) to the rest of the organization.
Whether it’s HR, facilities, finance or legal, the same workflows, self-service portals and automations that reduced IT ticket volume by double-digit percentages are now doing the same for onboarding delays, facilities work orders and procurement requests.
For CIOs and chief technology officers (CTOs) in state and local government, this shift represents one of the most significant strategic opportunities available right now, and it doesn’t require a new budget line, a massive implementation or a separate platform.
THE SILO PROBLEM IN GOVERNMENT
Anyone who has worked in or with a government IT department knows the frustration of silos. Departments operate independently, each with its own processes, its own inboxes and its own way of tracking work. A facilities request gets emailed. An HR onboarding task lives in a spreadsheet. A finance workflow requires three phone calls and two signature approvals that nobody can trace.
The result? Delays, dropped balls and a lack of visibility make it nearly impossible to manage resources, report on outcomes or continuously improve.
What many government IT leaders have discovered is that the moment they solve these problems for IT, other departments come knocking. They see how IT is operating, and they want the same thing.
That’s exactly what happened when the South Carolina Department of Commerce set out to modernize its ITSM platform.
Within 10 months, the ROI was so significant that CIO Doug Foster described it as “insane.” But more importantly, the momentum created by IT’s transformation spread across the organization. Other departments recognized that the same approach could work for them, and the platform quickly grew beyond IT into a true enterprise service management (ESM) deployment.
This isn’t an isolated story. It’s a pattern.
WHAT ENTERPRISE SERVICE MANAGEMENT ACTUALLY MEANS IN GOVERNMENT
Enterprise service management is the application of ITSM principles, such as service catalogs, structured workflows, self-service portals, automation and dashboards, to non-IT departments.
In government, that translates to a single platform where residents and employees can interact with any department through a consistent, intuitive experience.
Think of it this way: If a new city employee gets hired, their onboarding shouldn’t require the IT department to manually set up accounts, the HR department to email orientation documents, and facilities to track down a badge request, all through separate inboxes with no visibility into whether any of it is actually happening.
With ESM, that entire onboarding workflow can be automated, tracked and completed with far fewer touchpoints and far less room for error.
The city of Goodyear, Ariz., offers a textbook example of this progression. The city’s IT leadership set out to increase IT maturity by adopting ITIL-aligned processes. They set up a service catalog and self-service portal, and the results came quickly, with 75 percent of all service tickets beginning to flow through the portal, giving the team real data for the first time to manage resources and justify investment.
But CIO Lisa Faison’s vision didn’t stop there. With the platform running smoothly, the team began extending it to other city departments, moving toward an enterprise-level service and project management capability that benefits the entire city government, not just IT.
THE SELF-SERVICE ADVANTAGE
One of the most underappreciated aspects of ESM in government is the cumulative effect of self-service across departments.
When IT implements a self-service portal, they deflect tickets, free up technician time and improve response times. When HR, facilities and finance do the same thing on the same platform, the effect multiplies.
Employees stop sending emails into the void. They stop calling different phone numbers depending on which department they need. Instead, they go to one place, find what they need and submit a structured request that is automatically routed to the right team, with visibility into status every step of the way.
The city of Buffalo, N.Y., experienced this shift firsthand.
With roughly 2,100 city employees depending on IT service, the department needed a way to increase throughput without increasing head count.
Smart ITSM with automated workflows and a well-designed self-service portal made it possible to resolve issues faster and reduce ticket volume. But the real insight was about behavior change: Getting employees to use the portal required deliberate effort, including quarterly meetings with employees who were still calling the help desk to show them the benefits of self-service.
That kind of intentional change management, applied across departments through ESM, is what turns a technology investment into a service delivery transformation.
For Oklahoma City, which supports more than 5,000 city employees, the efficiency gains from ITSM were clear, and the feedback was unambiguous. “This is the first IT service management platform we’ve implemented that everyone loves to use,” then-Business Systems Manager Dusty Borchardt noted.
When a platform earns that level of trust from both IT staff and the broader employee base, expanding it to other departments becomes a natural next step.
In Oklahoma City’s case, the platform’s reporting and dashboards gave city leadership real insight into how IT was performing, and it created a foundation for bringing other service functions under the same visibility umbrella.
DATA IS THE HIDDEN VALUE OF ESM
When service delivery is fragmented across departments, there is no data.
There’s no way to know how long an HR onboarding request typically takes, where facilities work orders get stuck or how procurement timelines compare quarter over quarter. Leaders are flying blind.
ESM changes that.
When all service requests flow through a single platform, every interaction generates data. Response times, resolution rates, workload by team, self-service adoption rates — all of it becomes visible.
For government IT leaders who need to justify head count, make the case for new investment or demonstrate efficiency to elected officials and the public, that data is invaluable.
As Goodyear’s Faison put it: “It’s one thing to say we’re overworked, and it’s another to be able to illustrate this with concrete data.”
That’s the kind of credibility that leads to better budget conversations, more strategic resource allocation and a stronger IT organization overall.
THE “ONE PLATFORM” ADVANTAGE
Government IT environments are notoriously complex. There are legacy systems, compliance requirements, union contracts, budget cycles and stakeholders ranging from the mayor’s office to the front-line employee trying to get their laptop fixed.
Adding separate platforms for every department creates integration nightmares and administrative overhead that nobody has the bandwidth to manage.
This is why the “one platform” approach resonates so strongly in the public sector. No-code, low-admin platforms let department leads manage their own service catalogs without depending on IT to build every form and workflow.
This is what makes ESM expansion sustainable.
WHERE GOVERNMENT CIOs SHOULD START
If you’re a CIO or CTO in state or local government looking to extend service management beyond IT, the path forward doesn’t have to be complicated.
Here’s a straightforward starting point:
- Start with a quick-win department. HR or facilities often have the most visible service delivery pain points and the most to gain from structured workflows and self-service. A quick win with a high-profile department builds internal momentum and gives you a proof point to bring to leadership.
- Use your existing platform data to make the case. If your ITSM is already generating metrics on resolution times, ticket volumes and self-service adoption, those numbers tell a story about what’s possible. Apply that same lens to HR onboarding times or facilities work order backlogs, and the ROI argument makes itself.
- Bring department heads into the conversation early. ESM only works if the departments that you are expanding into are engaged stakeholders. The most successful government ESM deployments happen when department leaders see themselves as owners of their own service delivery, with IT as the enabler.
- Choose a platform designed for expansion. The difference between ITSM and ESM is largely architectural. Make sure your ITSM/ESM platform can support multiple departments with distinct service catalogs, workflows and portals, all without requiring a new implementation for each one.
IT AS THE SERVICE DELIVERY BACKBONE OF GOVERNMENT
There’s a strategic narrative available to every government CIO that goes far beyond ticket management: IT as the operational backbone that makes other departments more efficient, more accountable and more responsive to residents.
That narrative is hard to build when IT is firefighting. But when ITSM is mature, when self-service is working and when data is flowing, IT earns the credibility to extend the positive impact across the organization.
The cities and counties doing this well aren’t just solving an IT problem. They’re changing how government works.
They’re doing it one department at a time, with technology that scales.
Interested in seeing how your organization could benefit from enterprise service management? Explore TeamDynamix ESM solutions for the public sector.
