The Invisible Distance.

He had been building the wrong feature for three weeks.

Not because the requirements were unclear. They were as clear as we ever made them: a document, a Figma mockup, a brief walkthrough on a Monday call. He had nodded, asked two questions, and disappeared into his work. That was the pattern. I had six engineers spread across four timezones, and this one, based in Monterrey, was among the more capable. He understood the domain. He did not ask unnecessary questions. He delivered.

What I did not know, for three weeks, was what he was delivering.

Part of that was on me. I was the bottleneck for that team and for two others, with a launch date that couldn't move and stakeholders checking in every few days to ask where things stood. I was moving fast enough that I had stopped moving carefully. The weekly check-ins had become status collection exercises. I asked if things were on track. People said yes. I moved on.

The sprint review was the first indication. He screen-shared his progress, and there was a long moment of quiet before our product owner said, carefully, that she thought we had talked about something different. He had built a filtering system. We had wanted a full-text search with filtering and autocomplete combined. The two shared almost no underlying logic. He had worked from an edge case in the requirements document that had seemed, to him, like the central use case. He had built toward it thoroughly and correctly.

Three weeks of work. Sixty hours, give or take. All of it pointed in exactly the wrong direction.

The Gap Between Question and Answer

Distributed engineering teams have a visibility problem. I don't mean accountability visibility, and I don't mean the kind of visibility that managers mean when they ask for status reports. I mean something structural. The distance between when a question arises and when it can be answered is a gap, and in that gap, engineers keep working. They have to. That's the job.

In a co-located team, the question-to-answer gap is measured in minutes. You walk to someone's desk. You ping them and they look up. In a team with a twelve-hour timezone differential, the same gap is measured in half a workday. And a half workday of building in the wrong direction is not a small thing. It compounds.

This is the invisible distance. Not the miles between your office and your engineer's desk. The hours between the moment a question arises and the moment it can be answered.

[Sample continues in the full book.]