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 wrong

Before 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. I