What Commit Timestamps Taught Me About Remote Team Trust
A few months ago, I was reviewing a project timeline that didn't add up. The work was clearly done — the code was solid, the feature shipped on time — but the activity log told a strange story. Long gaps during "core hours," then a burst of commits late at night.
My first instinct was the wrong one: is this person actually working when they say they are?
But the more I looked at it, the more I realized the question itself was broken. The commit timestamps weren't evidence of someone slacking off. They were evidence of someone doing their best work on their own schedule — early morning for some, late night for others — and getting judged against a 9-to-5 mental model that doesn't apply to distributed teams anymore.
The real problem wasn't the person. It was the visibility.
We didn't have a way to see outcomes — only fragments. A commit here, a Slack message there, a deadline that either got hit or didn't. Everything in between was invisible, so we filled the gap with assumptions. And assumptions about people's work habits are almost always wrong, and almost always unfair.
What actually changes this
The teams that handle distributed work well aren't the ones watching the clock closest — they're the ones that shifted from presence-based trust to outcome-based trust. That shift needs two things:
Real data, not fragments. Not "were they active between 9 and 5," but a genuine picture of work happening across the day — when someone's actually focused, when they're blocked, when a deadline is at risk before it's missed.
Transparency in both directions. If a tool is watching someone's work, that person should be able to see the same data their manager sees. One-way monitoring breeds resentment. Shared visibility builds trust.
That second point is the one most monitoring tools get wrong. They're built for managers to watch employees, not for teams to see their own work clearly. That asymmetry is exactly what turns "monitoring" into "surveillance" in people's minds — and once it feels like surveillance, you've lost the trust you were trying to build in the first place.
We ended up rethinking this problem from the ground up while building TrackDots — specifically around the idea that visibility has to work for the employee, not just the manager, or it doesn't actually solve anything.
The commit timestamps weren't a red flag. They were a sign that our old way of measuring "working" needed to catch up with how distributed teams actually work.
