Why Won’t My Employees Take Responsibility?
It is one of the most frustrating questions a leader can ask: Why won’t my employees take responsibility?
You have explained what needs to be done. You have provided the resources. You have answered the questions. You have held meetings, sent emails, written policies, created procedures, conducted training, and probably reminded people more than once that they are adults who should be capable of doing the job they were hired to do.
And yet, somehow, responsibility keeps finding its way back to you.
An employee encounters a problem and brings it to the supervisor without a proposed solution. The supervisor encounters a problem and takes it to the manager. The manager takes it to the director. Before long, something that should have been handled at the lowest reasonable level has traveled halfway up the organizational ladder.
Then somebody says, “Nobody around here takes responsibility anymore.”
Maybe.
But before we blame the employees, there is another question that needs to be asked, and sometimes it is a much harder question for a leader to answer: Have we actually created an environment in which people are expected to take responsibility, or have we trained them to wait for someone else to make the decision?
That is a very different question.
Responsibility does not grow in a vacuum. People need to understand what they are responsible for, what authority they have to act, what success looks like, and what happens when they fail to meet an expectation. Telling somebody to “take responsibility” without providing those things is little more than a slogan.
An employee cannot reasonably be held responsible for an outcome they have no authority to influence. A supervisor cannot be expected to solve problems when every decision they make is second-guessed by someone above them. A manager cannot develop independent people if the organizational culture rewards them for bringing every problem back to the boss.
Responsibility requires room to operate. It also requires clarity.
One of the great failures of organizational leadership is assuming that a job description creates clarity. It doesn’t. A job description tells someone what their position is supposed to do. It does not necessarily tell them what decisions they are expected to make, what outcomes they own, where their authority begins and ends, or what they should do when circumstances don’t fit neatly into the policy manual.
That is where leadership comes in.
Recent Gallup research is interesting in this regard. Creating accountability was the lowest-rated of seven major leadership competencies in its 2026 research. Less than half of leaders rated themselves highly in their ability to create accountability, and managers were even less positive about their leaders’ ability to hold people accountable.
There is another side to this equation that doesn’t get discussed nearly enough.
Sometimes we teach people not to take responsibility.
Think about what happens when an employee walks into your office and says, “What should I do?”
You know the answer. You have dealt with this situation a hundred times before. You can solve it in thirty seconds, so you tell them what to do.
Problem solved.
Except it isn’t really solved.
What you have just taught that employee is that when they encounter a problem, the supervisor has the answer.
The next time something happens, they come back.
“What should I do?”
You answer again.
Pretty soon, you have become the organizational GPS. Nobody moves until you tell them which direction to go.
It usually starts innocently enough. The leader wants to help. The leader wants to prevent mistakes. The leader wants to move quickly. The leader knows the answer, and telling somebody what to do really will take about thirty seconds.
But if you answer the same question thirty times, you haven’t saved time. You have created a system in which everyone needs you.
That isn’t leadership. That’s dependency.
The next time someone brings you a problem that they should reasonably be capable of addressing, resist the temptation to immediately provide the answer. Ask them, “What do you think we should do?”
Then listen.
You may get silence. You may get three reasons why their idea won’t work. You may get a surprisingly good answer. You may discover that the employee has been thinking about the problem more carefully than you realized. You may also discover that they have absolutely no idea what to do because nobody has ever taught them how to think through the problem.
All of those outcomes are useful.
The objective isn’t to prove that your employees should already know everything. The objective is to develop people who can increasingly think, decide, act, and learn without requiring the boss to stand over them.
That is how responsibility develops.
But there is another uncomfortable truth we need to acknowledge. Sometimes employees really are avoiding responsibility.
Not every problem is a leadership problem. Not every poor performer needs another coaching conversation. Not every chronic complainer needs another explanation. Not every failure needs to be rationalized as a communication breakdown.
Some people simply do not want to own the outcome.
That’s where accountability comes in.
Accountability isn’t punishment. It is the organizational understanding that what you do matters, what you fail to do matters, and you are responsible for your part of the mission.
That standard has to apply to everyone.
The employee who consistently fails to follow through cannot be treated the same as the employee who consistently delivers. The supervisor who avoids difficult conversations cannot credibly complain about employees who avoid responsibility. And the executive who constantly overrides subordinate decisions cannot reasonably demand that subordinate leaders demonstrate initiative.
Accountability begins at the top because people watch what leaders actually do far more carefully than they listen to what leaders say.
This is also where organizations can become trapped in what I call the parent-child dynamic. (See my related article here: Moving Beyond the Parent-Child Dynamic In The Workplace )
The leader becomes the parent. The employee becomes the child. The parent reminds, checks, follows up, rescues, corrects, explains, protects, disciplines, and occasionally loses patience.
The employee waits.
“Did you do that?”
“No.”
“Why not?”
“I thought you wanted me to wait.”
“Why didn’t you tell me?”
“I didn’t know.”
“Why didn’t you ask?”
“I didn’t want to bother you.”
And around and around we go.
Eventually the leader is exhausted and asks, “Why can’t I get these people to take responsibility?”
The answer may be sitting right there in the relationship.
Because you have assumed responsibility for them.
That doesn’t mean employees should be abandoned. It means leaders have to learn the difference between supporting someone and carrying someone.
Support helps a person become more capable.
Carrying allows them to remain dependent.
Those are not the same thing.
Responsibility also disappears when leaders consistently walk past small failures because each one seems too insignificant to address.
A missed deadline. A promise that wasn’t kept. A meeting commitment that wasn’t completed. A supervisor who repeatedly avoids a difficult conversation. An employee who continually says, “That’s not my job,” when the team needs help. A person who complains about a problem but refuses to participate in solving it.
None of those things may seem particularly important by themselves.
But culture is built from repeated behavior.
If people learn that commitments are optional, they eventually stop treating commitments seriously. If they learn that someone else will always clean up the mess, they stop seeing the mess as theirs. If they learn that the loudest complaint receives the most attention, they learn to complain louder.
You get more of what you walk past.
That is one of the simplest rules of organizational culture I know.
There is another principle I have found particularly useful in leadership development. People need a common destination, but they also need enough room to determine how they will get there.
The destination is the mission. The responsibility is each person’s contribution to that mission. The authority is the room they have to act. The accountability is what happens when they deliver or fail to deliver.
Put those four things together and something interesting begins to happen.
People start thinking. They start making decisions. They begin solving problems before bringing them upward. They discover that they are capable of more than they thought.
And leaders begin getting some of their time back.
That last part matters.
If the leader is still personally solving every problem, approving every decision, settling every disagreement, and answering every question, the organization has not actually developed greater capacity. It has simply developed a more exhausted leader.
So what do you do tomorrow morning?
Start small.
When someone brings you a problem they reasonably should be able to address, don’t immediately solve it. Ask, “What do you recommend?”
When someone tells you something went wrong, ask, “What happened, what did you learn, and what are you going to do differently?”
When a supervisor tells you about a difficult employee, ask, “What have you done about it?”
When someone says, “We can’t do that,” ask, “Why not?”
When someone tells you there is a problem, ask, “What are our options?”
Then listen to the answers.
You are teaching people what responsibility looks like.
At the same time, make sure your expectations are clear. Define what people own. Give them appropriate authority. Establish reasonable boundaries. Follow up. Coach. Deal with failures when they occur. Recognize good work. And above all, apply the same standards to yourself that you expect from everyone else.
Don’t tell people to take responsibility while constantly taking it away from them.
So, why won’t your employees take responsibility?
Sometimes the answer is that they don’t know what they are responsible for. Sometimes they don’t have the authority to act. Sometimes they haven’t been taught how to think through problems. Sometimes they are afraid of making a mistake. Sometimes they have learned that taking initiative creates more trouble than simply waiting for instructions.
And sometimes, yes, they simply don’t want to take responsibility.
Your job as a leader is to figure out which one you’re dealing with.
The answer isn’t another motivational speech about accountability. It isn’t another poster on the wall. It isn’t another policy. And it certainly isn’t the leader becoming an organizational parent who spends every waking hour reminding adults to do the work they were hired to do.
The answer is to clarify what people are expected to own, give them the authority to act, and teach them to think through problems rather than simply handing them answers. Let people make reasonable decisions and learn from the consequences. When they struggle, coach them rather than immediately taking the problem back. When they fail to meet the standard, hold them accountable. Most importantly, stop rescuing people from every consequence of their choices, because people rarely develop a sense of responsibility when someone else continually steps in to carry it for them.
Leadership is not about doing everything yourself. It is about creating an environment in which other people can do what they are capable of doing, understand why it matters, and accept responsibility for the results.
That is what purposeful adults do. (Check out my book, The Guidant Path: The Self-Guidant, here.)
And that is what purposeful organizations require.
If you have a problem you’d like to discuss in a confidential, no-obligation Zoom visit, you can self-schedule it by clicking on this button:
Author’s Note: The content provided in this article is designed exclusively for educational and informational purposes, reflecting opinions shaped by decades of leadership training and organizational consulting experience. It should never be interpreted as formal professional advice. By reading or engaging with this material, you acknowledge that no professional-client relationship is established and that these insights do not substitute for tailored guidance from a qualified professional familiar with your specific circumstances. Consequently, readers are strongly advised to seek independent counsel from licensed legal, financial, medical, or other appropriate advisors before implementing any strategies or making decisions based on these perspectives. Ultimately, you assume full personal responsibility for any actions you choose to take or omit as a result of reading this material, releasing the author and publisher from any liability for outcomes arising from your reliance on the text.
