The argument · open work · 2026
The Economics of the Other.
Seven short sections, and the ways I might be wrong.
What happens to work when it no longer has to pass through another role? What I think gets lost, why nobody notices, and what you can do about it.
open studyThis argument needs other positions. Share a passage from your own work1 · Why does every week go well and the year go badly?
A meeting booked by an agent. Everyone has read the summary. The actions arrive before the call ends. By every measure, a great hour.
A month later the decision comes back. Someone says but we agreed, and the agreement is in the summary, not in the people.
Nothing went wrong in that hour. The hour was meant to do two jobs, and we only check one of them.
2 · One trip, two jobs
A junior has a difficult client email to answer. She takes it to her manager. He asks a question, says no to one line, and sends her back to rewrite it.
The email gets better. That is the first job. But two other things happened on the way: she got a little better at this, and he now knows what is going on with that client. One trip did both jobs.
Every organisation runs on these two jobs at once. I call them producing and forming. Producing is what gets done: it is counted, owned, on a dashboard. Forming is what takes shape between roles, and nobody can make it by decree. In the passage, judgement, responsibility and know-how form. From what held, trust forms. None of it has ever been counted, because it never had to be. It came free with the trip.
Work produces the output, and it forms what lets the work be done again. Only the first is on the books.
3 · AI removes the trip
Before, if you didn’t know something, you had to ask someone. If your argument was thin, someone pushed back. Nobody designed that. It just happened, and it did a second job: people learned, and decisions got an owner.
Now the answer arrives in two minutes, and it’s often very good. The junior asks the AI, and the email is fine, maybe better. The first job still gets done. The second one quietly stops.
I call the trip a passage: a moment where your work goes through another role that could change it, or say no. So the question to ask of any piece of work is simple: what does this no longer have to pass through?
Sometimes the trip was only friction. If the work didn’t need it to form, nothing is owed. Let it go.
But when it did, something is left behind. I call it relational debt: what didn’t have time to form between roles, because the work closed first.
4 · Nobody is waiting, so nobody notices
A debt usually has someone waiting for it. Here, nobody is. The manager was never asked, so he isn’t waiting for anything. Nobody sends an invoice for a lesson that wasn’t learned.
The bill comes later, under other names: work that has to be redone, a junior who still can’t handle the client, the one manager who ends up carrying everything nobody owned.
With AI agents it goes further. A study of 33,707 pieces of code written by agents found them abandoning the work as soon as a person asked for a real change (Minh et al., 2026). The agent opened the loop, and nobody could hold it to closing it.
The debt is real, but nobody is waiting to collect it. That is why it grows.
5 · It turns into culture
A junior doesn’t just miss one lesson. She learns that this is how work is done here. A team doesn’t just skip one disagreement. It learns that a clean finish beats an honest argument.
What wasn’t made is the debt. It accumulates when the way of working that produced it becomes what is valued, what is allowed. After a while, we call that culture. Something always forms. If not judgement, a habit.
6 · “But we keep a human in the loop”
The manager signs off the AI’s draft. He was in the loop. But he didn’t say no, didn’t send it back, and learned nothing about the client.
Approving isn’t forming a judgement.
The question isn’t whether a person saw it. It’s whether another role could have changed it, and whether that would have mattered.
a role counts only if its no could have changed what happened next
7 · So what can you do?
You can’t order people to collaborate. Tell a team to speak up, then give them a two-day deadline: asking the strategy lead means waiting until Monday, and the AI answers now. Nobody decided the strategy lead doesn’t matter. The deadline did.
In one team’s weekly review, each person opens with a doubt instead of an update: one thing they don’t know yet. It takes ten minutes. It’s where the questions that used to go to the AI at six in the evening start arriving.
For each passage, a team has three choices. Automate it, if nothing is needed there any more. Protect it, so a question can stay open long enough to find out whether another role is really needed. Or redesign it, so reaching the other role is worth it, and its answer can still change the work.
How I might be wrong
- Maybe organisations need much less of this than I think. Then most of what I call debt is a cost rightly removed, and I have to be able to say so in the room.
- Maybe people learn anyway, from practice, or from the AI itself. Then the trip mattered less than I think.
- Maybe the bill never comes. If teams that remove these trips show no later loss of judgement, ownership or skill, then it isn’t debt.
- Maybe a designed trip doesn’t work like the old, accidental one. Then my diagnosis stands, and my remedy doesn’t.
The strongest evidence against me: at Procter & Gamble, individuals working with AI did as well as teams working without it (Dell’Acqua et al., Organization Science, 2025). I agree. One person plus AI can now do what used to take two, for work one person can do.
The question I’d leave you with
Pick one piece of work this week, and ask:
What does this still need to form between roles, and not just to get finished?
If the answer is nothing, automate it. If the answer is something, don’t keep the old friction. Design the trip that still needs to exist.
That is the work of altraparte.