Maps should answer human questions
A practical note on spatial UX, public-good tools and why useful maps should start with the decision a person needs to make.
A useful map is not just a picture of where things are. It is a decision surface for someone who needs to do something next.
The map is rarely the question
It is easy to treat a map as the product. Put the points on it, add a search box, cluster the markers, and the interface looks finished.
But most people do not arrive with a cartographer’s question. They arrive with a human one: where is the nearest toilet I can actually use, which bin goes out tonight, where is that vessel moving, what is open now, what is close enough for the person I am with?
The map matters because it gives those questions shape. It shows distance, direction, density, and gaps faster than a table can. But the map is still a means, not the end.
Start with the decision
Good spatial interfaces start by asking what decision the person is trying to make. That sounds obvious, but it changes the whole build.
If the decision is “can I get there quickly?”, then distance and route confidence matter more than a beautiful marker. If the decision is “is this place suitable?”, then access notes, opening hours, baby-change details, and source confidence might deserve more space than the map itself.
The best map view is the one that helps a person stop inspecting the map and make the next good decision.
Show the useful uncertainty
Public-good tools often sit on imperfect data. Facility records age. Council boundaries do not line up with lived geography. Source systems disagree. A GPS coordinate can be technically valid and still slightly wrong in the way a person on foot will notice immediately.
That does not mean the interface should become defensive or complicated. It means uncertainty should be designed into the surface. Show when a record was sourced. Separate verified facts from helpful hints. Let the person understand why two nearby results are different.
A map can be calm without pretending the world is cleaner than it is.
Reduce map work when you can
One of the better signs in a spatial product is that people spend less time dragging the map around. Good defaults do a lot of heavy lifting: local search, sensible zoom, nearby-first ordering, visible filters, clear selected states, and copy that says what matters without making the user decode the data model.
This is especially important on mobile. A map that works beautifully on a desktop can become fussy when it is held in one hand on a footpath. Hit targets, sheet height, contrast, loading states, and the order of information start to matter more than the clever map layer.
Spatial work is interface work
I like maps because they make product decisions visible. You cannot hide a vague data model for long when the result has to exist somewhere. The interface has to decide what counts as near, what counts as available, what deserves emphasis, and what should happen when the location signal is missing.
That is the satisfying part. A good spatial interface joins design, engineering, accessibility, and source data into one practical answer. It respects the complexity underneath, but it gives the person something simpler: a next step they can trust.
That is the standard I keep coming back to for public-good tools. Not more map features for their own sake. Better answers for real situations, placed exactly where someone needs them.