There is something interesting about the way we describe completed work. Consider the difference between saying, “They have done it” and “It’s done.” Both sentences communicate that something has been completed, but they direct our attention toward two very different things. The first points toward the person; the second points toward the work itself.
This distinction may appear insignificant, but it reflects a deeper question about how we perceive work, responsibility, and even people.
When someone says, “They have done it,” the work is connected to its creator. We are not merely interested in the outcome; we are interested in who produced it. The sentence carries an element of ownership. It tells us that there was a person behind the result who acted, decided, struggled, solved, or perhaps simply took responsibility for making something happen.
On the other hand, when someone says, “It’s done,” the person almost disappears from the sentence. The work becomes independent of its creator. The question is no longer who did it? but simply is it complete?
This is often exactly what management needs to know.
When a manager asks, “Is the deployment complete?” they may not be asking for a story about the people involved. They need to know whether the deployment is complete, whether the system is ready, and whether the next activity can begin. In that context, “It’s done” is sufficient.
The work has become the unit of communication.
But imagine a different question: “Who handled the deployment?”
Now the person becomes important. Saying “They have done it” is not merely giving a status update. It is assigning ownership. It makes the person visible behind the outcome.
And this is where the distinction becomes philosophical.
Modern work often tries to measure everything through outcomes. Tasks are completed, tickets are closed, targets are achieved, systems are delivered. In this world, there is a temptation to believe that the result is all that matters.
But a result does not tell us everything.
Two people can produce the same outcome while having completely different relationships with their work. One may have taken genuine ownership, understood the problem deeply, and carried the responsibility until it was solved. Another may have simply completed the minimum requirement because the task was assigned to them.
The outcome may look identical from a distance.
The human experience behind it is not.
At the same time, there is another danger. When we constantly emphasize who did something, work can become a competition for visibility. People begin to attach themselves to outcomes not because the work requires it, but because recognition does. Every accomplishment becomes a statement of identity: I did this. My team did this. They did not.
The work then becomes secondary to the story of who gets credit for it.
Perhaps mature organizations need both perspectives.
There are moments when we should deliberately remove the person from the conversation and simply ask whether the work is complete. This keeps communication objective and prevents unnecessary attachment to ownership.
And there are moments when we must put the person back into the picture—especially when recognizing contribution, assigning responsibility, giving credit, or understanding why a particular outcome occurred.
The deeper lesson is that language reveals where our attention is placed.
“It’s done” looks at the destination.
“They have done it” looks at the person who walked there.
Neither perspective is inherently better. The mistake is assuming that one should always replace the other.
A task is not a person. And a person is not merely a task.
Good communication knows when to focus on the work and when to acknowledge the human being behind it.
Perhaps that is one of the quiet forms of wisdom in professional life: knowing when the person should disappear behind the work, and when the work should remind us to see the person.