Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / How to Use Strategic Incompetence at Work
Transcript
- Lucas: So there's a move in office politics that sounds like career suicide on paper but actually works if you do it right: it's called strategic incompetence. Luna: Strategic incompetence? That sounds like deliberately being bad at something. How is that not just a fast track to getting fired? Lucas: Right, that's the immediate reaction. But the key word is 'strategic.' You're not bad at everything — you become selectively bad at the things that aren't actually your job, so you can free up capacity for the work that matters. Lucas: Think of it like a triage nurse. You don't treat a papercut with the same resources as a heart attack. Strategic incompetence is about consciously deprioritizing the papercuts so you don't burn out. Luna: Okay, but let's get concrete. Who does this actually work for? I'm picturing a junior analyst trying this and getting a bad performance review. Lucas: Good point. It works best when you already have a reputation for being competent. Once you've proven you can do the work, you have some political capital to spend. The classic case is a mid-level product manager I came across — let's call her Priya. Lucas: Priya was great at strategy, user research, and roadmapping. But her boss kept asking her to maintain a complicated spreadsheet of feature requests that took hours every week. It was low-value admin work. So she started making tiny errors — nothing fatal, just enough that her boss stopped asking her to do it. Luna: So she got bad at spreadsheets on purpose? That's bold. Did it backfire? Lucas: In her case, no. The boss handed the spreadsheet to someone else who actually enjoyed that kind of work. Priya got back six hours a week for strategy. She eventually got promoted. But the risk is real — if you're not careful, you can get labeled as unreliable. Luna: So what's the boundary between smart and stupid here? Where does strategic incompetence cross into just being a slacker? Lucas: I think there are three rules. Rule one: only apply it to tasks that are low-visibility and low-impact if they fail. A spreadsheet with mild errors is fine. A client presentation? Not the place to goof off. Lucas: Rule two: you need to be excellent at the stuff that actually matters. If you're mediocre at your core job, strategic incompetence just looks like regular incompetence. Lucas: And rule three: you have to be subtle. You're not announcing 'I'm going to be bad at this.' You just let the quality slip a tiny bit, and when someone notices, you apologize and explain you're focusing on the critical path. Luna: That last point is huge. There's research on 'strategic self-handicapping' — it's a term from social psychology. People who claim they're bad at something to lower expectations sometimes actually perform worse. But the ones who do it selectively — without saying it out loud — tend to protect their reputation. Lucas: Exactly. The verbal version is almost always a mistake. If you say 'I'm not good at spreadsheets' you've just created a narrative. But if you submit a spreadsheet with one small error and then fix it quickly, the narrative is 'she's busy, not incapable.' Luna: And that's the office politics move — you're managing the perception of your workload. You're signaling that your time is better spent elsewhere. Lucas: Right. And it's not just about individual tasks. It can be about entire categories of work. I've seen senior engineers strategically 'forget' to attend meetings that don't need them, and they delegate the notes to a junior. They're not incompetent — they're prioritizing. Luna: But what about the person who picks up that spreadsheet or those meeting notes? Doesn't strategic incompetence just shift the burden to someone else? Lucas: That's the ethical question, and it's real. I think the difference is whether the task genuinely belongs to you. If it's your job, own it. But if it's scope creep — someone else's busywork that's been dumped on you — then declining it is actually fair. Lucas: In high-trust teams, there's research showing that when people explicitly negotiate task allocation, everyone is happier. Strategic incompetence is just a clumsy version of that negotiation. The ideal is to have the conversation directly, but not all workplaces allow that. Luna: So this is a tool for environments where saying 'no' directly is risky. That makes sense. In a lot of corporate cultures, you can't just refuse a task from your boss. Lucas: Exactly. And that's where strategic incompetence becomes a political tactic. You're not refusing — you're just being slightly less reliable on that one thing, so the boss naturally reallocates it. It's a soft no. Luna: I want to go back to Priya. Did she ever tell her boss what she was doing? Or was it completely covert? Lucas: As far as I know, she never confessed. And I think that's the right call because once you admit it, it becomes a manipulation. The whole point is that the boss makes the decision themselves — they decide the spreadsheet isn't worth Priya's time. That feels like their own insight, not a push from her. Luna: That's actually a classic influence technique — getting someone to arrive at your preferred conclusion on their own. It's the Columbo close from a couple episodes back, but applied to task management. Lucas: It really is. And it works because people trust their own judgments more than someone else's suggestion. So if your boss concludes that you're not the best person for the spreadsheet, they'll feel good about delegating it elsewhere. Luna: Okay, but let's talk about the risks. When does this blow up? Lucas: Biggest risk: you get caught. If someone realizes you're sandbagging on purpose, your reputation takes a hit. Trust is hard to rebuild. Lucas: Second risk: you accidentally go too far. If you make a real error that has consequences — like missing a deadline or costing the company money — that's not strategic, that's just a mistake. Lucas: Third: you might condition your boss to see you as bad at something, and later when you want to do that kind of work again, you've painted yourself into a corner. Luna: So it's not a long-term strategy. It's a short-term fix for a specific overload situation. Lucas: Exactly. Use it sparingly, and only for tasks that aren't core to your role. And always keep your core competencies sharp. Luna: You know, this episode is exactly the kind of practical insight that keeps people coming back to the show. And I know we don't do ads, which is intentional — it keeps the content clean. Lucas: Yeah, we've always wanted it that way. But the trade-off is that listener support is what keeps us going. If you've gotten something out of these episodes — maybe a tactic you've actually used at work — a couple of dollars a month genuinely matters. Luna: It really does. It's how we stay ad-free and focused on the content you need. If you're able, you can support us at buy me a coffee dot com slash fexingo. Lucas: And now back to the pitfalls, because there's one more I want to flag. Strategic incompetence can become a habit — and that's dangerous. If you start using it for everything, you lose the ability to do the work at all. Luna: So you're saying it's a scalpel, not a sledgehammer. Lucas: Exactly. Use it on one or two specific tasks that are draining your time, and then build a system for the future. Ideally, you get to a point where you don't need it because you've negotiated better boundaries upfront. Luna: So the endgame is to be so good at your real job that people naturally stop giving you busywork. Strategic incompetence is just a bridge to get there. Lucas: That's it. And the political lesson is: manage your workload by managing perceptions. Sometimes the most productive thing you can do is look slightly less capable at the things that don't matter. Luna: One more question: does this work differently in remote or hybrid environments? Because if you're not in the office, your boss can't see how busy you are. Lucas: Great question. Remote actually makes it harder to pull off because you can't subtly underperform in a visible way. In person, a slightly messy spreadsheet gets noticed. On Zoom, you have to be more deliberate — like taking a beat longer to respond when asked about a task, or saying 'I can get to that next week' instead of doing it right away. Lucas: The same principles apply, but the execution is more about timing than quality. You're signaling capacity constraints through your schedule rather than through errors. Luna: That's a good nuance. So strategic incompetence isn't just about being bad — it's about being selectively unavailable. Lucas: Right. And the best practitioners make it look natural. They're not gaming the system — they're just making smart choices about where to invest their energy. And that's really the core of office politics: understanding that your time is a resource, and you have to allocate it intentionally. Luna: Well said. I think we've given people a lot to think about. Next episode, we'll talk about another delicate move: how to take credit for a team success without looking like a glory hog. Lucas: That's a good one. Until then, try being a little less perfect at the things that don't matter — and see what happens.