I didn't take on my current GIS role in state government with a grand vision of public service. I did it for the benefits. After spending years in the private sector, I switched about two years ago, primarily for the healthcare, retirement, and job stability it offered.
I didn't anticipate how much of my job would involve assisting people who aren't GIS experts—and honestly, have no desire to be.
While my primary focus is on GIS development and programming, I spend a significant amount of time assisting users in my division and a few others. These are engineers, permit reviewers, inspectors—people who depend on spatial data for their work but often lack formal GIS training. Many of them feel overwhelmed by the tools.
The biggest misconception I encounter is the belief that you need to be an expert to use GIS. This mindset prevents many people from even trying. They think it's too technical, too complicated, or not for them.
So, I make it my mission to prove them wrong.
If someone's stuck, I'll go straight to their desk and guide them through the process—live, one-on-one, and without technical jargon. At other times, I create custom guides that break down the process with screenshots for each step. I don't assume anything. My rule is to build it as if the person reading has never opened ArcGIS Pro before—because sometimes, they haven't.
One of the best things I've done is create a customized ArcGIS Pro tab that declutters the interface and highlights only the tools our users need. This change makes the program much more approachable. What once seemed overwhelming suddenly becomes manageable. That simple change has helped people feel more confident using GIS in their daily work.
Custom tab created for our users that is simplified and only includes the tools they use.
Sometimes the impact is immediate—someone completes a task and moves on. But other times, the effects spread out. One project I supported involved coal mine permit data and local community impacts. The maps we created were later used in legislative briefings. That's spatial data influencing public policy—not because we used the latest buzzwords, but because the tools were accessible to those who needed them.
Success isn't about creating flashy dashboards or writing perfect code; it's about delivering value. It's about ensuring the tools get used. If I build something powerful that no one touches because it's too complex or intimidating, that's a failure.
I've learned that supporting non-GIS users starts with listening. Set aside the technical ego. Focus on what they need to accomplish, not what impresses other GIS professionals. Your feedback is crucial in this process, as it helps us improve and make the tools more accessible.
My advice to others working in the public sector? Build your tools as if the user doesn't care about GIS because they often don't. They care about outcomes, clarity, and efficiency. Our job is to make spatial data work for them, not the other way around. This approach ensures that we understand and consider the needs of our users, making the tools more effective and accessible to them.
One of our custom add-ins for quickly adding statewide imagery to a map.
GIS has tremendous potential in the public sector, but we'll never fully realize it if the technology remains locked behind jargon and complexity. If we want spatial thinking to spread, we must stop designing for GIS people—and start planning for everyone else.
