Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the I Am Not a People Person Employee
Transcript
- Lucas: We've all worked with someone who says, 'I'm not a people person,' as if it's a fixed trait they can't develop. But here's the thing: in most roles, some level of collaboration is non-negotiable. Luna: Right. And that phrase often becomes a get-out-of-jail-free card for avoiding anything that involves another human being. But it's not always laziness — sometimes it's genuine discomfort. Lucas: Exactly. I'm thinking of a case at a mid-sized SaaS company — about four hundred employees, growing fast. They had a senior developer, let's call him Mark, who was brilliant with code but never joined client calls, skipped team retrospectives, and only communicated through Slack messages. Luna: I've seen that type. How did his manager handle it? Lucas: For a year, she let it slide because Mark's output was good. Then a key client complained that they felt ignored — they wanted to hear directly from the technical lead. That forced a change. Luna: So the manager had to address the 'people person' narrative head-on. Lucas: Yes. And what worked is worth breaking down into three approaches. First, clarify minimum expectations. Not 'become a social butterfly,' but 'you need to appear on two client calls per quarter and attend the retrospective once a month.' Luna: Measurable, low-bar. That respects his zone while meeting the business need. Lucas: Second, reframe the narrative from personality to skill. Saying 'I'm not a people person' implies it's intrinsic. But client communication is a skill — it can be practiced. The manager pointed out that Mark already explained complex code to junior devs, so he had the raw ability. Luna: That's a great reframe. It takes it from identity to behavior. Lucas: Third, create a safe structure. The manager introduced what she called a 'communication passport' — a checklist of interactions Mark had to complete each quarter: one client kickoff, two status updates, three internal demos. He could prepare scripts in advance. Luna: So structure replaces the anxiety of improvisation. That's smart. Lucas: And it worked. After two quarters, Mark became comfortable enough that he started offering to lead demos. His own words: 'I still don't love it, but I know I can do it without panicking.' Luna: That's the goal — not to turn everyone into an extrovert, but to expand their toolkit. Lucas: Let me throw in a statistic. A Gallup study found that teams with high collaboration are twenty-one percent more profitable. That's a massive incentive for managers to address the 'not a people person' excuse. Luna: And ignoring it can cost you clients, as we saw with Mark's company. Lucas: Right. But the manager's approach here is what I want listeners to take away: don't threaten or punish. Instead, clarify the minimum, reframe the identity, and scaffold the behavior. Luna: What about employees who say they're 'not a people person' about internal collaboration, not just client-facing work? For example, a designer who won't attend cross-functional meetings. Lucas: Good point. The same framework applies. You say, 'I need you at the weekly sync to share your progress. Bring one visual or decision you need input on. That's it.' Luna: And if they still resist? Lucas: Then it becomes a performance issue. But in my experience, most people just need a smaller ask and a clear reason why their presence matters. If you can connect it to their own goals — 'your designs ship faster when engineering understands the rationale' — that helps. Luna: So it's really about managing expectations and providing a safety net. I've seen managers go too far the other way, forcing weekly presentations on someone who freezes up. Lucas: That's a mistake. The point isn't to make them uncomfortable; it's to build competence incrementally. A good rule of thumb: start with observation, then assisted participation, then independent interaction. Luna: That's a solid progression. And speaking of building competence without pressure, that's actually why we keep this show ad-free. We want to offer useful frameworks without any sales pitch attached. Lucas: Yeah, if that matters to you, there's a simple way to support the show: buy me a coffee dot com slash fexingo. It's just a small gesture that keeps the ads out and the content focused. Luna: Exactly. And now back to our people person — any final thoughts on how to close that conversation with an employee who still pushes back? Lucas: I'd say be direct but empathetic. You can say, 'I understand this feels outside your comfort zone. But the role requires it, and I'm going to help you get there. If after six months it's still a struggle, we'll reassign that responsibility — but for now, let's try my plan.' Luna: That shows both firmness and support. Good balance. Lucas: So next time an employee tells you they're not a people person, ask yourself: am I asking them to change who they are, or just to stretch a few centimeters? Because the answer changes everything.