An executive asks why a piece of work is taking so long. The team closest to it says they are already moving as fast as it can go. Both walk away from that exchange thinking the other one is wrong.
They are not. Neither of them is lying, and neither is being slow or unreasonable. They are reading two different clocks, and the last post in this series was about exactly that: nobody’s clock feels wrong from where they are standing. But there is a piece I left out on purpose, because it deserved its own post, and it is this. In a room like that one, only one of those two clocks usually gets treated as the real one. That is not physics. That is something else, and it is worth naming plainly.
What does altitude have to do with it?
A quick second idea, borrowed from the same place as the first. Gravity is not just about how close you are to something massive, it is also about how high above it you are standing. A clock at sea level and a clock on a mountaintop tick at very slightly different rates, because the mountaintop clock sits in slightly weaker gravity. Farther from the mass, time passes a little faster. This is not a rounding error institutions ignore. GPS satellites sit far enough above the Earth that their onboard clocks run measurably faster than clocks on the ground, and the system corrects for it continuously, or your phone’s map would drift within minutes.
Here is the part that matters for the room in that meeting. Nothing about standing at a different altitude makes one clock the correct one and the other a deviation from it. Neither position is privileged. The mountaintop clock is not more right than the sea-level clock. They are just different, and the difference is well understood, measured, and accounted for.
Back to the room
Here is where the metaphor stops being about physics and starts being about the room. In actual relativity, no observer gets to declare their own clock the true one. That is not a courtesy extended to everyone equally, it is a fact about how the universe works. But in most organizations, one clock quietly gets treated as the true one anyway, and it is almost always the executive’s.
Not because their reading is more accurate. Because of where they sit. The team’s clock gets treated as a deviation to explain, something running slow that needs correcting, while the executive’s sense of how fast things should move gets treated as the baseline everyone else is failing to meet. That is not a reading of the actual distance between the two positions. It is authority standing in for accuracy, and the two are not the same thing, even when they get handed the same weight in the room.
This is the real cost when it goes unnoticed. Not that executives ask hard questions, they should. The cost is a team quietly bending its own account of its work to match a clock that was never actually theirs to match, because the alternative feels like insubordination rather than what it actually is, an honest reading from a different position.
The correction system
GPS does not resolve the disagreement between the satellite clock and the ground clock by deciding one of them is right. It resolves it by building the actual relationship between the two into the system itself, as a standing correction, checked constantly, not argued about meeting by meeting.
That is what a real semantic contract does inside an organization, and it is worth saying plainly now that the metaphor has a place for it. Not a document that makes everyone agree, a shared instrument that tells you the true relationship between two readings so neither one has to be declared the winner. When an executive and a team disagree about pace, the useful question is not whose clock is right. It is what instrument exists, if any, to show the actual distance between where each of them is standing. Most organizations do not have one. That is the gap, not effort, not honesty, not speed.
Nobody in that room was behind. There was no instrument in the room to show them that.
This is part of a series exploring how AI and conversational interfaces are reshaping data architecture and business intelligence. Previous posts are available at insightsindata.com.
© 2026 Paul Nevill / Insights in Data
