Every Product Has a Mercator Somewhere
One country voted against changing the world map on Friday.
Its reason sounded exactly like a product review.
164 countries backed a UN resolution to move away from the Mercator map. The US voted no. Its argument: the UN should focus on real problems, not 16th century map projects.
I've heard that sentence in product meetings for years.
"It's just the interface. Let's focus on the real work."
The interface is the understanding
The interface is how people understand the real work.
There is no version of the data that reaches a human mind without passing through a representation. The map is how billions of people carry the planet in their heads. The dashboard is how your CEO carries the business in theirs. Dismissing the representation as cosmetic doesn't make it neutral. It just means nobody is accountable for what it distorts. It's the same reflex as an industry spending $2.5 trillion on AI models and almost nothing on making them usable: the conviction that the real work is always somewhere behind the screen.
Brilliant at one job, default at every job
Mercator was built in 1569 for sailors. Brilliant at that job.
A straight line on a Mercator map is a constant compass bearing. If you're navigating an ocean with a quill and a ruler, it's a masterpiece of purpose-built design.
Then it became the default for everything else.
Classroom walls. News graphics. The mental image most of the world holds of itself. A tool optimised for 16th century navigation quietly became the standard representation for questions it was never designed to answer, like how big continents are relative to each other.
On it, Africa looks about the size of Greenland. Africa is 14 times bigger.
Nothing about the land was wrong. The representation was.
Defaults stop looking like decisions
Stay with a representation long enough and it stops looking like a decision.
That's the dangerous part. Nobody has defended Mercator on merit for decades. It survives because it's there, the way the Yellow Pages survived right up until it didn't: not because anyone chose it, but because nobody remembered choosing it.
Products accumulate these constantly. The dashboard that leads with revenue because that's what the founder watched in year one, shaping every meeting since. The alphabetical customer list that buries your biggest account under companies starting with A. The org-chart navigation that reflects how the business is structured instead of how anyone works. The $64 million bus app failed on launch day partly because it represented the transit system the way the agency saw it, not the way a commuter standing in the rain does.
Each one was a reasonable call once, for a specific job, like Mercator was. Then it calcified into "how the product looks," and now it's shaping decisions nobody realises are being shaped.
Finding your Mercator
You find these the way the map critics did: ask what job the representation was originally built for, and whether that's still the job it's doing.
Some questions that surface them. What does our default view exaggerate, and what does it shrink? Who was this screen designed for originally, and who actually stares at it now? If a new hire formed their entire picture of the business from this dashboard, what would they get wrong by a factor of 14?
You won't find the answers in a redesign sprint. You find them by living with the work long enough to know what doesn't belong, which is exactly what "let's focus on the real work" teams never budget for. The distortion compounds silently until, like Australia's weather site, the gap between the data and the representation becomes the story.
It was never just the interface
The UN vote will grind on for years and the wall maps won't change tomorrow. That's fine. The vote matters because 164 countries just agreed, formally, that a representation is a real problem, that "it's just a picture" stopped being an acceptable answer.
Your product's version of that vote is available any time you want to hold it.
Every product has a Mercator somewhere.
---
