You can't deploy cohesion

I was an offshore outsourcer. For years, my job wasn't to govern delivery centers from afar: it was to go set them up, then fly back — physically, regularly — for a reason no SOW could ever put into words. Cohesion. Making the team over there and the team over here feel like they belonged to the same project. You don't steer that from a dashboard. You get on a plane.

Eleven years ago, I resigned. Not out of weariness: out of clarity. I could see DevOps, the twelve-factor app, the cloud and containerization dissolving the very problem I was paid to solve. Distance was becoming cheap to cross. Proximity — co-located squads, you build it you run it, the product owner in the room — was winning the war. My job, the guy you send to rebuild connection across the boundary, was becoming a relic. I was right to leave. I'm starting to think I was wrong to believe the muscle had died with it.

Covid was the first reminder. Overnight, entire organizations went back to managing opaque, distant, instrument-governed teams — and I felt the old reflex switch back on, before most people grasped what was happening. The distance agile thought it had killed wasn't dead. It had just been hidden by the shared office.

Agents are the second reminder, and the harsher one. Deploying a fleet of agents means reinstating the exact distance I spent my career crossing — except there's no one on the other side to visit anymore. You don't grab a coffee with an agent. You don't align a fleet over a team dinner. The thesis of this post, stated bluntly: agile won the proximity war so completely that it destroyed the muscle that managed distance — and we are now redeploying distance without the tool that used to close it. You can't deploy cohesion.

Forget the offshore you think you know

Before we go further, I have to kill a lazy reading, because it's the one that will make you tune out. When I write "offshore," you probably hear "cheap labor, far away, to drive costs down." That's the decorative version. It isn't the useful one here, and it isn't even the one that made delivery centers live or die.

What offshore actually produced was a social machinery: the whole set of rituals, templates and gestures we invented to collaborate across an opaque boundary with someone we couldn't watch work. The real problem was never the hourly rate. That was the line in the business case. The real problem — the one that sank a twenty-million-dollar center while another ran fine — was trust, alignment and knowledge transfer across a distance. Cost was the sales pitch; distance was the job.

And that's precisely the distinction agile blurred by winning. By removing the physical distance — co-located squads, embedded QA, continuous delivery — it made the social machinery invisible, then superfluous, then forgotten. We didn't decide that managing distance was pointless. We simply stopped having any distance to manage. The skill didn't expire: it lost its training ground. For a decade, nobody needed to board a plane to rebuild connection, because everyone was already in the same room — or one video call away from it.

Deploying agents reopens that ground. You suddenly inherit an industrialized, opaque workforce "on the other side" — and you discover that the gestures to manage it have been unlearned. Worse: some of them don't replay at all. That's where the inventory begins — what transfers, what has to be reinvented, and the one reflex that will betray you.

What transfers

Two offshore disciplines replay almost unchanged on a fleet of agents.

Trust across opacity. I never watched an offshore developer code. I built rituals to manufacture a trust I couldn't observe directly: acceptance criteria, milestone reviews, quality gates, reporting. Exactly what you're rebuilding today around an agent — eval gates, human review, the approval ritual. The problem is identical: producing trust without seeing the work. The offshore reflex transfers with no retrofit, and it arrives pre-trained.

Knowledge transfer into the box. The SOW we wrote until it hurt, the runbook, the spec "so detailed it stings" — that's your context, your prompt, your agent spec, reincarnated. Same discipline, and above all same failure mode: under-specify, and the box produces something plausible and wrong, exactly the way the offshore center delivered a badly written instruction to the letter. Anyone who suffered through a sloppy SOW already knows why your agent goes off the rails — and knows the answer isn't "a better model," it's "a better instruction."

What has to be reinvented

Here the transfer stops cold, and this is the heart of what I have to say.

The part of my job that had nothing to do with steering was cohesion: the travel, the team dinner, the physical presence that made two teams six thousand kilometers apart feel like they belonged to the same project. That gesture has no agent equivalent. You don't fly out to align a fleet. There's no one to shake hands with, no one to put at ease, no one whose cultural deference hides a disagreement a good dinner would draw out.

Which means cohesion, on the agent side, doesn't transfer: it gets reinvented, and it moves. It no longer lives between you and the box — there's nothing in the box to align. It lives between the humans in contact with the box. Your developers, your QA, your operators who each prompt, correct and approve a little differently. The drift I used to fight — twelve onshore principals, twelve subtly different instructions to a single center — replays in full, but entirely on the onshore side. The cultural boundary is no longer between here and there. It's between you and your colleague next to you, mediated by an agent that amplifies your divergences instead of absorbing them. The muscle to reinvent isn't "govern the agent." It's govern the coherence of the humans holding it — without the tool that used to work, proximity, since it's already there and solved nothing.

What betrays you

That leaves one reflex, a single one, and it's the most dangerous because it's just close enough to seem transferable.

Offshore trained me for dilated time. The correction loop was expensive and slow: time-zone gaps, overnight round-trips, loss of real-time feedback. Hence the reflex: over-specify up front, batch the feedback, because a late correction is prohibitively costly. Twenty years of distributed delivery carved that reflex into a generation of managers.

The agent inverts all of it. The loop is collapsed: correction is free and instant. The manager who replays the offshore reflex will over-specify and under-iterate — write the giant SOW, launch, wait, inspect — exactly where the agent's economics reward the opposite: thin spec, fast loop, correct in the moment. And the irony closes: collapsed time is precisely the reflex agile sold me eleven years ago. The one I resigned for. The synthesis nobody holds yet is offshore-style trust governance running at agile cadence — the muscle of distance, but wired onto the short loop. Neither the offshore veteran nor the pure agilist has it: the first has the governance but the wrong tempo, the second has the tempo but forgot the governance.

The role we deleted

Look at your org chart. The platform team owns the plumbing. The data team owns the models. Who owns the coherence of the humans in contact with the box — the drift across ten operators, the alignment of instructions, the trust you can't observe? Nobody. The box is empty.

It wasn't always empty. It had a name: the delivery manager, the service transition lead, the person you sent to rebuild connection across the boundary. Agile deleted that role because it had deleted the boundary — and it was right, as long as the boundary stayed deleted. Except we've just reopened it. We erased the role exactly as it became load-bearing again, and today we hand the hardest part — coordinating opacity — to the team least trained for it, convinced it's a tooling problem.

So here's the bet, dated, that you can throw back in my face in eighteen months: the teams that succeed at agent deployment at scale won't be the ones with the best platform, but the ones that rebuilt the muscle of distance — and they'll go find it among the very people agile declared obsolete. Not for their platform. For their scar tissue.

I left eleven years ago certain this job was finished. I'm starting to put my certainties away. You can deploy a fleet in an afternoon; you can't deploy the trust that holds it together. That one you still have to go and get — and there's no plane to catch anymore. You can't deploy cohesion. That's the whole problem, and it's yours now.