GIS Doesn’t Create Complexity. It Just Stops Letting You Ignore It.

Confused?!?!?!

At some point, almost every GIS team hears the same complaint: “GIS makes everything more complicated.” This is usually said right after a map exposes something inconvenient, like the fact that two systems describing the same thing don’t agree on where it is, what it’s called, or who owns it. Naturally, the map is blamed.

GIS didn’t make things complicated. It just showed up with receipts.

Before GIS gets involved, organizations are remarkably good at living with ambiguity. Boundaries are “approximate.” Definitions are “understood.” Data is “basically right.” None of this causes much trouble because the inconsistencies are nicely siloed. Spreadsheets don’t argue with each other. PowerPoints don’t ask follow-up questions. GIS does. The moment you try to put multiple datasets into the same spatial frame of reference, the contradictions stop being theoretical and start being visible.

This is usually where someone decides the GIS is the problem. Not the fact that three teams maintain the same dataset differently. Not the fact that updates happen “when someone remembers.” Not the fact that critical business rules exist only in someone’s head. No, clearly the issue is that the map is being difficult.

GIS has an unfortunate tendency to demand answers to questions organizations would prefer to postpone indefinitely. What exactly is this thing? Where does it start and end? Which version is authoritative? How current is it? These questions aren’t new. GIS just refuses to let them remain unanswered. That refusal is often interpreted as hostility.

I’ve watched GIS get blamed for everything from bad asset data to poor executive decisions. A map reveals a gap, someone doesn’t like what they see, and suddenly the conversation shifts to symbology, projections, or “whether we really need this level of detail.” Translation: can we please go back to a format that lets us ignore the problem?

The irony is that GIS is often introduced specifically to bring clarity. Leaders want better visibility, better analysis, better decisions. What they sometimes forget is that clarity cuts both ways. When systems are incoherent, GIS doesn’t smooth that over. It amplifies it. Spatial data is inherently integrative — it forces assets, policies, and reality to coexist in the same frame. If those things don’t line up, the map is going to make that painfully obvious.

This is why so many “GIS problems” turn out to be workflow problems. Data arrives late. Updates are manual. Ownership is vague. Recovery plans consist of “rerun it and hope.” None of that is spatially interesting, but all of it becomes spatially visible. If you’re seeing this pattern repeatedly, the issue isn’t that GIS is too complex. It’s that the surrounding systems were never designed to be consistent.

There’s also a persistent belief that once something is mapped, it must be authoritative. Maps look finished. Confident. Decisive. That confidence is earned only if the underlying assumptions are sound. Otherwise, you’re just producing very persuasive visualizations of confusion. GIS will happily scale whatever logic you give it, including bad logic, with impressive efficiency.

Over time, I’ve come to see GIS as an organizational diagnostic tool masquerading as a technical system. When it’s hard to work with, it’s usually pointing at something you don’t want to fix: governance, incentives, ownership, or the fact that nobody ever actually agreed on how things were supposed to work. Fix those, and GIS suddenly feels much more reasonable. Funny how that works.

So no, GIS doesn’t create complexity. It just removes the last place complexity could hide. If that feels uncomfortable, it’s not because the map is wrong. It’s because the organization wasn’t as aligned as it thought.

And yes, GIS will continue to get blamed for this. It always does.