Smaller Governments Have More Service Management Options
Smaller cities, counties and municipalities usually operate with limited IT staffs and tight budget cycles. Service desk investments often compete with more visible priorities, and CIOs may have to plan spending a year in advance.
New delivery models can lower the barrier.
One example is a domain-separated, multitenant environment that makes service management platforms more accessible. I compare it to a condominium building. Each customer has its own space and security, but shares the larger infrastructure. The customer can configure its environment, but it does not have to build or maintain the entire platform.
That gives smaller governments access to functions such as incident management, change management, configuration management and discovery without taking on the cost of a fully independent environment.
AI adds another layer. With access to the right data, AI can triage tickets, route them to the right place and, in some cases, resolve them automatically.
Those capabilities create proactive responses and improve overall customer satisfaction. This can reduce repetitive work and allow service desk staff to spend more time on problems that require human judgment.
READ MORE: Here is a guide to AI governance for state and local governments.
Legacy Technology Is Only Part of the Problem
Large government organizations often face a different sets of obstacles.
Many are still supporting legacy systems because replacing them is expensive and difficult to justify. Service desks also tend to be viewed as back-office operations, which can make modernization harder to sell during the budget process.
Procurement can slow things further. State and local governments often work through long RFP processes, and major technology changes can take years from planning to deployment.
Policy is another constraint.
Some agencies are interested in using AI, but have not finished setting rules for how it can be used. I work with government organizations that have restricted AI while they develop governance policies. That means even relatively basic service desk automation may have to wait.
Labor agreements can also shape what agencies are able to deploy. In one local government project, we explored using mobile devices and QR codes to track field work. The technology was straightforward. The labor contract was not. Workers could not be required to carry city-issued devices or use their personal phones for the process.
Problems like that do not disappear when an agency buys a new platform.
LEARN MORE: Regional collaboration is the overlooked layer in government IT.
Beyond IT: Service Desks as a Citizen Experience Function
The more interesting change is happening in how agencies define service itself.
Government service desks have traditionally supported employees. Now, agencies are looking at ways to connect IT support with services used by residents, including 311 requests, permitting and other forms of intake.
That changes the role of the service desk.
I think of it as a brand ambassador for the organization. A resident who needs a permit or a government employee who cannot access an application is judging the agency by what happens next. If the request disappears into a silo or has to move manually from one department to another, that becomes part of the user’s experience with government.
We are starting to see agencies take that problem more seriously.
The technology has reached a point where both large and small governments have credible options. The harder work is often internal: changing old processes, resolving policy questions and getting procurement lined up with what the agency is trying to accomplish.
In some governments, that work is finally beginning.
