Athlete processing setback and turning failure into growth - Apolo Ohno blog

How to Deal With Failure: What It Feels Like From the Inside

The first time I failed at something that truly mattered to me, I was fifteen years old and I didn't make the Olympic team. Not even close. I was too young, too raw, too far behind the guys who'd been in the system for years. But I'd convinced myself it was possible, which meant the gap between my expectation and reality was enormous.

I remember the drive home after. My dad didn't say much. I sat in the passenger seat and stared out the window and replayed every race in my head, looking for the moment where I could've done something different, where I could've been faster or smarter or just more.

The truth is I didn't have to look hard. I had coasted through the whole summer, skipping work I knew mattered, and I showed up to those trials overweight and underprepared. I hadn't given everything I had, not even close, and the result put that on a scoreboard I couldn't argue with.

The weeks after were some of the hardest of my life up to that point. Not because of the training - the training was fine, the training was a relief. The hard part was sitting with the knowledge that nobody had beaten me. I had beaten myself, months before the races ever started, and wanting something badly counts for nothing if the work isn't behind it.

If you're searching for how to deal with failure, I'm guessing you're somewhere in those weeks right now. This post is what I know about them - from the inside.

What does failure actually feel like from the inside?

Nobody tells you failure has a physical address. It lives in your chest and your stomach. It wakes up before you do. For days after those trials I'd have a few normal minutes in the morning before the memory landed, and then the whole weight came back.

That part is normal. I want to say that clearly because high achievers always assume the pain itself is the problem, something to be optimized away. It isn't. The pain is proportional to how much the thing mattered, and you wouldn't trade away the mattering.

What you do with the weeks after - that's the variable. The pain is the entry fee. The processing is the choice.

What happens between failure and fuel?

I didn't have language for it at the time, but looking back I can see what happened in those weeks was a process. My brain was doing something with the failure - not just storing it, but breaking it down. Extracting what's useful, discarding the rest.

The self-pity burned off first. That went pretty quick because I'm not built to sit in it long. Then the anger at myself mellowed into something more like curiosity - what went wrong?

Not emotionally, not "I wasn't good enough," but technically. Where were the gaps? What was trainable and what wasn't? What would I need to be different about by the time the next qualification cycle came around?

That shift - from emotional reaction to analytical extraction - is what separated failure from fuel for me. It didn't happen because someone taught me a framework or gave me a pep talk. It happened because I sat with the discomfort long enough for my brain to start working on it instead of reacting to it.

Most people skip this phase. The instinct is to either wallow in it or sprint away from it as fast as possible. Neither one works.

It takes time, it takes honesty, and it takes a willingness to look at what happened without the protective filter of your ego telling you it wasn't your fault.

Why is failure better data than success?

Once I got past the emotional noise, the failure started giving me information I couldn't have gotten any other way. Not encouragement, not motivation - actual data.

I learned my endurance was fine but my starts were slow. That I was skating technically sound but not tactically smart. That I relied too much on raw physical ability and not enough on race strategy and reading other skaters' patterns. That I was training like an individual athlete when short track is fundamentally a team and positioning sport.

None of that would've been visible to me if I'd made the team. Success hides your weaknesses because it doesn't force you to examine them. Failure puts them on a table in front of you and says look at this, all of it, right now.

If you're willing to look, it gives you a roadmap winning never could.

There's real research behind this, and it surprised even the researchers. A team at Northwestern studied scientists who applied for major research grants early in their careers and compared the ones who just barely missed the funding line against the ones who just barely made it. A decade later, the near-miss group was producing a higher rate of hit papers than the narrow winners - 16.1% of their papers landed in the top 5% of citations, versus 13.3% for the group that got the grant. Two groups that were statistically identical on the day of the decision, and the one that took the early punch came out ahead. The setback didn't just fail to break them. It appears to have sharpened them.

That's not a reason to seek out failure. It's a reason to stop treating it as a verdict. Handled right, it's an advantage the winners don't get access to.

The version of me that showed up for the next qualifying cycle was a fundamentally different skater. Not because I trained more hours - I trained smarter hours.

Because I'd taken the failure apart, piece by piece, and rebuilt my approach based on what it taught me.

Why do smart people bounce back badly?

I work with a lot of founders and executives now going through their own version of this, and most of them are handling it the same way. Not because they're weak or undisciplined but because the business world has the same instinct the sports world does - move fast, don't dwell, pivot immediately, action over reflection.

A product launch fails and the team is in a brainstorm the next morning figuring out the next move before they've understood why the first one didn't work. A quarter misses and the response is immediately about next quarter's plan without anyone sitting with the data long enough to learn from it.

Speed isn't the problem. Speed without processing is the problem.

A chief executive I worked with last year had just lost a major client, the kind of loss that alters a company. His instinct was to fix it immediately, to call the client, to offer concessions, to do something right now. I asked him to wait three days. Just three days of sitting with what happened and understanding the loss before reacting to it.

He didn't want to. It felt like doing nothing. But when we talked again on day three, he'd seen things he never would've caught in the rush to fix it.

The client relationship had been deteriorating for months. The product wasn't serving them the way it needed to. The account team had been covering for problems instead of escalating them. It wasn't a single event, it was an accumulation, and the only way to see that clearly was to slow down and sit with it.

How do you bounce back from failure this week?

If you're inside a fresh failure right now, here's the process I'd run over the next seven days. It's the same one I ran at fifteen without knowing it, and the one I still run now.

  • Days 1 to 3: let the wave pass. No major decisions, no fixes, no announcements. The first emotional response is loud and almost always wrong about what actually happened. Give it 72 hours to burn off, like the self-pity did for me.
  • Day 3 or 4: write the technical autopsy. One page. What actually went wrong, mechanically - not "I wasn't good enough" but where, specifically, the gaps were. Trainable on one side, not trainable on the other.
  • Ask one question only: "what's the information here?" Not "whose fault is this?" The first question opens the file. The second one closes it.
  • Pick the single most trainable gap and put the work on your calendar. Not all of them. One. My slow starts became a daily block of practice, not a vague vow to be better.
  • Tell one person the honest version. Not the spin, the real one. Saying it out loud is usually when you find out which parts of your story are ego protection.

This isn't something you do once and master. It's a practice that gets better with repetition but never becomes automatic. I still feel the pull to sprint away from losses, to paper over them with the next win, to treat failure as something to survive rather than something to learn from.

The discipline is in the pause. Letting the initial emotional wave pass without acting on it.

Sitting with the discomfort of having been wrong or having fallen short. Then getting curious instead of getting defensive - asking "what's the information here?" instead of "whose fault is this?"

What did Milan Cortina remind me about losing?

In February 2026 I worked the Milan Cortina Games for Yahoo Sports, sixteen years removed from my last race, and here's the arithmetic nobody puts on the broadcast: the overwhelming majority of athletes at any Olympics go home without a medal. Years of work, resolved in seconds, and for most of them the answer comes back no.

I stood in mixed zones this winter listening to athletes talk minutes after the biggest disappointment of their lives, and you could already hear the fork in the road in their voices. Some were narrating a verdict: it's over, I blew it, I wasn't enough. Others, often through tears, were already somewhere else - the start was late, the line into the second corner was wrong, here's what the next cycle looks like. Same pain. Completely different relationship to it.

I recognized the second group, because that's the move those weeks after my first trials taught me. The ones who metabolize the loss into information are the ones you see again. The resilience work I do with organizations is built on exactly that distinction - resilience isn't toughness, it's digestion.

What do you do with the failures that leave scars?

I've failed at more things than most people know about. Business ventures that didn't work, relationships I handled badly, investments that went sideways, decisions I'd undo if I could. The ones that made me better were the ones I stayed with long enough to learn from. The ones that left scars were the ones I ran from.

The failure isn't the end of the story. It's the raw material for whatever comes next. But only if you stay with it long enough.

The long version of this lesson is in Zero Regrets: what competing at that level cost me, and what it gave back in return.

If you're in a season where things aren't going the way you planned - that's most of what I write about in the Hard Pivot newsletter. The space between the setback and the next move. Join me there.

--AAO

The Hard Pivot Newsletter

One idea a week on pressure, performance, and reinvention.

Subscribe and get Chapter 1 of Hard Pivot free.

No spam. Unsubscribe anytime.