Before Session 12 · Failure Immunity
Read this before class — 15 minutes. There's one small task at the end: start your Failure Log. Come-ready is at the end.
The big idea: failure is the raw material of growth
You've spent the last three weeks reaching outward — three plans, sharing them, prototyping conversations with real people. Reaching outward means some of it didn't work. A message went unanswered. A conversation fell flat. A plan you loved on paper sounded hollow when you said it out loud. Good. That's not the cost of the process — that is the process.
Burnett and Evans put it bluntly: if you're designing your life, you're going to fail, because designers run experiments and most experiments don't work. The skill they call failure immunity isn't about failing less, or pretending failure doesn't sting. It's about processing failures fast enough that they turn into information instead of identity — the difference between “that didn't work” and “I'm someone things don't work for.”
Two levels of immunity
Burnett and Evans describe two levels, and most people only ever reach the first. The first level is what you've been practicing for three weeks without naming it: act, find out quickly whether it worked, learn, adjust. When you're clear that the experiment existed to teach you something, the sting mostly disappears — the failed prototype did exactly its job. Their own example is small and a little funny. Right before one of their big Stanford classes, Dave changed a teaching exercise on the spot and ran it cold, in front of eighty students, without even telling Bill. Bill's reaction wasn't alarm. It was something closer to delight — his co-teacher was willing to fail in public to find out if an idea worked. (It worked fine. They went back to the old version anyway, because it was better. That's the whole cycle in one story.)
The second level is bigger, and it's the actual vaccine. Burnett and Evans call it the big reframe of design thinking: life is a process, not an outcome. Most of us walk around quietly judging our lives by results — the grade, the offer, the relationship, the thing that did or didn't happen — as if someone at the end is going to add it all up and hand down a verdict. Designers don't work that way, because a design is never finished; it's always the current version, about to become the next one. If life is a process, then a setback is a stage of it, not the score.
The infinite game
The clearest way they explain that idea comes from the philosopher James Carse, who sorted everything we do into two kinds of games. A finite game has rules, boundaries, and a winner: you play to finish. An infinite game has no final whistle: you play to keep playing, and the point is to stay in it and get better. Passing this course is a finite game. Figuring out what kind of life you want to build — and who you're becoming while you build it — is an infinite one. Making a team is finite. Being someone your teammates trust is infinite. Neither kind is better; you're playing both all the time. The trouble starts when you mistake one for the other — when a finite loss (the no, the B-minus, the message that went unanswered) gets treated as a loss in the infinite game, as if it said something final about you.
It can't. That's where Burnett and Evans land: in the infinite game of becoming more yourself, there's no way to lose, because there's no last round. You'll still have setbacks, some of them painful. But a setback in an infinite game is a move, not a result. Their second reframe of the chapter follows directly: the belief that life is a finite game with winners and losers gets replaced by the recognition that it's an infinite one — nobody wins, nobody loses, everyone's still playing. Hold onto that as you sort your failures below. Most of the ones that sting are finite losses being mistaken for something bigger.
A failure, taken apart
In class, one of your mentors will walk through a real failure of their own — not a humble-brag, not a story where the failure secretly turns out to be a win in disguise. A real one. They'll show you the same move you're about to learn: looking at it through the lens (what actually happened, out there) and then the mirror (what it revealed, in here) — and sorting it honestly into one of the three types below. Watching someone do this without flinching is most of the lesson.
Three types of failure — and why sorting them matters
Screwups — simple mistakes on things you normally get right. You forgot the meeting. You sent the message to the wrong person. The fix isn't growth, it's an apology and moving on. Don't build a narrative out of a screwup.
Weaknesses — failures that come from a part of you that's been true for a long time and probably isn't changing much. You know this about yourself; it's shown up before. The smart move is usually working around it — designing so it matters less — not launching your fourth campaign to finally fix it.
Growth opportunities — failures with an identifiable, fixable cause. Something you could actually do differently next time — and the fix is worth the effort. This is the only category where the right response is “work on it.”
The sorting is the skill. Most people treat every failure like a growth opportunity — which means agonizing over screwups that deserved a shrug, and repeatedly assaulting weaknesses that deserved a workaround. Immunity comes from putting each failure in the right box and giving it only the attention that box deserves.
The Failure Log
The worksheet is in your folder — it has three columns: what happened, which type it was, and what (if anything) there is to learn. Before class, log two or three real failures from the last month. Course-related or not. Small counts. The Life Design Conversation message that went unanswered counts. Don't editorialize — just log, sort, and note.
This week's belief → reframe
The belief that gets people stuck: “If this didn't work, that says something about me.”
The designer's reframe: Failure is data about the experiment, not a verdict on the experimenter. You're never a failure — you're a designer whose prototype taught you something.
Your journal
One entry before class: pick the failure from your log that still stings a little. Write for ten minutes about which type it actually is — screwup, weakness, or growth opportunity — and notice whether you've been treating it as the wrong one. That mismatch, if you find it, is the most useful thing you'll bring to class. One more question as you write: was this a finite loss — a grade, a spot, a yes you didn't get — or did it feel like a loss in the infinite game? Most of the ones that sting are the first kind, mistaken for the second.
Come Ready
Bring your Failure Log with two or three entries started, and your journal entry. Your triad will work with one failure each — you choose which one, and how much of it to share.
ENT 1611 Designing Your Life · FSU Innovation Hub · Failure immunity and the failure types: Bill Burnett & Dave Evans, Designing Your Life (Knopf, 2016) · Lens and mirror: Shawn Ginwright, The Four Pivots · Finite and infinite games: James Carse, Finite and Infinite Games, as discussed by Burnett & Evans · Worksheets and submissions on Canvas