Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / How to Use Strategic Failing Upward in Your Career
Transcript
- Lucas: So there's this idea in career strategy circles called 'failing upward.' And the name sounds like a punchline — like, oh great, another way to spin mediocrity. But when you look at how it actually works in practice, it's one of the most counterintuitive, high-leverage moves an ambitious professional can make. Luna: I've heard the phrase thrown around, but I always thought it was just a nicer way to say 'surviving a screw-up.' Is there more to it? Lucas: Much more. The core idea is that a visible, well-timed failure — handled correctly — can actually accelerate your career faster than a string of modest successes. The key word is 'strategic.' You're not just hoping a mistake doesn't hurt you; you're deliberately choosing a situation where the potential upside of failure outweighs the downside. Luna: That sounds risky. Can you give me a concrete example? Lucas: Sure. I know of a case at a Fortune 500 consumer goods company a few years back. A mid-level manager was tasked with launching a new product line into a category the company had never played in before. Everyone knew it was a long shot — the market was crowded, the brand had no credibility there. But the manager went all in, did a splashy launch, and it flopped. Sales were maybe twenty percent of forecast. Luna: Oof. That sounds like a career-ender. Lucas: Normally, yes. But this manager had done something smart beforehand. He had gone to his VP and said: 'This is a high-risk project. If it fails, we'll learn exactly what doesn't work in this category — and that knowledge will be worth more to us than a modest success.' He pre-framed the failure as valuable research. Luna: So he got permission to fail, essentially. Lucas: Exactly. And when the failure happened, he didn't hide. He called a team meeting, laid out the data on exactly why the launch failed — wrong price point, wrong distribution channel, wrong messaging. He turned it into a case study. The VP was impressed. Six months later, he got promoted to a bigger role because he had shown he could take smart risks and extract learning. Luna: I see — so the failure wasn't really a failure in the long run. It was a learning investment that paid off in trust and visibility. Lucas: Right. And that's the essence of failing upward. You're essentially trading short-term outcome risk for long-term reputation capital. But it only works if you follow three rules. Luna: Lay them on me. Lucas: Rule one: choose the right stage. The failure has to happen on a project that has high organizational learning value — something the company doesn't know how to do yet, or a new market, or a new technology. If you fail on a core, well-understood process — like payroll or customer service — you'll just look incompetent. But if you fail exploring something uncertain, it's seen as brave. Luna: So you want to fail where the company expects uncertainty. Lucas: Exactly. Rule two: pre-frame the risk with stakeholders. Before you even start, make sure your boss and key allies understand that this is an experiment, not a sure thing. You want them to say, 'We might not succeed, but we'll learn.' If you don't pre-frame, the failure looks like a surprise and a mistake. If you do, it looks like a calculated bet. Luna: That's the part that requires real political skill. You have to manage expectations without sounding like you're making excuses in advance. Lucas: Big time. You do it by being honest about the uncertainty, not by being pessimistic. Say: 'I've looked at the data, and our odds of hitting the target are maybe forty percent. But even if we miss, we'll know exactly what doesn't work, and that insight could be worth millions.' That's framing. Luna: And rule three? Lucas: Rule three: extract a specific, actionable insight from the failure. You can't just say 'we failed, oh well.' You have to produce a clear diagnosis: 'We failed because X, and now we know that Y is a better approach.' That's what turns failure into learning. It's the difference between being seen as reckless and being seen as a thoughtful risk-taker. Luna: That makes sense. But I imagine this doesn't work in every workplace culture. Some places are zero-tolerance for any kind of failure. Lucas: Exactly right. You have to read your organization. Some cultures — like traditional banks, regulated utilities, or family-run businesses — view any failure as a black mark. In those places, failing upward is almost impossible. But in more innovative, growth-oriented companies — tech firms, startups, consumer goods companies with a culture of experimentation — it's more accepted. Luna: How do you know if your company is the kind where failing upward is possible? Lucas: Look at how senior leaders talk about their own mistakes. If the CEO tells stories about a product that bombed and what they learned, that's a green flag. If everyone sanitizes their resumes and never mentions failures, it's a red flag. Also, look at whether the company has formal 'fail fairs' or post-mortems that celebrate learning over blame. Luna: That's a good litmus test. So let's say you're in a culture that's open to it. How do you actually pick the right project to fail on? Lucas: You want something that is visible to the people who matter — your boss, their boss, maybe an executive sponsor. But not so visible that failure would be a public embarrassment for the whole company. A side project, a skunkworks initiative, a new market experiment. And you want the failure to be quick and cheap — not a multi-year, multi-million dollar disaster. A small, fast failure is a learning opportunity. A big, slow one is a problem. Luna: So you're basically running a controlled burn. Small enough to contain, but big enough to get noticed. Lucas: Exactly. And there's one more nuance: the failure has to be attributable to you, but not entirely your fault. If you failed because of something outside your control — market shift, competitor move, supply chain issue — that's actually better. It shows you're willing to take responsibility for a negative outcome, but you're not incompetent. You're just unlucky or overmatched. Luna: I've seen that play out. A colleague of mine once took over a troubled project that was already behind schedule. She knew it was going to fail, but she accepted it anyway. When it did, she gave a very clear post-mortem about the root causes — many of which predated her. The VP saw her as a clean-up hitter who could handle tough situations. She got promoted six months later. Lucas: Classic failing upward. She used a pre-framed failure to demonstrate leadership under fire. And that's the key difference between failing upward and just failing: the person who fails upward actively manages the narrative around the failure. They don't wait for others to interpret it. Luna: So you have to be the one to tell the story of your failure, and tell it in a way that highlights the learning. Lucas: Correct. You own the failure, but you also own the lesson. And if you do it right, people start to see you as someone who is willing to take risks, humble enough to admit mistakes, and smart enough to learn from them. That's a powerful combination. Luna: I think a lot of people worry that if they fail visibly, they'll be branded as a loser. But you're saying it's actually the opposite — if you handle it well, it can make you look more capable. Lucas: Yeah, but it's a fine line. If you fail too often, even with good framing, people start to question your judgment. So you can only pull this move maybe once or twice in a career. You need to bank some successes in between. Failing upward is a spice, not the main course. Luna: That's a good way to put it. So how do you know when you've built up enough credibility to attempt a strategic failure? Lucas: You need a track record of delivering on the basics first. If you're new to a role or you've already had a few stumbles, don't try this. You first have to establish that you're competent. Then you can use a strategic failure to show you're also brave and insightful. Luna: It's almost like you need to earn the right to fail. Lucas: Absolutely. And that's where a lot of people get it wrong. They try to fail upward without having built any political capital first. They come in hot, take a big swing, miss, and then wonder why they're on a performance improvement plan. You have to earn the trust before you can risk it. Luna: That's a good reality check. So what's the first step for someone who wants to try this? Should they start by talking to their boss about a risky project? Lucas: Start smaller. Look for a project that's already seen as a long shot — maybe something that's been sitting on the back burner. Volunteer to lead it. Then, in your first conversation with your boss, frame it as an experiment. Say, 'I think there's a twenty percent chance this works, but even if it doesn't, we'll learn something valuable.' That's how you start planting the seed. Luna: And if your boss says, 'No, I need a guaranteed success,' then you know your culture isn't ready for this move. Lucas: Exactly. And that's useful information too. If you're in a zero-failure culture, your best career move might be to build a reputation for reliability, not risk-taking. Or to find a different company that values experimentation. Luna: That's a great point. Knowing your environment is half the battle. Lucas: Yeah. And I think that's the core insight: failing upward isn't about being lucky or spinning a disaster. It's about strategically choosing a visible, manageable failure that showcases your ability to learn and adapt. And then managing the narrative so that the organization sees the lesson, not just the loss. Luna: If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. It's a small gesture that keeps us independent. Lucas: Yeah, we really appreciate that. Just a couple bucks helps us keep producing episodes like this without any sponsor pressure. So if you got something out of today's show, consider it. Luna: Okay, back to the topic. So we've talked about how to fail upward, but what about the flip side? How do you protect yourself if you're in a culture that punishes failure? Lucas: That's a great question, and it's actually a different strategy altogether. In a blame-heavy culture, you want to minimize visibility of any failure. Focus on low-risk, high-reliability tasks. Build a reputation for being dependable. And if you do take a risk, make sure you have documented stakeholder buy-in beforehand. Cover your tracks. But honestly, if you're in that kind of culture long-term, you might want to think about whether it's the right environment for your growth. Luna: So failing upward is really a tactic for certain cultures and certain career stages. It's not a universal strategy. Lucas: Exactly. And the best strategists know when to use it and when to play it safe. The key is to be intentional about your career moves, not just reactive. Think about what kind of reputation you want to build, and then choose your projects accordingly. Luna: Alright, I think we've given people a lot to think about. Thanks, Lucas. Lucas: Thanks, Luna. And to our listeners — go ahead and take that smart risk. Just make sure you've framed it first.