Ownership vs responsibility: why "it's not my job" happens on good teams

On most teams, everyone does their part. The designer delivers the design. The developer builds it. The account manager sends it to the client. And still, somehow, the project lands late, with something missing that everyone assumed someone else had handled.

That is the gap between responsibility and ownership.

Two different things

Responsibility is about tasks. "I am responsible for the design." When the design is delivered, responsibility is fulfilled.

Ownership is about outcomes. "I own the launch." The owner cares about whether the whole thing works, including the parts they do not do themselves.

Teams with plenty of responsibility and no ownership are full of people doing their jobs well while the project drifts.

Where the gap shows up

• Work handed over and never checked on: "I sent it to them"
• Problems spotted and not raised: "Not my area"
• Decisions nobody makes because nobody feels entitled to
• Projects that stall in someone else's inbox

None of these are laziness. They are what happens when ownership is unclear.

Make ownership explicit, at the right level

Not every task needs an owner beyond the person doing it. Every project does. One person who owns the outcome, keeps an eye on the whole thing and chases the handoffs. See the single-threaded owner.

Own your handoffs

The most practical form of ownership for everyone else is owning your handoffs. When you pass work to someone, you still care whether it arrives and gets done. That means:

• Making the request clear
• Knowing when you sent it
• Checking back if it goes quiet

On a 2D board, handed-off work sits in Other with the person's name and how long it has waited. In Axtio, items over a week are flagged for chasing. That small visibility turns "I sent it" into "I sent it, and it is still with Dana after eight days, so I will check in." See the handoff is the work.

Ownership without micromanagement

Ownership is not about watching people. It is about watching the work. An owner who can see where every action sits does not need to ask people for status updates, which is what makes micromanagement unnecessary. See team accountability without micromanagement.

A simple team agreement

• Every project has one named owner
• Everyone owns their handoffs
• Anyone who spots a problem raises it, even if it is not their area

Three sentences, and most dropped balls disappear. See accountability in a 2D world.