High standards mean nothing when leaders fail to provide the coaching, clarity, and support people need to meet them.
Accountability in leadership demands more than setting
expectations and enforcing consequences. When managers
weaponize performance metrics without providing meaningful
coaching, clear direction, and adequate resources,
accountability becomes blame disguised as leadership.
Leaders who demand results while neglecting employee
development contribute to the very performance
failures they condemn.
Set uncompromising standards, develop the capabilities
needed to meet them, remove barriers, and hold both
employees and leaders accountable.
The Executive Brief
60-Second Read
The Bottom Line
The Uncomfortable Truth
The Leadership Imperative
One kind of manager is particularly damaging in the workplace. One who can tell you exactly where an employee is failing but struggles to explain what they’ve done to help that employee succeed.
They have the dashboards. They have the performance reports. They have the documentation. And when results fall short, they’re ready with a performance improvement plan.
What they don’t always have is evidence of meaningful coaching, skill development, or any serious attempt to understand why performance is falling short.
That’s not accountability. That’s blame dressed up in a leadership title.
Somewhere along the way, too many organizations confused holding people accountable with holding people responsible for everything that goes wrong. Managers learned to enforce standards without accepting responsibility for creating the conditions necessary to meet them.
And the consequences can be devastating.
Next comes a breakdown in trust. Team members quietly stop asking for support, so real issues get buried. Once fear overtakes drive, the entire culture shifts. Suddenly, the goal isn’t hitting high benchmarks anymore—it’s avoiding the next painful conversation.
Let’s be honest for a second. Just telling an underperforming team member to “do better” doesn’t actually fix anything. All you’re really doing is pointing out a problem everyone already knows is there.
Don’t misunderstand me. I believe in high standards. I believe in measurable expectations, individual ownership, and real consequences when performance doesn’t improve.
But I also believe leadership comes with an obligation that too many managers conveniently overlook.
You don’t get to demand accountability from your people while dodging accountability for how you lead them.
Standards Are Not a Leadership Strategy
Setting expectations is important. Measuring performance is necessary. Holding people responsible for their commitments is essential.
But none of those things, by themselves, constitute leadership.
I’ve encountered managers who could recite every performance metric, identify every underperforming employee, and explain every disciplinary step in their organization’s performance management process.
Ask them what specific skills their struggling employees need to develop, and the conversation becomes considerably less confident.
Ask what coaching they’ve provided, what barriers they’ve removed, or what they’ve changed about their approach, and sometimes the answers become painfully vague.
That’s a problem.
A performance dashboard can tell you an employee is missing their sales target. It cannot tell you whether that employee struggles with discovery, objection handling, product knowledge, or confidence.
It cannot tell you whether the employee understands what successful performance looks like or whether their manager has ever demonstrated it.
And it certainly cannot replace the difficult, sometimes uncomfortable work of developing another human being.
A dashboard can expose poor performance. It cannot replace the leadership required to improve it.
Just because you can see the dashboard doesn’t mean you know what’s actually going on. Many leaders will spot a bad metric, jump straight to a conclusion, and start handing out consequences without ever digging into why the numbers dropped in the first place.
Far too often, a struggling team member gets labeled as the problem. The data is weaponized as proof, and a PIP is thrown at them as the cure-all. Meanwhile, the real operational bottleneck goes completely unchecked.
It’s a pretty convenient setup if you want the perks of being a manager without having to actually take responsibility when things go sideways.
When Accountability Becomes a Weapon
Accountability should create clarity, ownership, and improvement.
But in the wrong hands, it becomes something entirely different.
It becomes a weapon.
Performance metrics stop being tools for understanding and improving results. Instead, they’re used to expose shortcomings, justify criticism, and document failure.
Before you know it, coaching goes completely out the window, replaced by pure interrogation. One-on-ones just turn into painful meetings where people try to explain away why the dashboard is red. Pretty soon, your team realizes that being honest about where they’re struggling just puts a target on their back.
And slowly, almost imperceptibly, the culture begins to change.
People stop raising their hands when they’re struggling. They become reluctant to acknowledge mistakes. They focus on protecting themselves rather than solving problems.
The damage isn’t always immediately visible in a performance report.
It shows up in the employee who stops offering ideas because they’ve learned that taking risks isn’t worth the criticism.
It shows up in the team member who quietly struggles rather than asking for help.
It shows up in the manager who is surprised by an employee’s resignation, despite months of warning signs.
And it shows up in organizations that confuse compliance with commitment.
When people fear being caught failing more than they’re motivated to succeed, you’ve created a culture of self-preservation, not accountability.
This doesn’t mean employees should be protected from uncomfortable feedback. Quite the opposite.
People deserve honest conversations about their performance. They deserve to know when they’re falling short and what needs to change.
But there’s an enormous difference between a leader who says, “You’re not meeting expectations, and here’s how we’re going to address it,” and one who says, “You’re not meeting expectations. Fix it.”
One accepts responsibility for helping improve the outcome.
The other simply assigns blame.
I Know What It’s Like to Be Expected to Succeed Without Support
My perspective on accountability didn’t come from a leadership textbook.
It came from experience.
Earlier in my career, I worked under managers who expected results without providing much direction, coaching, or development. I learned what it felt like to be held responsible for outcomes without the guidance needed to achieve them.
Later, when I was promoted into management, I faced a different version of the same problem.
I had responsibility for people, performance, and business outcomes, but little formal preparation for what effective leadership actually required.
I was expected to coach, motivate, manage performance, navigate difficult conversations, and develop employees.
The title changed. The expectations increased. The support didn’t necessarily follow.
I learned many of those lessons through experience, mistakes, observation, and a determination not to repeat some of the leadership behaviors I’d experienced myself.
That experience shaped how I think about accountability today.
Because the problem isn’t limited to frontline employees.
Organizations frequently fail managers in the same ways managers fail employees.
They promote strong individual contributors into leadership positions, hand them a team and performance targets, and assume the skills that made them successful individually will translate into developing other people.
Then, when those managers struggle, the organization questions their leadership ability without examining how well it prepared them to lead.
It’s the same destructive cycle, just one level higher.
We demand performance. We withhold development. We express disappointment when expectations aren’t met.
And then we call it accountability.
I’ve spent years working to break that cycle in my own leadership approach. Not because I’ve always gotten it right, but because I’ve experienced what happens when leaders don’t.
We cannot keep demanding outcomes while neglecting the investment required to achieve them.
Support Is Not Optional. It’s Part of the Job.
If you’re responsible for someone’s performance, you’re also responsible for giving that person a reasonable opportunity to succeed.
That doesn’t mean doing their job for them.
It doesn’t mean accepting excuses, tolerating repeated underperformance, or lowering expectations until everyone can meet them.
It means recognizing that performance depends on more than individual effort.
Employees need clarity. They need capability. They need feedback. And they need leaders willing to remove obstacles rather than simply criticize the people encountering them.
I believe that responsibility comes down to four essential leadership practices.
1. Make Expectations Impossible to Misunderstand
You cannot fairly hold an employee accountable for a standard they don’t understand.
Yet managers routinely assume that because they communicated an expectation, the employee understood it.
Those are not the same thing.
Telling an employee to improve productivity, demonstrate more urgency, or communicate more effectively may sound like direction. But without specifics, those statements leave enormous room for interpretation.
What does success look like? How is it measured? What behaviors produce the desired outcome? What should the employee prioritize when competing demands arise?
Strong managers refuse to leave this stuff up in the air. They set the standard in plain language, model the actual behavior themselves, and check for true alignment before sending anyone back to do their job.
Clarity isn’t a courtesy. It’s a leadership responsibility.]
2. Develop the Skills Required to Meet the Standard
One of the most frustrating leadership behaviors I’ve encountered is repeatedly telling someone to improve without teaching them how.
An employee struggles with objection handling, so the manager tells them to book more meetings.
A supervisor is actively dodging hard conversations with their reps. Instead of actually coaching them on how to deliver critical feedback, the boss just tells them to go out there and hold the team accountable.
A team misses its productivity target, so leadership demands greater urgency.
None of those instructions address the capability gap.
If someone doesn’t know how to perform a skill, repeating the desired outcome more forcefully won’t magically create competence.
Development requires observation, diagnosis, demonstration, practice, and feedback.
In sales development, for example, I’ve seen employees perform well when a prospect is engaged and receptive but struggle when the conversation gets difficult.
Simply demanding more meetings won’t fix that.
The leader needs to understand whether the breakdown occurs during discovery, objection handling, value articulation, or the transition to securing a commitment.
Then they need to coach the specific behavior.
That’s the difference between managing a number and developing performance.
You cannot coach an outcome. You coach the behaviors and skills that produce it.
3. Make Coaching an Investment, Not a Documentation Exercise
Coaching has become one of the most overused and misunderstood words in management.
Too often, organizations measure whether coaching happened rather than whether it helped.
A manager completes the required number of sessions, enters notes into the system, and checks the box.
But what changed?
Did the employee gain a new skill? Did they understand what they needed to do differently? Was there an opportunity to practice? Did the manager follow up to determine whether the behavior improved?
If the answer is no, the coaching may have accomplished little beyond creating a record.
Meaningful coaching should clearly connect an observed behavior, the feedback provided, the action taken, and the resulting improvement.
It should be specific enough that an employee leaves knowing exactly what to practice and how success will be evaluated.
And it should be consistent.
Employees shouldn’t receive meaningful attention only when their performance becomes a problem.
If the first time an employee receives serious coaching is when their job is at risk, leadership has already missed opportunities to intervene.
4. Remove Barriers Instead of Blaming People for Encountering Them
Not every performance problem is a skill problem.
Sometimes employees struggle because the systems, processes, tools, or resources around them are inadequate.
Maybe the data is poor. Maybe priorities change constantly. Maybe the workload is unrealistic. Maybe different leaders are giving conflicting instructions.
Or maybe the employee is being measured against a target that no longer reflects the conditions under which they’re working.
These realities don’t eliminate individual accountability.
But they absolutely demand leadership attention.
A manager who knows an employee faces a significant obstacle and does nothing to address it cannot reasonably pretend the resulting performance is entirely the employee’s responsibility.
Leaders must distinguish between what employees can control and what requires organizational intervention.
Sometimes the most consequential thing a manager can do isn’t deliver another performance warning.
It’s to fix the broken process that’s making success unnecessarily difficult.
Support Does Not Mean Lowering the Bar
Some people want to treat empathy and accountability as opposing forces, and that is how servant leadership goes off the rails.
They’re not.
Leaders can care deeply about people while maintaining demanding performance expectations.
In fact, I would argue that doing both is essential.
Employees deserve the opportunity to succeed. They also have a responsibility to act on the opportunities they’re given.
A manager can provide clear expectations, targeted coaching, appropriate resources, and consistent feedback. An employee can still choose not to apply the guidance, resist development, or fail to demonstrate the effort required.
At that point, accountability must have consequences.
Avoiding difficult decisions isn’t compassion.
Allowing repeated underperformance to continue indefinitely can create additional pressure on teammates who are meeting expectations. It can damage morale, undermine trust, and weaken the standards that make teams successful.
Strong leaders recognize that supporting one employee cannot mean abandoning their responsibility to everyone else.
The distinction is whether the leader has genuinely tried to understand and address the performance gap before escalating consequences.
Support is not a promise that everyone will succeed. It’s a commitment to give people a fair opportunity to succeed.
And when someone continues to fall short despite meaningful support, leaders must be willing to make difficult decisions with fairness, clarity, and respect.
Compassion without accountability can create complacency.
Accountability without compassion can create fear.
Effective leadership requires the courage to practice both.
Before You Hold Someone Accountable, Hold Up a Mirror
When performance falls short, many managers’ first instinct is to look outward.
What did the employee fail to do? Why aren’t they trying harder? Why aren’t they taking ownership?
Those questions may be legitimate.
But they’re incomplete.
Before escalating a performance issue, I believe every leader should ask themselves some uncomfortable questions.
Did I make the expectation clear?
Not just communicate it, but ensure the employee understood what success required.
Did I identify the actual performance gap?
Am I addressing the underlying skill, behavior, or obstacle, or am I simply reacting to a disappointing result?
Did I provide meaningful coaching?
Think about whether you really gave them what they needed to succeed. Did you actually show them how it’s done, give them a chance to practice it, and offer concrete notes on what to tweak before sending them back to the floor?
Did I remove the barriers within my control?
Have I addressed the tools, processes, resources, or competing priorities that may be contributing to the problem?
Did I follow through?
Ask yourself if you actually saw this through. Did you look at the data to check their progress? Did you give credit where it was due, change up your feedback if they were struggling, and make sure the expectations didn’t slip?
And did the employee take ownership?
Did they demonstrate effort, apply feedback, practice the necessary skills, and make a reasonable attempt to improve?
That final question matters just as much as the others.
Accountability must run in both directions.
If the leader has fulfilled their responsibilities and the employee still refuses to engage, the conversation changes.
But if the leader cannot confidently answer the first five questions, the performance problem may not be where they think it is.
Before you hold someone accountable for failing, make sure you’ve held yourself accountable for leading.
Build an Accountability Culture That Actually Improves Performance
The strongest accountability cultures aren’t built around fear, constant scrutiny, or the threat of disciplinary action.
They’re built around a shared understanding of what success requires and a mutual commitment to achieving it.
Employees know what’s expected. Managers understand their responsibility to develop capability. Performance problems are addressed early. Feedback is specific. Progress is visible. Consequences are consistent and fair.
And perhaps most importantly, nobody gets to hide behind their job title.
An employee cannot continually blame the manager for performance they refuse to improve.
A manager cannot continually blame employees for problems they refuse to investigate or address.
And senior leaders cannot demand exceptional management while neglecting the development of the people they’ve entrusted to lead.
That is what genuine accountability looks like.
It’s not soft. It’s not permissive. And it certainly isn’t easy.
It requires leaders to have uncomfortable conversations, acknowledge their own shortcomings, challenge broken processes, and sometimes admit that their approach isn’t working.
But that’s the responsibility that comes with leadership.
You don’t earn the right to demand high standards simply because you have a title.
A promotion might give you the authority to set KPIs, but it doesn’t automatically give you the right to demand excellence. That is something you still have to earn from your people every day.
Accountability isn’t what you do to people when they fail. It’s what you build with them so they have a fair opportunity to succeed.
And when you’ve done that work, you can hold the line on performance without sacrificing your integrity or your commitment to people.
Because accountability without support isn’t leadership.
It’s just blame.