Across the country, local governments are being asked to do more with less. Costs are rising, revenues are uncertain, and communities are navigating increasingly complex challenges. In these moments, it is easy to turn inward and focus on budgets, staffing, and structure.

I have felt that pull myself. But I have also learned something important. Residents do not experience our budgets. They do not experience our organizational charts. They experience us in moments. Moments when they need help, when they are confused, and when something is not working the way they expected. And in those moments, they decide whether they trust us.

What we often underestimate is that the experiences people have in those moments are shaped long before those moments ever occur. They are shaped by the systems, tools, and decisions we design when pressure is lower and options feel broader.

That realization has shaped how I think about leadership, especially during times of fiscal constraint. If we make changes without understanding how people experience our systems, we risk making things harder, not better. We risk increasing the friction and fragmentation that may already exist in public service delivery, especially in moments when resources are constrained and the margin for error is smaller.

This is why the work of understanding and designing experiences cannot wait until times of constraint. It must begin earlier, when we have the space to see clearly, test approaches, and build systems that can hold up under pressure. Because the systems we design in stable times determine how well we serve in constrained ones.

The question, then, is where does this work begin?

When Change Feels Different on the Inside and Outside

In Portland, we are navigating both fiscal pressure and structural change. Our form of government has shifted, roles have evolved, and we are exploring ways to centralize services like human resources, procurement, and technology. These are necessary changes, but they do more than improve efficiency. They reshape how work happens and how those changes are felt by both residents and employees.

From a leadership perspective, these efforts are about alignment and responsible use of limited resources—and they should be. But they also influence something less visible and just as important: how those changes are experienced in practice.

And that has led me to ask some different questions. What does this feel like to the employee trying to do their job? What does this feel like to the resident/business trying to get help? Because those answers are not always the same as what we see on paper.

A process that looks streamlined in a chart can feel very different to the person navigating it. What appears efficient on paper can translate into multiple handoffs, delays, and uncertainty in practice. And when that happens, the burden does not disappear. It shifts. And it often lands on employees, and ultimately, on the residents we serve.

That tension creates a critical leadership responsibility. When our systems tell one story but experiences tell another, leadership must close that gap. And it starts by looking at the experience of the people closest to the work.

Every Experience Starts with an Employee

The closest place to see that difference is through our employees. Behind every resident interaction is a public employee trying to help someone solve a problem.

It might be someone calling because they are struggling to pay their bill or trying to understand whether they qualify for assistance. It could be a developer trying to make their way through the city’s permitting process. These are not simple transactions. These are moments where people may already feel stressed, uncertain, or even embarrassed.

Our employees want to help in these moments. But too often, they are navigating systems that were not designed with their experience in mind; systems that become even more difficult to navigate when resources are stretched and demands increase: multiple databases, disconnected platforms, layered policies, and processes that require coordination across teams. Over time, those systems force employees to create workarounds.

When resources are limited, those workarounds are not just frustrating, they are costly and consume resources that organizations can no longer afford to lose. And, from the inside, those workarounds become normal. From the outside, they feel like friction and fragmentation.

Within the Portland Water Utilities’ Customer Service group, I introduced journey mapping as a way to help a few employees step back and look at our financial assistance program differently.

We did not complete a full end-to-end journey map, but we did begin exposing employees to what it means to look at and experience a service from the customer’s or resident’s perspective. And even that initial work was enough to surface important insights.

We know that some residents are unsure whether they qualify for assistance. Others delay applying because of stigma, language, and other barriers. Some struggle to gather the documentation required to complete an application. These are realities our employees encounter every day as they try to help people navigate the system.

What became clear is that we had already learned many of these things through years of experience, and we often keep learning them the hard way. Journey mapping provides a way to learn them more intentionally. It gives us a tool to understand, empathize, and analyze the experience end to end, so that when pressure increases, we are not reacting blindly but operating from a clearer understanding of how our systems really work for customers. That clarity becomes especially important when resources are constrained and decisions must be made quickly and with confidence.

When we begin to see the experience comprehensively, we can identify issues more quickly and address them more holistically, rather than responding to problems one at a time. It creates space for us to step back, see the full experience, and move beyond piecemeal fixes toward solutions designed for how people actually interact with our services.

That powerful shift in perspective allows us to identify where we’re asking too much of residents and where employees are compensating for gaps in the system. And, it helps us see where our programs may not always be delivering the outcomes we intend. We move from reacting to individual challenges to designing systems that better support both residents and employees from the start.

Journey mapping does not replace what we learn from experience, but it helps us see thing sooner, more clearly, and more consistently across our organization.

Seeing People Clearly Changes How We Design

As we began looking more closely at our financial assistance program, it became clear that we were not serving one type of customer. We were serving many, and needed to start identifying these different customer profiles, understanding that each is navigating our programs and the city in their own way.

A single mother living in an apartment and receiving SNAP benefits experiences the city differently than a retired couple who has lived in their home for 40 years and is managing rising costs on a fixed income. A small business owner balancing both their home and business costs, while planning for retirement has yet another experience.

When we treat these residents as if they are all the same, we miss what matters: how they experience our services, how they interpret our actions, and how those interactions shape their trust in us.

The same is true for our employees. A recent college graduate entering their first public service role brings different expectations and needs than someone who has worked for the city for 25 years and is looking for ways to continue making an impact as they approach retirement. Another employee may be mid-career and ready to take on more responsibility and grow into leadership.

We also see differences in how supervisors, middle managers, frontline staff, and executive leaders experience the organization. There are differences between represented and non-represented employees, between those who are closest to the work and those shaping it.

Each of these perspectives matters because each one experiences the system differently. When we treat employees as if they are all the same, we miss what matters most: how they experience their work, what they need to be effective, and how well our systems support or hinder them.

This is where segmentation, or identifying different profiles, becomes a critical tool. When we begin to understand these different profiles through segmentation, we start to see patterns. We see where policies land differently. We see where communication does not connect. We see where systems support people and where they slow them down. And once we see those patterns, we can no longer (or should no longer) design the same way.

That understanding allows us to design programs and services differently. It helps us align the way we work with how people experience us, allowing us to serve both employees and residents more effectively. And, when budgets are tight, it allows leaders to direct limited resources where they will have the greatest impact.

It also changes how we make decisions. Once we begin to see what it is like for residents and employees to experience our systems, we have to ask a different set of questions. Not just what works, but for whom. Not just what is efficient, but what is clear, consistent, and trustworthy. And that is where data, technology, and governance begin to matter in a different way.

Building trust is not just about the tools we use. It is about how decisions are made, who is involved, and how consistently and clearly those decisions are explained.

Trust is not built in a single decision or moment. It is built across many small moments and decisions. If experience is where trust is felt, then decision-making is where trust is won or lost.

Designing Through Constraint

Fiscal constraint forces difficult decisions. There is no way around that. But I have come to believe that how we decide matters just as much as what we decide.

Before we centralize a service, we must understand how people are using it today. Before we reduce staffing, we must understand where employees are already carrying invisible burdens. Before we redesign a process, we must understand how it feels to move through it. This is not about slowing down decision-making. It is about making better decisions, especially when resources are limited.

When we take the time to understand experiences, through tools like segmentation and journey mapping, and by listening to what employees and residents are already telling us, we can reduce unnecessary complexity and cost for governments and our communities. We can identify where services are not working as intended and address issues more holistically rather than through piecemeal fixes.

Segmentation helps us understand who we are serving. Journey mapping helps us understand how they experience us. Together, these tools can fundamentally change how cities and counties design programs and services.

We can support employees more effectively. We can make it easier for residents to navigate services. We can also ensure that the resources we do have are used in ways that create the greatest and best impact. In doing so, we protect something that is easy to lose and hard to rebuild—trust.

Residents may not remember the details of a budget decision or a structural change. But they will remember how it felt to interact with their city, and whether the system worked when they needed it most. Those experiences shape trust.

So, in times of fiscal constraint, trust becomes the foundation for effective decision-making. It allows us to make difficult choices, stand behind them, and move forward with our communities. That trust is built by understanding how people actually experience our services, and using that insight to design and deliver them in ways that truly work.

QUISHA LIGHT is the public works customer service division manager for Portland, Oregon.