Collaboration Deflation

The Augmented Practitioner — Interlude No. 1

After two hours with AI every morning, my colleagues haven't gotten worse — I have.

I've been sitting with that sentence for three weeks, trying to decide if it's honest or just convenient. I still don't know. What I do know is that it keeps arriving at 9:30 AM, uninvited, when the first meeting of the day begins and the other window — the one where the real work was happening — is still open on my second screen.

I'm a consultant. I have spent two decades helping organisations see themselves clearly enough to change. I am, apparently, significantly less useful at this when the patient is me.

For the past several months, my working day has had two distinct phases.

The first begins before anyone else arrives — just me, strong filter coffee, and an AI that does exactly what I ask, exactly as I mean it, faster than I can fully articulate the need. Strategies drafted. Frameworks stress-tested. Content shaped. Problems I've been carrying for days resolved in twenty minutes. By 9:30 AM I have already produced what would constitute a full working day by any reasonable measure of output.

Then the meetings begin.

And here is where I run into the limits of my own self-knowledge. Because what I feel in those first few minutes — before I've adjusted, before the professional muscle memory kicks in — is not something I have a clean name for. It is not contempt for my colleagues. It is not impatience exactly, though impatience is the closest word in the dictionary.

It is something more like grief. A small, specific grief for the quality of attention I had an hour ago, and the knowledge that I won't have it back until tomorrow morning.

Is that what you feel too? I'm asking genuinely. Because I haven't found anyone willing to say it out loud yet.

I'm going to try to name what's happening, with the caveat that I'm working from the inside of the condition, which is not where diagnostic clarity usually lives.

I'm calling it Collaboration Deflation.

It is what happens to a practitioner whose daily experience of AI-augmented work has permanently shifted their reference point for productive collaboration. Not frustration. Not burnout. Not arrogance, though it can be mistaken for all three — including by the person experiencing it.

The mechanism, as best as I can reconstruct it from the inside:

When you work with AI, the gap between intent and output compresses to near-zero. You think something — the AI produces it — you react — it adjusts. The feedback loop runs in seconds. Over time, and I think this happened to me without my noticing, your nervous system calibrates to that loop. It becomes the baseline against which all other collaboration is measured.

When you return to human collaboration, the gap reopens. Your colleague needs context you've already internalised. They interpret the brief through their own frame. What returns is adjacent to what you asked for. The timeline is days, not minutes. And you experience this not as normal — because it is normal, it was always normal — but as loss.

Deflation is the right word because it is precise. The value of human collaboration hasn't fallen. Your denominator changed. Everything is now being measured against a standard no human collaborator was built to match.

I should be able to advise a client through exactly this kind of cognitive recalibration. I do it regularly. I am finding it considerably harder to advise myself.

There are three textures to the experience, and I want to name each one because I suspect you'll recognise them.

The first is velocity. You completed in two hours what your colleague will spend three days on. You know this before they've said a word. You carry that knowledge into the meeting and it changes the quality of your listening — not maliciously, but measurably.

The second is fidelity. You said what you meant. The AI did exactly that. With a human colleague, the same instruction travels through their context, their current workload, their interpretation of what you really meant. What returns is close, not precise. You find yourself re-explaining. You find yourself wondering — not unkindly, but persistently — why.

The third is the pull. The most insidious of the three. It isn't just that the meeting feels slower. It's that part of your attention never fully left the other window. You are physically present. Cognitively, you're already back there — thinking about the next problem AI will help you solve, the next thing you could build before anyone else arrives tomorrow. The meeting is happening to you. The real work, in your mind, is waiting.

I notice all three of these in myself. I don't have a clean solution to any of them. A consultant who cannot prescribe for himself is a particular kind of uncomfortable.

India adds a weight to this that I don't see named elsewhere.

In the consulting practices I've operated in and around for twenty years, knowledge transfer has always been a relationship built slowly. Senior to junior, over months and years of proximate work. The junior colleague who needs extensive briefing before delivering isn't failing. That's the system working as intended. The senior's patience — the willingness to explain, correct, re-explain — is how capability compounds in this market.

Collaboration Deflation corrodes that patience quietly.

When every briefing feels like friction, when every correction feels like a tax on time you could spend with a tool that needs neither, something breaks in the mentorship chain. Not dramatically. Quietly. The senior becomes less available. The junior receives less. The gap that was supposed to be closing stays where it is.

I have watched myself become less patient in exactly this way. I haven't asked my team whether they've noticed. That conversation is still ahead of me and I am — I'll be honest — not entirely sure I'm ready for what they might say.

Here is the part I didn't expect to find when I started writing this.

Collaboration Deflation doesn't stay where it begins.

It began for me at the AI-to-practitioner interface. That first deflation I've described as honestly as I can. But somewhere in the months since, a second deflation appears to have started — one level downstream, at the practitioner-to-team interface.

The same mechanism. Different players.

My attention, increasingly drawn to what else I could build with AI — the next framework, the next system, the next problem I could have resolved before anyone arrived — has made me a less present collaborator for the people who depend on me. I am, it seems, doing to my team what AI did to me.

I haven't confirmed this. I'm working from observation and suspicion, not feedback I've actually sought. But the practitioner who cannot see this possibility in himself is not being rigorous. He's being comfortable.

The question I cannot answer — and the reason I'm writing this rather than keeping it in a private note — is this:

If AI augmentation makes the individual practitioner dramatically more capable, but quietly makes them a worse collaborator, what exactly have they gained?

I don't know. I'm not sure the question has a clean answer yet. What I am fairly sure of is that the practitioners who figure out how to hold both states — the augmented and the collaborative, without one corroding the other — will have an advantage that compounds over time.

I haven't figured it out. I'm at the stage of having named the problem, which in consulting we sometimes call progress, and sometimes call avoidance.

If you recognise any of this, I'd genuinely like to know. Not because I have the answer. Because I suspect the answer, when it arrives, will need more than one practitioner's experience to be worth anything.