Ownership Requires More Than an Assignment

We have all been in meetings where a decision is made, and everyone agrees something needs to happen next. Someone needs to follow up. Someone needs to communicate with the client. Someone needs to move the work forward.

The meeting ends with what feels like clarity, but no one has actually named who owns the next step. A week later, everyone is surprised to learn it still hasn't happened. I have seen this more times than I can count, and it's taught me something simple—when the owner is "somebody," the work often belongs to nobody.

To me, ownership means knowing what belongs to you. It means understanding what you are responsible for, what you have the authority to move forward on, what you need to communicate, and what you are expected to carry across the finish line. That level of ownership is hard to create without clear leadership, but it also requires personal responsibility from the person receiving it.

I have always believed there is a difference between assigning someone a task and giving them ownership. An assignment may sound like, "I need you to handle this." Ownership comes with a fuller conversation: "This is your project. Here is what I expect from beginning to end. I know you can do it, and if you encounter barriers along the way, let me know how I can help remove them."

That conversation provides clarity, but it also communicates trust. It tells the person they have room to lead the work while reminding them they aren't expected to navigate every obstacle alone. In my experience, people are much more likely to take ownership when they know their leader trusts them and will support them when they genuinely need it.

This can get complicated when something doesn't go as planned. The project may be moving more slowly than expected. Perhaps a stakeholder is frustrated, or a customer has raised a concern. Those situations may require a leader to become more involved, but I have seen how quickly involvement can become interference when the leader reacts before gathering the facts.

A leader may begin communicating with stakeholders without first talking to the person responsible for the work. They may make an unrealistic promise or change an expectation without explaining why. Sometimes they step in and take over because they are trying to solve the problem quickly. Even with good intentions, the result can be more chaos than clarity.

I am not suggesting that leaders stand back and allow a project to fail. Sometimes stepping in is necessary. But before doing that, it matters to talk with the person who owns the work, understand what has happened, and get a fuller picture of what may be getting in the way. That conversation can help a leader determine whether the situation requires intervention, additional support, clearer expectations, or simply a little more time.

Trust plays a significant role in all of this. It is difficult to take ownership when you regularly feel undermined, are left out of conversations about your work, or aren't sure your leader will support you when something goes wrong. Over time, people may become more hesitant to make decisions or take initiative, even when they technically have the authority to do so.

I have heard leaders say, "I stepped in because I didn't trust that it would get done." I understand the concern, especially when the outcome matters and other people are waiting. At the same time, if a leader doesn't trust someone to complete the work they have been assigned, a larger conversation needs to happen.

From my perspective, that becomes a leadership issue. That does not necessarily mean the leader caused the problem, but the leader does own addressing it. The issue may involve unclear expectations, a need for development, inconsistent communication, a performance concern, or work that was assigned to the wrong person. Quietly taking the work back may solve the immediate problem, but it rarely resolves the underlying one.

The person who owns the work also has responsibilities. Ownership includes asking questions when expectations are unclear, seeking the information needed to move forward, communicating concerns early, and raising potential barriers before they become emergencies. It also includes following through and closing the loop so others are not left wondering where things stand.

When someone does not follow through, I prefer to begin with curiosity: "Help me understand what happened." Seeking to understand does not remove accountability. It simply grounds the conversation in facts rather than assumptions, which usually leads to a more honest discussion about what happened and what needs to change.

Accountability also needs to move in more than one direction. Employees need to be able to say, respectfully, "The expectations changed without a conversation," "I did not have the information I needed," "You communicated around me," or "A promise was made that we could not realistically fulfill." Those conversations may be uncomfortable, but healthy accountability cannot stop with the person who has less positional power.

I recently found language for something I have believed for a long time…if accountability only travels down the org chart, it isn't accountability. It's authority. Authority gives you the right to make certain decisions. Leadership determines whether people trust you with that right, and accountability requires you to answer for how you use it.

Healthy workplace cultures require both clear leadership and personal responsibility. People need to understand what they own, have room to own it, and know that they can raise questions or concerns along the way. Leaders need enough visibility to provide support and address problems without unintentionally taking ownership away.

Perhaps the question for all of us is not only, "Who owns this?" It may also be, "What am I doing—or not doing—that makes it easier for them to own it?"