Why People Fail at Leadership

The owner had done it again.

He moved somebody into a bigger role, expected results inside a quarter, and put none of the support behind it that would have made those results possible. When the results did not come, he handed the guy an ultimatum in a room with other people in it: “fix your subordinate, or I will fix both of you.”

The guy quit instead.

What the owner saw was one person walking out the door, and he was genuinely blindsided by it. What I saw, sitting a little outside of it, was the fourth or fifth run of the same pattern, and a building full of people who had watched every one of them unfold.

Nobody filed a complaint. Nobody asked for a meeting. What they did instead is the part I keep coming back to: they stopped raising their hand.

Nobody announced it or made a big deal out of it. But the next time an opportunity came up, the people who would have stepped forward a year earlier let it pass by them.

That is what a loss of confidence in leadership looks like from the inside. You almost never get confrontation. You get a room full of capable people actively deciding that stepping up or speaking out is not worth the cost.

I have been leading people for close to thirty years and I have been on both sides of this and the switch flips a lot earlier than anyone thinks.

What Causes a Loss of Confidence in Leadership?

A team loses confidence in leadership when the gap between what leadership says and what leadership does becomes predictable. It is rarely one bad decision. Instead, the loss builds through a series of small, unremarkable moments where something was said out loud and then nothing happened, until the team can forecast the outcome before you finish your sentence.

Most leaders look for this in the wrong place. They brace for the hard calls: the layoff, the price increase, the shift change, the project they had to kill. Those feel enormous from the front of the room, so that is where they assume the damage lives.

In my experience the hard calls are survivable, and often the opposite of damaging, as long as they are delivered directly and the reasoning is real. People can work for someone who tells them something they do not want to hear. What they cannot work for is someone whose words have stopped meaning anything.

The damage comes from the small stuff. “I’ll look into that.” “Let me find out and get back to you.” “We’ll get that on the schedule.” Each one is a tiny promise, made in good faith, in a hallway, and forgotten by lunch. You are not keeping a good record of them. But your team is, and their memory for it is much better than yours, because they are the ones waiting on the answer.

I got a clean look at this from the other side of the table with a vendor a while back. They committed to something, then did not do it, then changed it at the last minute… multiple times. On its own, any one of those promises is a bad week at a busy company. Stacked up, it cost them the relationship. The way I put it at the time was that their confidence had been eroded to a point where that ship had sailed for me, and I am not especially proud of how short my fuse was about it. That is the part worth understanding. By the time I said it out loud, I had already been done for a while but they had no idea.

Your team is doing the same math, and they have far more riding on it than I did in my situation.

The Habits That Erode Trust

Four patterns account for most of what I see. They look small in isolation, which is exactly why they run for years.

Commitments with no home. Somebody brings you an idea or a problem, you tell them you will look into it, and while it may be top of mind or even written on a piece of paper, it rarely survives.

Almost none of this is careless, and I want to be careful how it gets read. The information arrives while your head is somewhere else. You are mid-quarter, mid-crisis, walking between two other things, and somebody catches you with something that deserves real thought. You mean it when you say you will look into it. Then the day does what days do, and by the afternoon it is out of sight and out of mind. Overload is the mechanism, not indifference.

The part that took me years to understand is that there are two versions of this, and from the other side of the conversation they look identical.

In the first, the thing genuinely died. In the second it did not. You are still working on it. It needed approval from somebody else, or research, or a proposal you have already submitted and are waiting on. You are doing exactly what you said you would do, and the person who brought it to you has no idea, because you have not said a word since.

That second one is what I got wrong for most of my early leadership days. My model was simple. You told me, I am working on it, that is the end of the transaction. Then inevitably somebody would ask whatever happened to that, and I would have a perfectly good answer ready. Still working on it. Waiting on feedback. Learning more about two other pieces before I can decide. All of it true, and none of it ever said out loud.

That is where “no update is still an update” came from, and I have been saying it ever since. It shows up in the change management toolkit for the same reason it shows up here: silence breeds speculation, and the absence of communication is itself a message. When you tell somebody you are still working on something, the content of the update is not really the point. What you are telling them is that the thing they brought you still exists.

Work takes far longer than the person waiting on it imagines, and the feedback loop is what closes that gap. Three sentences cover almost every case:

– I am still working on it, and here is what it is waiting on.
– This is a no for right now. It stays on the board and we revisit it next quarter.
– I am not going to get to this.

That third one costs you nothing, which surprises people. What costs you is the silence, and it costs you a small piece of credibility every time, and the invoice never arrives anywhere you can see it.

Treating the title as the authority. People step into a bigger role believing the respect arrives with the nameplate. Some authority does. Respect gets earned over time, through what you do for the team and how you carry their mistakes, and it can be spent faster than it accumulates. The leaders who struggle most with this are usually the ones who were promoted for being excellent at the work and were never told the job changed underneath them.

Indecision. This is where a leader’s own shaky confidence shows up on the floor, and it is the connection most people miss. A leader who is unsure delays. The delay reads to the team as either a hidden agenda or an inability to choose, and both are corrosive. Confidence is contagious in either direction. A team watching their leader hedge for three weeks on a call that should have taken three days learns something durable about what to expect next time.

The persona. Trying to be a version of yourself you think the role requires. It is exhausting to maintain, so it slips, usually under pressure, and the slip is what people remember. Nobody expects you to have it all figured out. They expect you to be the same person on a bad Tuesday that you were in the interview.

None of these four are character flaws. Every one of them starts as a reasonable response to a real constraint, which is why they are so hard to catch in yourself.

The Signals You Get Before Anyone Complains

You will almost never get an actual complaint on any of this stuff. By the time someone tells you directly that they have lost confidence in you, they have usually already made other plans. What you get instead are behavioral signals, and they are readable if you know what you are looking at.

People stop raising their hand. The clearest one by a wide margin. An opening comes up and the people who would have wanted it a year ago are suddenly uninterested. They watched what happened to the last person who stepped forward without support and they drew the obvious conclusion.

The questions dry up. Think about the last meeting you sat in where one or two people did all the talking. Everybody else nodded along, nobody offered much, nobody wanted to make waves. From the front of the room that reads as agreement, or as a team with nothing to add. It is worth asking what is going on underneath it.

When I roll out a change with a team, I tell them plainly that silence is acceptance. If nobody pushes back, the decision stands. That rule is a good forcing function and it has one failure mode worth naming: it only works while people still believe that speaking up changes the outcome. Once they stop believing that, silence means something much worse, and the two look identical from the front of the room.

Decisions start routing around you. People stop asking and start deciding on their own, or they stop deciding at all and let things sit. Either way you are out of the loop on things you used to be in the middle of.

You hear about problems later than you used to. This one is qualitative and you will almost always catch it after the fact, which is exactly why it is worth naming. You notice the aftereffect first. Then you find yourself asking: When did that happen? When did that decision get made? How long has this been going on? Those questions are the signal. By the time you are asking them, information has been routing around you for a while.

If your weekly leadership meeting has turned into everyone taking turns justifying their numbers, that is a related problem with its own fix, and I wrote about why your leadership meeting reviews the same numbers every week and nothing changes separately.

How to Rebuild Confidence Once It Is Gone

The instinct here is almost always wrong, and this is the part worth reading twice.

When a leader finally notices the room has gone cold, the reach is usually for something big. An all-hands. A heartfelt speech. A new initiative with a name and a kickoff. I understand the impulse, because the debt feels large and a large gesture feels proportionate to it.

It makes things worse when not done right. A big promise, delivered to a team already holding a record of promises you did not keep, is just one more example. They have heard the speech before. What they have not seen is the actual follow-through, and a speech itself doesn’t provide that.

Here is the sequence that actually works.

Own the specific thing, not the general thing. A vague apology reads as theater. Name the pattern out loud. In the situation I opened with, the honest version was not “we could communicate better.” It was closer to this: we moved people into roles, we did not give them the support or the runway to succeed, we expected results anyway, and we have now done that more than once. Specificity is what makes an apology believable, because it proves you actually see it.

Say what changes, in operational terms. The best framing I have heard on this came from a leader in that same conversation, who said the owner needed to stand up and say we screwed this up, I am committed to not screwing this up anymore, and here is how. That third clause is the whole thing. The first two are sentiment. The third is a plan, and it is the only part the team can verify.

Make smaller promises than you are capable of keeping. This is counterintuitive and it is the fastest lever you have. You are trying to reestablish that your words predict reality, and the size of the promise is irrelevant to that. Commit to three small things you are certain you can deliver in the next two weeks, then deliver them on the day you said. Do that six times and you will have rebuilt more than any offsite ever has.

Put the commitments somewhere visible. Owner, date, status, where everyone can see it. This is not bureaucracy, it is the mechanism. My version of the accountability conversation is deliberately boring: you committed to this date, it is still not done, what do we need to do to get it done? That question only exists when the commitment was written down in the first place, and it works precisely because there is nowhere to hide, including for you.

Expect the next hard decision to be the real test. Everything above buys you a hearing, not a verdict. The team is waiting to see what happens the first time it gets expensive. If the new way holds when the quarter goes sideways, you have something real. If the first bad month produces an all-bets-are-off reversal, you have confirmed exactly what they suspected, and the second recovery is much harder than the first.

The owner from the opening did all of this. He owned the pattern in front of his team, said what was going to change, and then spent the following year proving it in small increments. The culture turned around. That is the scorecard, and it took considerably longer than the conversation that started it.

Rebuilding runs slower than losing, and there is nothing unfair about that. It is just how credit works. You spent it over months without noticing. You will earn it back the same way, and you will notice every bit of it.

What I would not do is treat it as finished. Brené Brown has this marble jar theory that I keep coming back to: every action either puts a marble in the jar or takes one out. There is no third option where the jar just sits there. That team is still building on what they started, which is the correct end state, because there isn’t a stopping point. You are either adding or subtracting. The question is never whether you have repaired it. The question is which direction today went.

Where Confidence Sits in the Sequence

Everything I teach runs on Clarity, then Consistency, then Accountability, in that order. Confidence is not a separate initiative you run alongside them. It is the output of the middle one.

Clarity means people know what is expected. Consistency means what you said last month still holds this month. Confidence is what a team feels once consistency has been true long enough that they stop checking. Accountability only becomes possible after that, because you cannot hold someone to a standard they have watched you move.

If you are building this from the ground up rather than repairing it, I covered the construction version in how to build trust as a leader, including why empathy without clarity tends to backfire. The conversations most likely to move the needle here are the ones people avoid, which I broke down in 3 conversations leaders avoid but shouldn’t.

Final Thoughts

The uncomfortable part of all this is that the receipts ledger exists whether or not you are keeping it. Your team has been tracking the distance between what you say and what happens since the day you got the job, and they are never going to show you the book.

So do not wait for the complaint. It is not coming.

Go back through the last four weeks instead. Find the things you said you would do in a hallway, in a meeting, on a call, and count how many actually happened. The ones that quietly died are not oversights. They are the whole mechanism, and they are the only part of this you can start fixing on Monday.

That’s it for today.

See you all again next week!

Dave