Eighteen months after Apple’s board pushed him out, a student at MIT asked Steve Jobs how he felt about it. He didn’t reach for the comeback version. He said the true one first, then kept moving.
In the fall of 1992, Steve Jobs stood in front of a room at MIT Sloan and modeled resilience in leadership by doing something almost nobody does in public. He admitted he lost.
Eighteen months earlier, Apple’s board had pushed him out of the company he’d co-founded. He wasn’t building Apple anymore. He was running NeXT, smaller, scrappier, and mostly unknown to the room he was speaking to. When a student asked him directly how he felt about what had happened at Apple, Jobs didn’t reach for the version of the story that makes the speaker look wise in hindsight.
He said the plain version.
“I think everybody lost. I think I lost. And I wanted to spend my life there. I think Apple lost. I think customers lost.”
No qualifier. No “but it was the best thing that ever happened to me.” Just: it was bad, and I lost.
Then he said the sentence that’s stayed with me since I first read the transcript:
“And having said all that, so what? You go on. It’s not as bad as a lot of things. It’s not as bad as losing your arm. So people go on. And companies go on.”
That’s it. That’s the whole answer. No pivot to a lesson. No inspirational reframe. Just an accurate account of what happened, followed immediately by forward motion. This is what resilience in leadership actually sounds like when nobody is performing it for an audience.
Resilience in Leadership: Why This Version Beats the Polished Story
Most of the Steve Jobs material in circulation comes from after the comeback was complete. after the iPhone, after Pixar, after the world had already decided how the story ends. That version is comfortable. It lets you nod along without sitting in the part where things were genuinely bad and nobody knew yet whether they’d get better.
This talk doesn’t give you that comfort. It was delivered from inside the dip. NeXT hadn’t succeeded yet. Jobs didn’t know, standing in that room, that any of it would work out. He was just telling the truth about where he was, in real time, with no guarantee of a third act.
That’s what makes it useful for leadership development, rather than merely inspiring in a way that evaporates by lunch. A story told after the win is entertainment. A story told from inside the loss, before anyone knows how it ends, is instruction.
What This Means for Your Own Team
Resilience gets talked about like it’s a personality trait, some people have it, some don’t. It isn’t. It’s a practiced response to loss, and the practice starts with the step most leaders skip entirely: naming the loss accurately, out loud, without spin.
Watch what leaders actually do after a real setback, a client lost, a reorg that erases their role, a product that fails in the market, a team that gets cut. The instinct is almost always to reframe immediately. “It’s actually an opportunity.” “Everything happens for a reason.” That instinct isn’t wrong exactly. It’s premature. It skips the step where the loss gets to be a loss.
Jobs’ version does something different. He says the true thing first, lost, and only then says the thing that lets him keep moving: so what, you go on. The order matters more than it looks like it should. Skipping straight to the silver lining is a way of not actually processing what happened, which means it tends to come back later, usually at a worse time and in a worse form, as resentment, as burnout, as a team that quietly stops trusting the leader’s account of reality.
Building Resilience in Leadership: What This Means for Your Preparation
If you lead people through disruption, and if you’re reading this, you probably do, the model here isn’t “project unshakeable confidence at all times.” It’s something more specific and more useful: tell the truth about what was lost, briefly and without performance, and then move.
Teams don’t lose trust in leaders who admit a real loss. They lose trust in leaders who pretend nothing happened, because everyone in the room already knows something happened. The pretending is what erodes credibility, not the admission.
This matters more, not less, in a moment when so much organizational language around AI disruption is either false confidence (“we’ve got this handled”) or false alarm (“everything is about to change and nobody’s ready”). The useful posture sits in between: name what’s actually been lost or is being lost, a role, a way of working, a certainty, and then say clearly what happens next. That combination, said plainly, does more for a team’s actual resilience in leadership than any amount of forced optimism.
Jobs didn’t know in 1992 that NeXT’s technology would eventually save the company that had just fired him. He wasn’t building toward that ending. He was just telling a room of students the truth about a bad year, and then getting back to work. That’s the version of resilience in leadership worth teaching, not the one with the ending already known, but the one practiced without any guarantee of it.
Those prepared need not fear the forces at work. Not because they don’t lose. Because they know how to lose and keep going.
Take the Kryptonite Scorecard at realmikeevans.com/scorecard to see where your organization stands, including the resilience and accountability gaps that can hold you or your team back.
Distinct or Extinct: Future-Proofing People and Organizations in the Age of AI is available now on Amazon.