The Chief Failure Officer: Why Getting It Wrong Matters More Than You Think

We've been failing since the wheel was invented. So why are we still so scared of it?

There's a certain woke, eye-roll required when saying the title "Chief Failure Officer, " but in a world where everyone's optimising their LinkedIn headlines and celebrating wins, here's someone whose actual job is to talk about what didn't work.

And before you ask: yes, this is a real role; it probably comes in different versions that might also include innovation or transformation, but its not so much about the title, as it is about the intention behind the role... their job isn't to fail on purpose (that would be weird), but to make failure safe, normal, and useful.

Why This Matters

The premise is simple: innovation and failure are a package deal. If everything you try works, you're not innovating. You're just doing what you already know how to do, maybe slightly better.

The Chief Failure Officer exists to make it okay to try things that might not work. They're the person who asks "what did we learn from that?" instead of "whose fault was that?" That shift in language, small as it sounds, changes everything.

The Myth

You'd think a role like this would be aligned with a massive corporation with deep pockets, companies that can afford to launch ten products knowing nine will tank. This creates a dangerous assumption: that failure-friendly cultures are a luxury you can only afford when you're already successful.

That's backwards.

Small organisations, tight budgets, resource constraints, these are exactly when you need to experiment. You just need to do it smart.

Failure on a Shoestring

The principles scale down perfectly. You don't need a dedicated executive or millions in experimentation budget. You need a mindset shift and some practical habits.

Test cheaply. Most assumptions can be tested for almost nothing. Mock up that feature in Figma. Send that email to twenty customers. Try that new process for one week with one team. Your experiments don't need to be expensive to be informative, actually, cheaper is often better because you can run more of them.

Make failure safe. Set aside specific time or projects where "it didn't work" is an acceptable outcome. Maybe it's one afternoon a month. Maybe it's 10% of someone's time. The permission matters more than the percentage.

Share what didn't work. When someone tries something and it fails, your response determines everything. Awkward silence teaches people to play it safe forever. Genuine curiosity about what was learned teaches them to keep trying. Choose wisely.

Keep a record. A simple document where people log experiments that failed and why. Over time, this becomes invaluable organisational memory, a map of dead ends so nobody wastes time re-visiting them.

The Real Role

In a smaller organisation, the Chief Failure Officer might be 5% of someone's job. Their responsibility is simple: be the person who asks the uncomfortable questions.

• What's the smallest version we could test?

• How will we know if this isn't working?

• What did we learn from the last thing that failed?

• Are we failing enough?

That last one is key. If you haven't had a good failure recently, you're probably optimising instead of innovating. Both are important, but they are different things.

What Nobody Talks About

Playing it safe has costs too. The opportunity you didn't pursue. The competitor who was willing to experiment. The team that's learned not to suggest anything bold.

Research shows failure-friendly cultures actually outperform failure-phobic ones. When people feel safe to experiment, they try more things. Most fail. But the occasional success more than pays for everything that didn't work.

Start Small

If this resonates but you're not sure where to begin:

Pick one small thing to test this month. Before you start, define what you'll learn whether it works or not. Then do it, document what happens, and share it with your team without apologising. That's it. That's the entire job: creating space for intelligent experimentation and making it okay to say "that didn't work" without career-limiting consequences.

You don't need a new org chart. You just need to decide that trying beats not trying, and that learning from failure is worth more than protecting your track record. Because here's the thing: the only people who never fail are people who never try anything interesting. And in a world that's changing faster than ever, not trying might be the biggest risk of all.

Happy Failing!