Who Owns What Happens Next?
Completing your responsibility and owning the outcome aren't always the same thing.

Have you ever followed up on something only to hear, "I sent that to ______"?
Technically, the person did what they were supposed to do. They received the information and passed it along to the right person. But if nothing happened after that, who owned making sure it did?
This is one of those situations where individual responsibility and organizational ownership aren't necessarily the same thing. We can clearly define what each person is responsible for doing and still leave gaps in who is responsible for making sure the work actually moves forward.
Think about a customer who calls with a problem. The person who answers can't resolve it, so they send a message to someone who can. Their responsibility may have been to route the issue to the right person, and they did exactly that. But the customer doesn't care that the message was successfully routed. They care that their problem gets resolved.
The same thing happens internally. An employee receives information another department needs and forwards the email. Someone completes a form and submits it. A manager asks a team member to take care of something and assumes it's now handled. Each action moves the work one step forward, but moving the work and owning what happens next aren't necessarily the same thing.
This is where "I did my part" becomes interesting to me. Sometimes it sounds like an accountability problem, but I don't think that's always fair. If the process tells someone their responsibility ends when they send the email, submit the form, or notify another person, they may have done exactly what the organization asked them to do.
The real question is whether the organization clearly defined what happens to ownership at that point.
Ownership doesn't mean one person has to follow every piece of work from beginning to end. In most organizations, that wouldn't make sense. Work has to move between people, roles, and departments. But when responsibility changes, ownership can't simply disappear in the space between them.
Someone needs to know when they have become responsible for moving the work forward, and the person handing it off needs to know when that transfer has actually occurred. Otherwise, both people can reasonably believe the work belongs to someone else.
That's how customers end up calling back for updates. It's how internal requests sit unanswered. It's how leaders find themselves chasing down work they thought was already being handled. And it's how an organization can have clearly defined individual responsibilities while still struggling with accountability for the overall outcome.
When something repeatedly gets stuck, delayed, or forgotten, it's worth looking beyond the person who last touched it. Trace the work back and ask where ownership was supposed to change.
Was that point clear to both people? Did the next person know the work was now theirs? Was there any way to know the transfer actually happened?
Completing your responsibility matters, but so does knowing who is responsible next.
Ownership shouldn't disappear when responsibility changes hands.







