When Asking AI Means Asking People Less

Nobody misses the questions we no longer ask each other. They were friction, every one of them. They interrupted somebody mid-task, cost a senior engineer ten minutes, and came back with a paragraph an agent now produces in four seconds with the offending commit attached. Every reason to be glad they are gone holds up. Something still leaves with them.

The shape of it is familiar enough that you can probably date your last one. You open a file you have never touched and find a conditional that makes no sense — three lines guarding an edge case that, as far as you can tell, cannot happen. A few years ago the next move was almost automatic: check the blame output, find the name that keeps appearing, type some version of hey, do you remember why we do this here?

Somebody answers. The exchange takes ten minutes, most of it on the two tangents that were not the question. You get your reason — an integration that broke one December, a workaround that outlived its cause. You also get things nobody set out to hand you. You learn who carries that part of the system in their head. They learn what you are touching this week. A risk gets mentioned sideways. Two weeks later they ask how it went, because they had become, without deciding to, slightly invested.

Today that paragraph arrives from an agent with repository context, drawn from the same history. The explicit problem gets solved cleanly, without waking anyone. What does not get solved is everything the conversation was doing on the side.

Which leaves a question our rituals were never designed to answer. What happens to a team when needing each other becomes optional?

The invisible half of a simple question

Every interaction at work has a technical value and a social value, and only one of them ever appears in a ticket. The technical value is the thing you asked for: the reason behind the conditional. The social value is the engineering work that leaves no commit around it: who now knows what about whom, which parts of the system turn out to be confusing, who owes whom a small favour they will never call in.

For most of software's history, you could not buy the first without paying for the second. They arrived in the same envelope.

There is a sentimental version of this argument that I do not believe. Interrupting a colleague so that human interaction can occur is absurd. Waiting thirty-five minutes for a colleague in another time zone to explain what a machine explains instantly is not collegiality, it is waste dressed as culture. When Hadley and Wright surveyed 1,545 US knowledge workers who use AI at least monthly, 65% said they turn to AI tools before asking a colleague for help. That is a rational choice about somebody else's afternoon, not evidence of anything decaying.

That is what makes the aggregate hard to see. The decision is rational every single time, and the consequences only show up after a few thousand of them.

Help-seeking as two-way telemetry

Asking for help is often read as a deficit state — proof that someone lacks knowledge, tolerated in juniors and counted against everyone else. It is also a relationship-building behaviour, and that second reading is the one that matters. When you ask a person for help you say two things you would never say out loud: that they know something you do not, and that you trust them enough to show the gap.

The person answering receives a different set of signals. They learn what you are working on, where you got stuck, which subsystem is hard to hold in your head, which documentation has gone stale, and where they might be useful this week.

That is the part I have started thinking of as telemetry. Help-seeking runs in both directions: the asker gets an answer, the team gets a reading of its own state. Nobody instruments it or stores it, but it is a kind of ambient information no survey was designed to capture.

An agent preserves the first channel beautifully and drops the second on the floor. A three-wave study of 303 service employees in China found that closer collaboration with AI predicted less professional help-seeking, partly through what the researchers call psychological availability: people felt resourced enough to handle things alone. Survey data, one country, a sector that is not ours. The mechanism is still worth sitting with. AI does not make asking a person harder. It makes you feel capable of not asking.

The shrinking social surface area

Call it social surface area, for want of a name that already exists: the small, unplanned points of contact a team generates while working. A question in a thread, ten minutes of pairing, a second opinion on something half-formed, two people staring at the same stack trace and disagreeing about it.

Nobody scheduled any of it. It happened because the work required it.

A team can lose most of that surface area without losing any of its formal communication. The standups survive. So do the retros, the planning sessions, the 1:1s, the Slack channels. On paper you communicate as much as before. Underneath, there are fewer situations in which you genuinely need one another, and needing is what helped turn communication into familiarity.

Teams can talk constantly and still become less interdependent. Those are separate variables, and we only ever watch one of them.

In Stack Overflow's 2025 survey, 68.7% of developers using AI agents agreed the agents had increased their productivity, while 17.3% agreed they had improved collaboration within their team — the lowest-rated effect in the set, by a wide margin. That is not proof that agents damage collaboration, only a picture of where the benefits are legible. We measure the hours an agent saves. We rarely measure the conversation that no longer happened.

The limits of psychological safety

For years, engineering organisations have spent a lot of energy making it safer to ask. Safe to admit you do not understand the deploy pipeline, safe to show work that is not finished, safe to say I don't know in a room where everyone else is nodding. Building psychological safety in engineering teams has been, correctly, one of the load-bearing projects of engineering leadership.

Most of that work went into reducing the cost of asking. AI changes a different variable: the need to ask at all. Safety ≠ necessity — you can build a team where asking is free and simultaneously remove most of the reasons anyone would. The old failure mode was someone sitting on a question for three days because they were afraid of looking slow. The new one is someone not having the question long enough for anybody to see it.

The engineer who suddenly looks autonomous

Here is where this stops being philosophical for anyone who leads people.

A junior engineer on your team starts asking fewer questions. Their pull requests are cleaner. They unblock themselves. By most of the signals we use, this reads as growth, and it might be — but it reads the same way when someone has moved every question to a system nobody else can see. Call it Silent Unblocking: resolving your confusion privately and completely, so fast that no one around you learns you were confused.

The learning can be real. The learner's side of the exchange does not necessarily disappear — yours is the side that does. You no longer see the mental model, the assumption that was slightly off, the three subsystems generating most of the confusion. The questions were a map of where understanding was thin, and the map has gone dark while the territory stayed exactly as it was.

Fewer questions has become one more broken proxy for engineering seniority, still read as if it meant what it used to. I have written before about what the individual stops absorbing. This is the narrower loss: what the room stops seeing.

The practical version is smaller than it sounds. In a 1:1, "what did you get stuck on this week?" surfaces almost nothing now, because getting stuck lasts ninety seconds. Lately I have been asking a clumsier version instead. "What did you work out alone this week that you would have asked someone about a year ago?" It gets closer to the map.

The dependency nobody designed

Needing expertise created dependency. Dependency created interaction. Repeated interaction created familiarity. Familiarity made the next question easier to ask, and answered questions left a loose reciprocity — the person who once walked you through the billing flow when you first joined, and whose review request you still open first. Nobody designed this. No one budgeted for it or wrote it into a working agreement. It was a side effect of work requiring other people.

So a fair amount of what we call team cohesion has been running on accidental infrastructure. Not built. Not maintained. Load-bearing, and invisible until the conditions that produced it change.

I am not arguing that the dependency was good. Some of it was gatekeeping; some was undocumented knowledge hoarded by people who enjoyed being asked, and removing that is an improvement. The uncomfortable part is narrower. We are dismantling a mechanism we never acknowledged was one.

The case against my own worry

The evidence gets inconvenient here, in a useful way.

In Gensler's 2026 survey of more than 16,000 office workers, the people using these tools most heavily reported stronger team relationships than their peers, not weaker ones, and spent less of the week working alone. Selection effects may explain some of that, but the correlation runs against the isolation story rather than with it. Hand knowledge workers a generative AI tool and, in a randomised field experiment, they claw back about two hours a week from their inboxes and work fewer evenings. Fewer evenings in an inbox is not a cost to mourn. Someone who arrives at a discussion having already worked through the obvious questions is a better colleague, not a worse one.

And AI clearly did not invent workplace loneliness. Loneliness at work was sitting alongside burnout and lower job satisfaction long before any of this arrived.

Though the Hadley and Wright data holds one detail I cannot put down. Half of those knowledge workers described themselves as moderately or highly lonely at work, and three-quarters had used AI for some form of social support. Only 12% said it made them feel any less lonely while they worked. Whatever people get from these tools, it is not the thing the relationships were providing.

AI is not making work lonely. That is the wrong charge, and aiming at it lets the real question pass. What AI changes is which human interactions are structurally necessary — and whether work gets lonelier depends on what moves into the space the necessary ones used to occupy.

Final thoughts

I have no interest in defending the old friction. Every minute somebody sits blocked on an answer another human happens to be holding is worth reclaiming, and the tools that reclaim it should be used without guilt.

The thing worth holding onto is smaller and harder. When you automate an interaction you remove more than the transaction it contained, and the remainder was doing unrecorded work: exposure to somebody else's unfinished thinking, awareness of what your colleagues are struggling with, the chance to teach, the chance to ask, the context that never reaches a document. None of that requires inefficiency. It only ever arrived that way. Because the friction was never the thing doing the work. It was only what the work came wrapped in, and it is easy to mistake the wrapper for the contents.

So the task is not to talk to each other more. Needing each other used to be the mechanism — it made knowing, trusting, and helping each other happen without anyone having to want it. And it is being decommissioned quietly, one perfectly reasonable question at a time. That is probably an improvement, and I would not undo it even if I could.

What I am less sure about is the part nobody owns. Whatever replaces it will have to be built deliberately. The harder part may be noticing that anything disappeared at all.