Not Every Failure Counts Against You - MAC158

Two people walk out of two different meetings having heard the same sentence: it didn't work. One of them skipped a step in a process the company has run four hundred times. The other tried something the company has never tried. Same sentence, same tone in the room, same quiet adjustment in how each of them gets described in the next talent review.That's the problem underneath this whole piece: your organization almost certainly cannot tell those two people apart. Not because anyone up the chain is cruel — because sorting the difference is genuinely hard and the meeting has twenty minutes. That failure to sort is expensive in a very specific, very avoidable way, and there's a fix that costs about ninety seconds and changes the entire conversation.Three kinds of wrongBefore any of this is useful, the terminology has to be exact. Amy Edmondson, a Harvard Business School researcher who has spent a career studying how organizations handle things going wrong, lays out three distinct kinds of failure, and argues they need opposite responses.A basic failure has one cause, is usually preventable, and happens in territory that is completely known — the invoice with last quarter's numbers, the wrong client name in the deck, the checklist step skipped because the day ran long. There's no mystery and no glory here. A basic failure needs a system, not a lesson.A complex failure happens when several things go wrong at once and no single one of them would have caused the problem alone — the vendor slips a week, the reviewer is on leave, the requirements quietly changed in a meeting nobody wrote down. You don't eliminate complex failures. You build slack and make the pieces visible to each other.And an intelligent failure is the one nobody teaches. Edmondson sets four conditions for it: it happens in genuinely new territory where no playbook exists; it's a credible route toward something that matters; it's informed by what you already know, not a wild swing; and it's kept as small as possible while still teaching you something.An intelligent failure isn't a mistake. It's the price of information you couldn't have bought any other way.I want to sharpen something I said in an earlier episode, Own Your Mistakes, Deliver Results (MAC-149). I stand behind most of it, but I treated "your mistake" as one category — a thing you step toward, own cleanly, and move past. What I missed is that a good chunk of what gets called your mistake was never a mistake at all. It was a bet. And owning a bet the way you'd own an error isn't integrity — it's a filing error, and you're the one who filed it.Here's the distinction: a mistake is something you should have known. A bet is something nobody knew. Notice that has nothing to do with the outcome — both end in it didn't work. The difference sits entirely in what was knowable beforehand, which is exactly the information that disappears the moment the result is on the table.The lane nobody is driving inMost organizations respond to all three kinds of failure identically — not from cruelty, but because sorting them is slow and the meeting is short. So the org reacts to the outcome, the one piece of information everybody already has. Basic, complex, intelligent — same flinch, same footnote in the calibration room. I covered where that instinct goes once it's left alone in The Blame Game (MAC-099); what's happening here sits one step upstream of blame, in the sorting that never occurs in the first place.People learn fast, and what they learn isn't "don't be careless." It's "don't be the person standing next to the uncertain thing." They stop volunteering for the ambiguous project. They stop floating the idea that would need a real test. I've watched this happen to people who were, on paper, the strongest performers in the room. None of them decided to become conservative — they just took the only signal the system was actually giving them: unpredictability is expensive.That produces an empty lane. Almost everyone in your organization competes in the same place — flawless execution on known work — because that's where the incentives point. Meanwhile the genuinely ambiguous proj