Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / How to Manage a Boss Who Is a Perfectionist and Never Satisfied
Transcript
- Lucas: So let's talk about the boss who is never satisfied. The perfectionist. The one who looks at a deliverable you spent two weeks on and says, 'This is good, but let's tweak the font — and actually, can we rethink the whole structure?' Luna: Oh, I've had that manager. The goalposts move every time you approach them. It's exhausting. Lucas: Exactly. And there's a specific case I want to anchor this on. A product manager I know — let's call her Sarah — worked at a mid-sized SaaS company. She spent six months redesigning their customer dashboard. The CEO had approved the scope. Stakeholders had signed off. But her direct manager, a VP of Product, kept finding issues. Luna: What kind of issues? Lucas: Little things. The shade of blue was two hex codes off. The loading animation should be a spinner, not a progress bar. Then three days before the launch deadline, the VP said, 'Actually, I think we need to rethink the information hierarchy — let's move the key metrics to a separate tab.' That's a complete overhaul. Luna: And Sarah had to start from scratch? That's brutal. Lucas: She had to delay by two months. And the pattern kept repeating. Every project, same thing. She'd deliver, he'd reject or ask for massive revisions. The team morale tanked. And here's the thing — her boss genuinely believed he was upholding high standards. He saw himself as the guardian of quality. Luna: Yeah, that's the tricky part. Perfectionist managers often don't see themselves as the problem. They think they're helping. Lucas: Right. And before we go deeper — this is actually a good moment to mention that conversations like this are exactly what keep Fexingo going. If this show has helped you navigate a difficult work situation or think through a career move, a couple of dollars a month genuinely makes a difference. You can find us at buy me a coffee dot com slash fexingo. It's what keeps these episodes ad-free and focused. Luna: Yeah, and it really does add up. We hear from listeners who say a single episode changed how they approached a tough conversation. So thanks to anyone who chips in. Lucas: Alright, back to the perfectionist boss. So why do they behave this way? I think the root is often anxiety masquerading as rigor. They're afraid of delivering something that gets criticized, so they keep the project in a state of perpetual improvement — which never actually ships. Luna: That resonates. It's like they're outsourcing their own fear of failure onto your work. Lucas: Exactly. And the standard advice — 'just set clearer expectations' — often fails because perfectionists resist specificity. If you say 'let's define what done looks like,' they'll say 'we can't know yet, we'll know it when we see it.' That's a control move. Luna: So what actually works? Because generic advice like 'communicate more' is useless when the other person doesn't want to be pinned down. Lucas: There's a four-step strategy I've seen work. Step one: proactively define 'done' in writing, with explicit success criteria, and get sign-off from the broadest group you can — not just the perfectionist. Loop in a stakeholder, a peer, even a customer. That creates a social contract that's harder for one person to override. Luna: So you're building a coalition. That's smart. Lucas: Yes. Step two: use time-boxed iterations. Instead of a six-month project with one big review, break it into two-week sprints with a hard launch date for each increment. The perfectionist can't say 'let's rethink the whole thing' on the last day if you've already shipped three versions. Luna: That forces closure. I like that. Lucas: Step three: reframe their feedback as trade-offs. When they say 'this isn't good enough,' ask 'what improvement would you prioritize if we only have three days?' That pushes them to rank their concerns. Often they can't articulate a single concrete thing — which reveals that the complaint isn't about quality, it's about anxiety. Luna: And if they do name something, you've got a specific fix. Lucas: Exactly. Step four: build an ally network. Find someone senior who respects your work — maybe the VP of Engineering or a director from another department — and ask for informal feedback on your major deliverables before the perfectionist sees them. If that ally says 'this is great,' you have ammunition. Luna: So when your boss starts nitpicking, you can say 'actually, the CTO reviewed this and thought it was ready to ship.' Lucas: Right. And that's not undermining your boss — it's just getting a second opinion. But you have to be careful not to make it look like you're going over their head. Frame it as 'I wanted to get a broader perspective before the launch.' Luna: What about the scenario where nothing works? You've tried all four steps, and your boss still moves the goalposts. When do you say 'this is a lost cause'? Lucas: Good question. There's a diagnostic: if your manager consistently delays shipping, rewrites your work from scratch, and never expresses satisfaction — even privately — you may be dealing with pathological perfectionism. That's not fixable through managing up. Luna: At that point, what do you do? Lucas: Document everything. Keep a log of every project scope change, every delayed deadline, every instance where their feedback contradicted earlier approval. Then have a direct conversation — not accusatory, but data-driven: 'I've noticed that on the last three projects, we've had to re-scope after I thought we were done. Can we figure out a process to prevent that?' Luna: And if they still resist? Lucas: Then you escalate. Not to HR with a complaint — but to your skip-level or to a mentor in the organization. Say 'I'm struggling to deliver effectively because of repeated scope changes. Can you help me understand if there's a way to align our process?' That positions you as proactive, not whining. Luna: And ultimately, if the organization tolerates that behavior, you may need to decide if it's worth staying. Lucas: Exactly. A perfectionist boss can stunt your growth because you never get the satisfaction of shipping, never get the feedback that comes from real users. You're just polishing endlessly. And that's not a career — that's a holding pattern. Luna: So the takeaway: don't try to cure your boss's perfectionism. Instead, build systems that force closure, build alliances that validate your work, and if all else fails, know when to walk. Lucas: Exactly. Sarah eventually left that company. She now works at a startup where the motto is 'ship and iterate.' She told me her only regret is that she stayed two years too long. Luna: That's a powerful lesson. Sometimes the best way to manage a difficult boss is to find a better one. Lucas: Well said. That's all for this episode. Thanks for listening.