“Claude Did It” Isn’t a Description. It’s a Handoff
At the end of a call, minutes before the next meeting, a colleague gave a name to something that had been on my mind for a while: the personification of Claude.
“When we say Claude did this instead of I did this with Claude, we’re personifying it — this sounds like handing it the responsibility for the code we produce.”
We spent the last minutes of that call searching for patterns we could learn from this insight. Here is what I’ve learned from this conversation.
The Handoff Has No Receiver
Grammar is quietly generous. Make something the subject of a sentence and you grant it agency — and agency drags accountability behind it. “Claude did this” has exactly the shape of “John did this”: an actor, an act, and someone to answer questions about it later.
Except a terminal tool doesn’t attend the incident review.
Put to good use, it can help with design decisions that have been taken, but it doesn’t have a preference for this abstraction over that one, and the exact context that was used today won’t be here next quarter explaining the migration path. It can help, but cannot be accountable — not because the models aren’t good enough yet, but because accountability isn’t a capability. It’s a relationship between people.
So the handoff in “Claude did it” never completes. Responsibility leaves the speaker and arrives nowhere.
The sentence doesn’t transfer responsibility to the tool. It evaporates it.
The Sentence Predicts the Review
Let me be fair to the phrasing first, because nobody says “Claude did it” in order to dodge anything. It’s shorthand, and in the narrow mechanical sense it’s even accurate — the model did produce those lines. That’s precisely why it spreads: it is true about the typing and false about the owning.
And substitute Copilot, Cursor, or whatever name your team’s tool answers to — the grammar works the same.
But the framing has a cost, and the cost lands in a specific place: code review.
Say “Claude did it” often enough and you start standing next to your own diff instead of behind it. You feel a little less obliged to understand what was produced — and that is the classic “looks good to me” review: approved by someone who was never quite its author, merely nearby when it happened.
“I did this using Claude” reverses the stance before the review even starts. The diff is mine. The model was leverage, the way the compiler and the framework are leverage. If it’s wrong, the failure sentence starts with “I”.
None of this says people stop being responsible for their work the moment they phrase it badly. It’s a risk, not a verdict. But it’s the kind of risk that compounds quietly, one unexamined pull request at a time.
Leaders Set This Standard Further Than They Intend
Here’s where this stops being a style preference.
Habits of speech don’t spread evenly through a team — they spread from the people others calibrate against. When a team lead says “Claude built this service,” in praise or in complaint, the team hears something more durable than the sentence: this is how we talk about ownership here. The standard travels further than the intention. Nobody decides to set it. It gets set anyway.
Which means the cheapest AI-governance instrument available to anyone running a team is the grammar of their own standup sentences.
We don’t hand AI responsibility for the code we produce.
My colleague said that in passing, as something obvious. I’ve read policy documents ten pages long that speaks about the same and still commit to less.
What I Take From This Conversation
Not a rule about language — correcting other people’s sentences only turns a useful observation into an office joke.
What I took was an agreement with myself: this is how I talk about my work now. The price is the free excuse — “Claude did something weird” — and what it buys back is every line I merge being mine again.
The surprise, after sitting with it for a while: the effect is upstream of the sentences. Knowing the work gets reported as “I did this using Claude,” I make the many tiny decisions — merge this diff or read — in a way I won’t hesitate to take full responsibility for. A different agency model, not a different phrasing. The price is paid in installments too small to notice.
And that’s the part that counts: the standard my team absorbs won’t come from anything I announce about AI. It will come from the subject of my sentences — and the actions that follow.
Listen for it in your next standup: which sentence does your team reach for when the demo works — and which one do you reach for when production breaks?