He Said the Mistake Was His. It Wasn't.

A regulatory detail had been overlooked, and it very nearly cost them a major client.

In Chapter One, David watches the room react. Senior leaders are furious. The team braces. And the thing that happens next is the thing that always happens next — the book puts it in one line.

People whispered, trying to distance themselves from blame.

Anyone who has been in that room recognises it. The conversation has not started yet and everyone is already positioning.

Then Sehgal steps forward.

“The responsibility for this oversight is mine.”

No excuses. No deflection.

And here is the detail almost every reader glides past.

It wasn't his mistake.

Somebody else overlooked the regulatory detail. Sehgal took responsibility for a failure he did not personally cause, in front of people who knew perfectly well that he had not caused it.

For a long time I read that as character. Decency. The kind of thing you admire and cannot really operationalise.

I now think it was a technique, and a deliberate one.

You Cannot Diagnose a Room That Is Protecting Itself

Watch what Sehgal does immediately afterwards. He runs a transparent review of what went wrong — and he includes junior analysts, and interns.

Now ask whether that review could have happened ten minutes earlier.

It could not. Not honestly.

While blame is still live in a room, everyone in it is solving a different problem than the one you think you are solving. You believe you are running an investigation. They are running a risk assessment about themselves. Every answer you receive has been filtered for what it might cost the person giving it.

You will still get information. It will simply be the wrong information — technically accurate, carefully bounded, and useless for finding the actual cause.

So the sequence matters more than the sentiment.

Taking the blame is what makes the investigation possible. Not because it is noble, but because it is the only move that removes the incentive everyone in the room is currently obeying.

Accountability, done this way, is not a moral gesture. It is a precondition for diagnosis.

And notice that it is the leader who has to spend it, because the leader is the only person in the room who can absorb blame without being destroyed by it. That is, in a fairly literal sense, what the seniority is for.

The Number That Should Go Up

There is a real case that shows this working at scale, and the numbers are the interesting part.

When Mary Barra became CEO of General Motors in January 2014, she walked almost immediately into the ignition switch crisis. A defective part, linked to deaths, that engineers had flagged years earlier. Congress later established that the fix would have cost 57 cents, and that it took the company ten years to recall the cars.

Barra did not deflect to previous leadership, which was available to her and would have been partly true. She testified before Congress in April 2014 and said, with victims' families in the room, that she was deeply sorry. She brought in Kenneth Feinberg — who had administered the September 11th compensation fund — and by June had committed to an uncapped fund covering deaths and serious injuries.

Now the part I find most instructive.

The ignition switch recall itself covered around 2.6 million vehicles.

By the June hearing, four months later, lawmakers were questioning her about a safety crisis that had forced GM to recall 20 million.

Read that as a performance metric and it looks like catastrophic deterioration. The company took responsibility and its problem count went up by a factor of eight.

But nothing got worse in those four months. Problems that had been hidden for a decade surfaced, because the cost of surfacing them had finally dropped below the cost of concealing them.

That is what a working accountability system looks like from the outside. It looks like things getting worse.

A Test You Can Actually Run

Which gives a leader something better than a principle.

After you last took responsibility for something that went wrong — did more problems surface in the following weeks, or fewer?

If fewer, nobody believed you.

That is an uncomfortable measure, because most of us would instinctively report a quiet period afterwards as evidence that the matter was handled. It is usually evidence of the opposite.

What This Is Not

I want to be careful, because this idea is easy to counterfeit and I have seen the counterfeit more often than the real thing.

“I take full responsibility” has become a phrase that ends conversations. Said in a town hall, absorbed as applause, and followed by nothing. That is not accountability. It is a rhetorical device that purchases the appearance of ownership at no cost, which — by definition — means it signals nothing.

The distinguishing test is simple: what investigation followed?

Sehgal took the blame and then opened the review to interns.

Barra took the blame and then commissioned a review that interviewed 230 employees and went through 41 million documents, dismissed fifteen people, and accepted a record federal fine.

In both cases the sentence was the beginning of the work, not a substitute for it.

Absorbing blame publicly is also not the same as absorbing consequences privately. Sehgal did not conceal who made the error, and he did not pretend the error had not happened. He removed the fear from the room so the facts could enter it, and then he went and got the facts.

Why They Worked Late

The client gave them another chance. The team stayed late to fix it.

The book is precise about why, and it is the last line I would keep if I had to cut everything else:

Not from fear. But from respect.

Both of those get you late nights in the short run. Only one of them survives the project.

And only one of them means that the next time somebody notices a regulatory detail going wrong, they say so on the day they notice it — rather than four months later, when it has become somebody else's turn to stand up and say the responsibility is theirs.