Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Perfectionist Without Breaking Their Spirit
Transcript
- Lucas: So you have this employee who turns in flawless work. Every deliverable is polished, every email is meticulously worded, every presentation is pixel-perfect. And yet, somehow, you are worried. Luna: Yeah, because the cost of that perfection is starting to show. Maybe they are turning things in late, or they are burning out, or they are hoarding work because they don't trust anyone else to do it right. Lucas: Exactly. And as a manager, you are in a bind. You do not want to crush their drive or diminish their standards. But you also know that perfectionism, left unchecked, can actually hurt the team. I think the first step is to separate perfectionism from high performance. Luna: That is a key distinction. High performance is about achieving excellent results efficiently. Perfectionism is about an unrelenting need to avoid mistakes, often at the cost of speed, collaboration, and well-being. Lucas: Right. And there is research on this. Organizational psychologist Adam Grant has written about how perfectionists often set impossibly high goals, and when they inevitably fall short, they experience shame and self-criticism. That emotional toll can actually reduce their long-term output. Luna: So how do you approach someone like that? You cannot just say 'lower your standards.' That would feel like an attack on their identity. Lucas: No, you have to reframe what 'good' means. One technique I have seen work is to introduce the concept of 'learning goals' versus 'performance goals.' A performance goal is 'I must get an A on this presentation.' A learning goal is 'I want to learn how to communicate this data more effectively.' Both can lead to excellent work, but the learning goal reduces the fear of failure. Luna: That is interesting. So you are shifting the focus from outcome to growth. But how do you actually bring that up in a one-on-one without making them defensive? Lucas: I think you start with curiosity. You say something like, 'I have noticed that you consistently deliver high-quality work, and I really appreciate that. At the same time, I am wondering how you feel about the process. Does it ever feel like the standard you set for yourself costs you more time or energy than you would like?' You are inviting them to reflect, not prescribing a fix. Luna: And if they say yes, then you can explore together. But what if they say no—that they are fine? Do you push? Lucas: You do not push. You bring data. For example, if their perfectionism is causing late submissions, you can say, 'I have noticed that the last two projects were delivered after the deadline. I know the quality was high, but missing deadlines creates downstream pressure on the rest of the team. Can we talk about how to balance quality and timeliness?' Luna: That is concrete. And it ties the feedback to business impact, not personal criticism. Another angle I have seen work is to model vulnerability. If you, as the manager, share a time when you submitted something that was 'good enough' and it turned out fine, it gives them permission to relax a bit. Lucas: Absolutely. I remember a product manager at a SaaS company I worked with—let us call her Sarah—who was a perfectionist. She would spend hours tweaking the wording on feature descriptions. Her manager, a guy named Tom, started sharing his own 'good enough' stories in team stand-ups. He once said, 'I shipped that last release with a known typo in the release notes because I decided the fix could wait. And you know what? Nobody complained.' Luna: That kind of modeling is powerful. It signals that leadership values speed and learning over flawlessness. But Tom also did something else: he gave Sarah explicit permission to prioritize. He said, 'For this project, I want you to aim for 80 percent quality and hit the deadline. We can iterate later.' Lucas: Yes, that is crucial. Perfectionists often need a specific target. If you just say 'do your best,' they will default to 100 percent. But if you say 'I need this by Friday, and I am okay with 80 percent quality,' it gives them a clear boundary. And you have to mean it—you cannot then nitpick the 80 percent work. Luna: Right. And if you do that a few times, they start to see that 80 percent is often enough. Over time, you can gradually increase the quality bar again as they learn to calibrate. But there is another layer: some perfectionists also micromanage their teammates. Lucas: That is a common pattern. They do not trust others to meet their standards, so they either redo other people's work or take on everything themselves. That can destroy team morale and bottleneck progress. Here, the intervention is different. You have to set clear expectations about their role and the team's autonomy. Luna: Yeah. I have seen managers use a 'red line' approach: they tell the perfectionist, 'You can review this work, but you cannot change it unless it is below a certain threshold. For example, if it is factually incorrect, flag it. But if it is just a stylistic difference, let it go.' Lucas: That is a good tactic. And you can pair it with a 'three-strike rule' for delegation. If the perfectionist assigns a task to someone else, they are not allowed to redo it unless there are three specific errors. That forces them to let go and gives the other team member room to grow. Luna: So we have covered reframing goals, modeling vulnerability, setting explicit quality targets, and curbing micromanagement. But what about the emotional side? Perfectionists often tie their self-worth to their output. If you criticize their work, they take it personally. Lucas: That is the hardest part. You have to separate the person from the work. One way is to use 'process feedback' instead of 'person feedback.' Instead of saying 'you are too detailed,' say 'the level of detail in this section slowed down the review process. Next time, could we aim for a draft with the key points first, then add polish later?' Luna: And you can also affirm their identity as a high performer while challenging the behavior. Something like, 'I know you care deeply about quality, and that is one of your strengths. I want to help you apply that strength in a way that does not burn you out.' Lucas: Exactly. That message says 'I see your value, and I want to protect it.' And that is a powerful foundation for change. I think the bottom line is that managing a perfectionist requires a delicate balance of validation and redirection. You are not trying to fix them—you are trying to help them become a more effective version of themselves. Luna: And honestly, if we have helped you think through that balance today, that might be worth the price of a coffee. If today was useful, you can support the show at buy me a coffee dot com slash fexingo. It is a small way to keep us ad-free and focused on content like this. Lucas: Yeah, we appreciate that more than we can say. It really does help. So back to the topic—one more practical exercise I have seen work is to ask the perfectionist to write down their standard for a task before starting. Then, after they finish, ask them to compare the actual outcome to that standard. Often they realize they exceeded it by a wide margin. Luna: That is a great calibration tool. It builds self-awareness. Over time, they start to see that 'good enough' is actually better than perfect in many situations, because it allows for iteration and feedback. Lucas: Right. And that is the ultimate goal: to help your perfectionist employee become not just a high performer, but a resilient, adaptable one. Because in a fast-changing market, the ability to ship and learn is often more valuable than the ability to polish. Luna: Well said. And if you have a team member who is both brilliant and demanding of themselves, I hope this episode gives you a few tools to support them without breaking their spirit.