11. Own the Failure, Distribute the Credit¶

Correction handles the individual case. This chapter is what the leader owes when the team fails visibly — own upward, correct inward, and do not collapse the two.

The room was waiting for an answer.

The project had failed. Not catastrophically — but visibly enough that the layer above me wanted to know what happened, and they wanted to know now.

The easy move was sitting right there on the table.

I could have walked them through it cleanly. Who missed the commitment. Who ignored the dependency. Who did not escalate when they should have. Most of it would have been technically accurate. Some of it would have been fair.

I did not take that move.

What I said in that room was simpler.

This happened under my responsibility. I own it.

That is not because everyone on the team had performed. Some had not. I knew it before I walked in. But the team worked under my direction, my system, my standard, and my communication. Whatever broke inside that perimeter was also mine to carry.

The harder work started after the room emptied.

Because owning the failure upward did not mean everyone downward was now safe.

Back with the team, I had to do the opposite move. I had to separate blame from responsibility, carefully, and without letting the noise of the external conversation bleed into the internal one. I sat down and mapped the failure honestly.

Some of it was legacy tech debt nobody had paid down. Some of it was unclear product direction — which was on me. Some of it was missing process — also partly on me. Some of it was capacity. The team had been asked to carry too much. And some of it was execution discipline. People had missed commitments without flagging risk early.

Each of those needed a different response.

You cannot fix tech debt by blaming an engineer. You cannot fix unclear direction by blaming a PM. You cannot fix capacity by demanding harder work. But if someone repeatedly missed commitments and did not raise the risk — that conversation still had to happen. On its own terms. Without me hiding behind the "I own it" line I had used in the room above.

So I had it. Directly.

No more vague "the team should fix this." Every problem got an owner, a next step, a risk flag, a dependency map, and a timeline. I told them I would rather hear bad news early than receive a surprise later. Hiding risk became a bigger problem than having risk.

The line I tried to hold between the two rooms was this:

I will not humiliate you upward. I will not lower the standard downward.

Public ownership was not a permission slip for mediocrity. The team should feel protected from unfair external blame. They should also understand that the protection came with a higher expectation, not a lower one. Honesty. Discipline. Follow-through.

That was the trade.

What bad leadership usually does¶

When a project fails and the layer above asks for answers, the default move is distance.

Most leaders reach for the accurate explanation. The team missed the dependency. The engineer did not escalate. The PM dropped the ball. These things may even be true.

But the way they get delivered moves the weight off the leader and onto the people who did the actual work.

The leader stays intact. The team takes the hit.

And then the leader wonders why nobody raises risk early anymore.

When a win is visible, the default move flips. It becomes retention.

Most leaders do not consciously steal credit. They just describe the outcome in a way that keeps themselves at the center. My strategy. My coordination. What I built. The team gets a polite acknowledgment, but the framing keeps the leader as the main character.

This feels natural, because the leader did contribute.

The cost is not dishonesty. The cost is that the win lives inside one person's narrative. The team does not learn what made it repeatable. They learn to wait for that person to do it again.

Both defaults — passing the failure down, keeping the credit up — produce the same long-term result. A team that depends on the leader and does not trust the leader at the same time.

The principle¶

The leader owns the system. The team owns the spotlight.

When the team fails, the leader carries it externally — because the direction, the standards, the communication, and the process all sat under the leader's responsibility.

When the team wins, the leader passes the spotlight downward — because the win is more useful to everyone if it is owned by the people who built it.

Both moves are responsibility, not generosity.

Why it matters¶

If the leader uses the team as a shield, three things happen.

People stop raising risk, because raising risk now means becoming the name in the next room. Communication tightens. Bad news arrives late, when the damage is already structural.

Trust erodes. The team learns the rule: when things go well, the leader is here. When things go badly, the leader is somewhere else.

And the leader's own thinking gets lazy. If the failure is always somebody else's, the leader never has to look at the system that produced it.

If the leader keeps the credit, a different damage shows up. Slower, but real.

The win becomes a one-time event instead of a repeatable capability. The team does not learn the pattern, because the pattern is wrapped around the leader's name. The next time a similar problem appears, everyone waits.

That is dependency, not leadership.

What better leadership looks like¶

Public ownership and internal accountability are not in conflict. They live in different rooms, and they do different work.

Externally, the leader takes the failure cleanly. No qualifiers. No quiet pointing. No "well, the team was supposed to…" tucked into the sentence. The weight stops with the leader.

Internally, the leader does the harder work. Map the failure honestly. Sort the causes. Some will point at the system. Some will point at people. Some will point back at the leader. The leader is not exempt from the mapping.

After the mapping, the accountability conversation happens directly. Not in a meeting where everyone is present and nobody is named. With the specific people, on the specific behaviors, with a clear path forward.

The leader is the one who decides when each conversation happens, and which room it happens in. That is the actual job.

The tool — The External / Internal Script¶

The cleanest practical tool I have for this is two sentences. One for each room.

External / Internal Script

Use these in order. Do not collapse them into one conversation.

External (in front of leadership or stakeholders): "This happened under my responsibility. I own it."
Internal (back with the team after the room clears): "Now that I have taken that responsibility, I need you to be very clear with me: what can you commit to, what is blocked, and where did we miss?"

The first sentence protects the team from unfair external blame. The second sentence makes sure that protection does not become cover.

The two together model the move for the team. They see what public ownership looks like. They see what internal accountability looks like. They see that the same leader does both, and does not blur them.

The script is simple enough to use Monday morning. A leader who has these words ready does not have to improvise in a stressful room — and improvising in a stressful room is where most leaders accidentally throw their team under the bus.

When you sit down for the internal conversation after the external one, the rough mapping is usually some mix of these:

Legacy tech debt nobody paid down.
Unclear direction.
Missing or broken process.
Capacity that did not match the ask.
Execution discipline — commitments missed, risk not flagged.

This is not a framework. It is just the way I actually run the diagnosis after a failure. Some of those will land on the team. Some will land on the leader. The point of the list is to stop the lazy move — collapsing a multi-cause failure into one person's name.

The other side — distributing the credit¶

The other story is shorter, and it is the quieter one.

There was a stretch where community-led engagement on the product genuinely improved. Rewards redemption climbed. The app started showing healthier signals. The improvement was visible enough that it could have been named as a leadership win.

I had been the one connecting the dots. Across growth, CRM, community, product, and tech. Setting direction. Removing blockers. Keeping the teams pointed at the same outcome.

It would have been easy to frame the result as my strategy working.

I did not do that.

I distributed the credit according to the actual work.

Community had activated the users. They got that recognition specifically. CRM had sustained the engagement loop. They got that recognition specifically. Marketing had shaped how the campaign communicated. Specifically. Tech had carried the product and operational pieces. Specifically.

My role had been direction and coordination. That role did not disappear in the telling. It just did not need the spotlight.

I took responsibility for the direction. I let the team own the pride. For me, that is a better leadership trade.

Not because giving credit away is generous. Because the team started to see the win as repeatable.

If I had claimed too much of it, the next time a similar problem showed up, people would have waited for me to be clever in the room again. By giving the credit to the functions that did the work, the team could see the system underneath it. Clear direction. Cross-functional coordination. Consistent activation. Feedback loops.

That pattern can be repeated by people who do not need me to do it for them.

That is the win behind the win.

Simple rules¶

Take the external blame cleanly. No qualifiers. No quiet pointing.
Do the internal accountability conversation separately, with the specific people, on the specific behaviors.
Do not collapse a multi-cause failure into one person's name.
Map the failure honestly. The leader is not exempt from the mapping.
Distribute credit by actual contribution. Name the functions or the people specifically.
If the win lives only in your narrative, the team cannot repeat it.
Public ownership is not a permission slip for mediocrity. Higher protection comes with higher expectation.

Reflection questions¶

In the last failure I had to explain upward, did I leave the room with the weight, or did the team?
After I took external ownership, did I actually run the internal accountability conversation, or did I let it slide?
When I mapped the last failure, which causes pointed back at me — direction, process, communication — and did I name them honestly?
In the last win I described, whose name was at the center of the sentence?
Can the team I lead repeat the last win without me being in the room?
Am I protecting people from unfair blame, or am I protecting them from honest accountability?

Reminder¶

I will not humiliate you upward.

I will not lower the standard downward.

That is the line.

That is leadership responsibility.