When Michael Smith became Nevada’s CTO in May 2026, he brought a deep understanding of the state’s IT landscape. He’d begun his public service career more than a decade ago as an application developer at the Department of Motor Vehicles. He later spent six years working on enterprise IT services at the Department of Administration before joining the Governor’s Office of Technology four years ago. In his new role, he draws on all that experience — plus his work in retail.
For many years, Smith was a manager at big-box stores. Although that may seem unrelated to his current role, it shaped his understanding of customer experience. In a recent interview, Smith discussed how he applies the lessons he learned serving shoppers to serving his current customers — state agencies — and how that ultimately improves services for the public. Below are highlights from the conversation. This interview has been lightly edited for clarity and length.
A Focus On Consistency
Smith will measure his team’s success not just on how it delivers individual projects, but on its ability to deliver consistently over time. My role is to lead the statewide technology strategy, focusing on operational excellence and customer experience, and coordinating across executive branch agencies. We aim to be a bridge between our strategy and the day-today operations of people serving Nevadans. My approach comes from working here for almost 11 years and across different areas, leading deployments in areas like Microsoft Office 365 and ServiceNow. My job is to make sure we turn our strategy into operations that serve our agencies and our constituents.
Since taking this role, I’ve identified a few priorities. First is customer experience. That’s huge for me. Coupled with that is improving service delivery and operational consistency. Our partner agencies and constituents should know what to expect and how we’re going to meet their needs. We should do that consistently, day in and day out. If we’re consistent, customers know exactly what to expect and how things will get done.
We’re also focused on advancing modernization efforts and embedding security in everything we do. I spent the better part of three decades in big-box retailing, and that’s where my focus on customer experience comes from. Sometimes we want customers to be where we want them to be, but they’re in a different place. We need to lean into their expectations.
That’s what I bring to what I call the business of government. We serve partner agencies as well as constituents, and I want to make sure we’re meeting their needs. That comes from my time in retail. Customers have expectations, and we need to meet them.
A Key Component: Process Clarity
One way to improve consistency is to hit the marks on processes. With that in mind, Smith is developing operational playbooks for the team to follow.
When we don’t have process clarity, people interpret things differently, which leads to inconsistent service. Work becomes reactive instead of structured and operational. Agencies see delays, rework and misaligned expectations. The same issues recur because we haven’t agreed on what “good” looks like. It goes back to expectations. The customer may have one expectation, and we have another. We need to meet theirs.
Playbooks take our strategy and turn it into day-to-day operations. They define the desired outcome, assign roles and responsibilities, and lay out step-by-step workflows, escalation paths and communication expectations. They also include how we gather feedback from customers. When we build these playbooks, everyone knows exactly what they need to do, and it removes ambiguity.
A Failure To Communicate?
Sometimes projects go awry, Smith says, not because of technical problems but because IT doesn’t understand the customer’s pain points. There’s a difference between customer service and customer experience, he says. It often comes down to expectations. Customers come in with expectations, and if we don’t ask the right questions, we may go down the wrong path. We arrive at a solution and think we’re done, but the customer says that wasn’t what they needed. We need to understand their priorities and clarify the goal upfront. I see it often: We think we know what the customer wants, or they think they know, but until we really work through it together, we don’t get to the right outcome.
Listening is one of the more difficult things. Sometimes we listen just to respond rather than to understand. We need to slow down and truly listen. Don’t get five steps ahead or formulate your answer too early — understand what the customer is actually saying. Most IT professionals move fast and want to get to the next thing, but we have to pause and listen to understand rather than react. It’s the difference between customer service and customer experience. Closing a ticket means we may have provided a service, but what did that experience look like? The customer determines whether the issue is truly resolved.
We need to focus on the full experience from the time they call the service desk to when the issue is resolved. We should verify that we’ve solved the problem and that the customer is satisfied.
Building a CX Culture
Over time, clear, consistent practices around the customer experience should become self reinforcing, Smith says, leading to a broader cultural shift.
Culture is about an organization’s priorities and values. It’s not easy to instill, but leadership has to drive it. We focus on ownership: We own the customer, own the problem and own the solution. The behaviors we reinforce are what shape the culture. If everyone consistently prioritizes the customer experience, the culture shifts. In IT, we don’t always have the strongest service culture, so we have to shift our mindset to serving others. You have to care about your team and your customers. If you care, you’ll go out of your way to create a good experience and provide the right solutions.
We’ve all experienced poor service. If my car breaks down, I don’t want to hear, “Come back in a month.” In IT, there’s a person behind every ticket who can’t do their job. We need to think about the experience we would want if we were in that position.
In retail, you have customers and employees, and you have to drive a service culture from the top down. Customers can tell whether you care. In government, people want to get back to serving others. If we understand that, we can provide better solutions, communicate more effectively and deliver a stronger experience.
This article originally appeared in our recent guide, “Taking the Guesswork Out of Digital Services.” To learn more about how your counterparts are using technology to improve the delivery of resident programs, download it here:
