Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage the Employee Who Always Says I Did My Part
Transcript
- Lucas: So here's one I hear from managers all the time: 'My top performer does excellent work, meets every deadline, never misses a detail — but the moment I ask them to collaborate with another team, they say: I did my part.' Luna: Yeah, that phrase is like a wall. 'I did my part' — it sounds reasonable, but it also completely stops the conversation. Lucas: Exactly. And the manager is left thinking, wait — your part was to write that report, but we needed you to attend the handoff meeting so the analytics team could understand your assumptions. You did your individual task, but the team outcome didn't happen. Luna: So how do you even start that conversation without sounding like you're dumping extra work on someone who's already delivering? Lucas: I think the first thing is to diagnose the root cause. In my experience, this isn't usually insubordination or laziness. Often it's a genuine mismatch in how the employee defines their job. They see their role as a set of discrete tasks, not as part of a shared result. Luna: Right — they're operating on a 'task completion' model, not an 'outcome achievement' model. Lucas: Precisely. And that mindset gets reinforced in a lot of workplaces. If you've been rewarded for years based on individual productivity metrics, collaboration feels like overhead. There's a 2025 Gallup survey I saw that said 41 percent of remote workers report lower cross-team collaboration than when they were in the office. So this problem is getting worse, not better. Luna: Forty-one percent — that's huge. And I bet the 'I did my part' attitude is stronger among remote employees because they don't organically see how their work connects to others. Lucas: Exactly. So the solution isn't to scold them or say 'you need to be a team player.' That just creates defensiveness. Instead, I've seen managers succeed with a four-step approach. Step one: clarify expectations proactively, not reactively. Luna: Meaning you set the collaboration expectation before the project starts, not after they've already said 'I did my part'? Lucas: Yes. When you kick off a project, say something like: 'For us to consider this a success, it's not enough that each person finishes their piece. We need the handoffs to be smooth, and we need everyone to attend the integration review.' That way, the employee knows from day one that collaboration is part of their job. Luna: But what about the employee who's already in that pattern? They've said 'I did my part' multiple times. You can't just go back in time and set expectations. Lucas: No, you can't. So step two is a one-on-one conversation where you connect their individual tasks to the team outcome. Use specific examples. Say: 'I know you finished the data analysis on time — that was excellent. But when you didn't attend the handoff meeting, the operations team couldn't interpret your findings, and the launch was delayed by a week.' Make it concrete. Luna: So you're showing them the cost of not collaborating. That's powerful. Lucas: Right. And then step three: use peer-based examples. If there's someone on the team who is really good at cross-functional work, point to them as a model. Not to shame the employee, but to say: 'Here's how Sarah handles it — she sends a one-page summary before the meeting and then follows up with a Slack message. That's the kind of collaboration we need from everyone.' Luna: That feels less accusatory. It's a 'here's what great looks like' rather than 'you're failing.' Lucas: Exactly. And step four: create low-stakes collaborative assignments. Don't throw them into a high-pressure cross-functional project right away. Instead, give them a small task that requires one brief meeting with another team. Make it easy to succeed. Luna: Like asking them to review a document from the marketing team and provide feedback in a shared doc. Low commitment, but it builds the muscle. Lucas: Perfect example. And after they do it, you reinforce: 'That feedback helped marketing adjust their campaign. Thanks for taking the time.' You're positively reinforcing the behaviour. Luna: That's really practical. But I want to go back to something you said earlier — the idea that this is often a mindset issue, not a bad attitude. Can you unpack that a bit more? Lucas: Sure. I once worked with a SaaS company — roughly 200 employees — and they had a senior engineer, top of the stack, never missed a deadline. But he kept saying 'I did my part' when asked to help the product team with specifications. The CEO was ready to fire him. But when I talked to the engineer, he said: 'My job is to write code. The product team's job is to write specs. If they can't do their job, that's not my problem.' Luna: Wow. So he genuinely believed that helping another team was outside his role. Lucas: Yes. And he wasn't wrong — from a strict job-description perspective. But the company needed him to be part of the product development cycle, not just a code factory. So we redefined his role: 'Your job is to help ship great products. Writing code is your main tool, but sometimes that means reviewing specs or joining design reviews.' Luna: And did it work? Lucas: It did, eventually. It took about three months. He started attending spec reviews, and he actually found bugs in the product logic before any code was written. He became one of the most valuable people in the company. But it required reframing his job, not just telling him to do more. Luna: That's a great case study. And it shows that 'I did my part' can be a symptom of how you've defined the role, not the person. Lucas: Right. And that's why the manager's job is to clarify the outcome, not just the tasks. If the team outcome is 'launch a feature by Q3,' then everyone's part includes the handoffs. If someone says 'I did my part,' you can say: 'Our part was to launch the feature, and we haven't done that yet. So we're not done.' Luna: Speaking of outcomes — you know, this is exactly why we keep the podcast ad-free. We want to focus on practical outcomes for you, not sell you something. If this kind of conversation has helped you in your career, you can support the show at buy me a coffee dot com slash fexingo. It's a small way to keep us independent. Lucas: Yeah, we've never taken ads, and that's intentional. The support from listeners is what makes that possible. So if you've gotten value from episodes like this one, that link is buy me a coffee dot com slash fexingo. Now back to that SaaS engineer — what was the biggest takeaway you had from that case? Luna: I think it's that the employee's resistance to collaboration was actually a failure of role design, not a personality flaw. The manager had set them up to think of their job narrowly. Lucas: Exactly. And once you broaden the role definition, the behaviour changes. But it requires the manager to be intentional. You can't just hope people figure out that collaboration is part of their job. Luna: So what if the employee still pushes back even after you've clarified expectations and given them low-stakes tasks? Lucas: Then it becomes a performance issue. But most of the time, if you've done steps one through four, the employee will come around. If they don't, you escalate. You say: 'Collaboration is a core part of this role. If you can't do it, we need to discuss whether this is the right position for you.' Luna: That's firm but fair. And it's a last resort. Most people want to be part of a successful team — they just need to see how. Lucas: That's the whole thing. The 'I did my part' wall comes down when the employee understands that their part is the team's outcome. Not just their individual task.