Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / How to Use Strategic Incompetence Without Harming Your Career
Transcript
- Lucas: So I want to start with a confession — and I'm not proud of it, but here we are. About five years ago, I was working at a mid-size tech company and my manager kept asking me to update a weekly spreadsheet that was basically a glorified color-coded status tracker. It took maybe an hour, but it was mind-numbing. Luna: Let me guess — you started 'accidentally' breaking the formulas? Lucas: I didn't just break them. I subtly introduced errors that made the whole thing look unreliable. And then, after a couple of weeks of my manager getting frustrated, she reassigned it to someone else. I felt a little guilty, but also — I got my hour back. Luna: You weaponized incompetence, but you did it strategically. Which is basically the topic of today's episode. Lucas: Exactly. Strategic incompetence — the deliberate underperformance or feigned inability to avoid certain tasks. There's a 2024 study in the Journal of Organizational Behavior that found nearly 15% of workers admit to using this tactic at some point. Luna: Fifteen percent. That's one in seven people. And I bet the real number is higher because people probably don't admit it in surveys. Lucas: Right, social desirability bias. But the study is interesting because it distinguishes between two types: one is defensive incompetence — you do it to avoid burnout or protect your time. The other is offensive — you do it to manipulate who gets credit or blame. Luna: And the second one is where your reputation takes a real hit. Lucas: That's the key distinction. So today I want to look at how you can use strategic incompetence sparingly and smartly — without getting caught and without damaging your career. Because there is a right way and a wrong way. Luna: And maybe also talk about when it backfires spectacularly. Lucas: Let's get into the case that brought this to my attention. A friend of mine — let's call her Sarah — worked at a Fortune 500 consumer goods company in brand management. She was great at her core job: consumer insights, campaign strategy. But every quarter, she had to produce a 30-page operations review that nobody read. Luna: The classic busywork. Lucas: So she started submitting it late. Then she started including data that was slightly off. Nothing critical, just enough that her boss would say, 'You know, maybe I should have Mark do this, he's more detail-oriented.' And it worked — for about a year. Luna: But I'm guessing there's a 'but' coming. Lucas: The but is: the company went through a reorganization. New VP comes in, wants to know who owns what. Her boss is asked, 'Why did you move that report off her plate?' And the boss says, 'She wasn't reliable.' Suddenly, in the new org chart, Sarah is seen as someone who can't handle operational rigor. Luna: And that's the risk. You get labeled for the behavior, not the intent. Lucas: Exactly. The tactic only works if the people around you don't realize it's a tactic. Once they catch on — or worse, once it becomes part of your permanent record — you've lost more than you gained. Luna: So what's the right way to do it? Because I think there are times when it's valid — especially if you're drowning in low-value tasks. Lucas: Speaking of drowning — we should take a quick moment here. If this show helps you think through career moves or decisions, a small number of listeners actually chip in monthly at buy me a coffee dot com slash fexingo. It's how we keep this thing ad-free and focused on real workplace dynamics. Luna: Yeah, it's a pretty small group, but it makes a big difference. And it means we don't have to sell you a mattress or a meal kit. Lucas: Exactly. So if you've gotten value from episodes like this, that's where to go: buy me a coffee dot com slash fexingo. And now back to the fine art of strategically failing. Luna: All right, so the right way. Give me the framework. Lucas: First, you only deploy this on tasks that are clearly low-value and low-visibility. If the CEO is going to see it, or if it's tied to a revenue number, you own it completely. Second, you need to be excellent at your core responsibilities. Luna: So it's a contrast effect. You're good at the important stuff, so people are more likely to overlook your 'weakness' on the trivial stuff. Lucas: Exactly. The study I mentioned found that strategic incompetence is most effective when the employee has high social capital and high performance in their primary role. If you're already seen as a top performer, people attribute your failure on a minor task to 'everyone has blind spots' instead of 'they're gaming the system.' Luna: But if you're already struggling in your main job, it just looks like more evidence. Lucas: Right. So rule one: be indispensable first. Rule two: never use it on the same task twice. If you fail at something and it gets reassigned, don't then fail at something similar — that's a pattern. Luna: So Sarah's mistake was using it on the same recurring task every quarter. That's a pattern. Lucas: Exactly. A one-time 'oops, I'm not great at spreadsheets' can be believable. A pattern of 'oops, I'm never great at spreadsheets' is a liability. Rule three: make sure the failure is minor and fixable by someone else in a short time. Luna: You don't want to create a fire that burns down the whole project. Lucas: Right. Strategic incompetence should cost the organization, at most, an hour of someone else's time. If it causes a missed deadline or a client complaint, you've crossed into real incompetence. Luna: What about the emotional toll? Because I think pretending to be bad at something you're actually good at feels... icky. Lucas: It does. And that's why I think the best approach is actually to be transparent about your strengths and weaknesses in a more honest way. Instead of feigning incompetence, you can say, 'Look, I'm really good at the analysis, but the formatting takes me twice as long as it would take you. Could we trade?' Luna: That's delegating, not deceiving. Lucas: And that preserves your reputation. But I also understand that not every workplace allows that level of candor. Some managers will just say 'do it anyway' and then you're stuck. Luna: So strategic incompetence becomes a last resort for people who don't have enough power to negotiate their workload. Lucas: Yes. And that's where it gets tricky. Because if you're in a low-power position, you're also the most vulnerable to getting caught and penalized. Luna: So the people who can most afford the risk are the ones who need it least. Lucas: That's the paradox. Which is why I think the most sustainable strategy is to build enough trust and credibility that you can say no directly. But that's a longer game. Luna: Let's talk about when it backfires. Besides Sarah's case, do you have other examples? Lucas: There's a famous example from the dot-com era. An engineer at a startup kept 'accidentally' breaking the build on Friday afternoons so he wouldn't get paged over the weekend. Eventually, the CTO noticed the pattern and he was let go. The company couldn't trust him with mission-critical code. Luna: Which is ironic because he was probably great at his job otherwise. But the one thing he failed at was the thing that mattered most in that context. Lucas: Right. The issue was, the build was high-visibility, even if it was routine. So rule four: never use strategic incompetence on anything that's part of your core job description. Luna: So for a software engineer, the build is core. For a brand manager, the operations report might be periphery. Lucas: Exactly. And that's the judgment call. You have to be honest with yourself about what you're actually paid to do. If your manager's job is to make sure that report gets done, and you make her look bad, you're in trouble. Luna: There's also the risk of it becoming a habit. I've seen people who start with strategic incompetence on one task, and then it spreads to more and more things until they're actually underperforming. Lucas: That's the slippery slope. The study calls it 'competence erosion.' You start by faking it, but eventually you stop developing those skills altogether. Then when a promotion comes up that requires those skills, you're genuinely not ready. Luna: So the antidote is to periodically check yourself: Is this a one-time tactic, or am I building a habit? Lucas: Right. And I would add: keep a list of the tasks you've strategically failed at, and make sure you're not avoiding the same type of work for more than six months. Because if you never learn a skill, you're not being strategic — you're just avoiding growth. Luna: That's a good point. So let's say I want to use this tactic once for a low-value task. What's the playbook? Lucas: Step one: confirm the task is genuinely low-value and no one's career depends on it. Step two: do a half-hearted version — not so bad that it causes a problem, but bad enough that someone else thinks they could do it better. Step three: when someone offers to take it over, be gracious. Say 'That would be a huge help, I really struggle with this stuff.' Luna: And then don't complain about losing it. You want them to feel like they've helped you. Lucas: Exactly. And step four: double down on your core strengths. Make sure your performance in your main role is so strong that nobody questions your overall competence. Luna: I've also seen people use strategic incompetence to avoid being promoted into a role they don't want. Like, a top salesperson who doesn't want to be sales manager might 'accidentally' show poor leadership skills. Lucas: That's a whole other use case. And it can be effective, but it's risky because it limits your trajectory. If the company ever restructures, you might be seen as un-promotable. Luna: So it's a short-term solution that can have long-term consequences. Lucas: Which is why I think the best approach is to combine strategic incompetence with intentional skill development. If you're going to duck out of a low-value task, use that time to build a high-value skill. That way, you're not just avoiding — you're investing. Luna: So Sarah should have used the hour she saved from the ops report to learn something that would make her more valuable in the reorg. Lucas: Exactly. Instead, she just coasted. And when the reorg came, she had no new skills to point to. So the strategic incompetence was exposed as just... incompetence. Luna: I think the bottom line is: use it rarely, use it on truly trivial tasks, and make sure your core performance is undeniable. Lucas: And be honest with yourself about why you're doing it. If it's to protect your time for higher-value work, that's a good reason. If it's just laziness or resentment, it will probably backfire. Luna: So I'm curious — do you still use it today? Or have you moved to more transparent methods? Lucas: I try to be transparent now. But I'd be lying if I said I never accidentally misspelled a name in an email to avoid being put on a project I know is a time sink. Luna: The typo defense. Classic. Lucas: It's a small sin. But I'm aware of the risk. And I think that's the key — awareness. As long as you know what you're doing and why, and you've weighed the consequences, it's not necessarily unethical. It's a tactic. Luna: It's a tactic with a shelf life. Use it too long and it expires. Lucas: Exactly. So my challenge to listeners this week: look at your task list. Identify one low-value thing you're doing that you could strategically delegate — honestly or not. Then use the time you save to learn one skill that makes you more valuable. That's the winning play. Luna: I like that. It turns a potentially shady tactic into a career development strategy. Lucas: That's the goal. Thanks for listening, and we'll see you next time.