Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Always Works in Silos
Transcript
- Lucas: So this week we're looking at a challenge I hear from a lot of first-time managers, especially in product or marketing teams. The employee who works in silos. Doesn't share updates, doesn't loop in adjacent teams, and your cross-functional project keeps stalling because no one knows what they're doing until the last minute. Luna: Right, and there's a subtle version of this too. The person who's perfectly nice in meetings, but when you look at the actual workflow, they're effectively an island. Information flows in but almost never out. Lucas: Exactly. And the instinct as a new manager is often to assume ill intent. You know, 'They're hoarding power,' 'They don't want to collaborate.' But in my experience, especially with individual contributors who are strong technically, the root cause is usually something else. Luna: What's the most common driver you've seen? Lucas: Two things, and they often overlap. First, a genuine belief that collaboration slows them down. They're measured on output, and in their head, every meeting is a tax on their real work. Second, and this is the one that surprises managers, they often don't have a clear mental model of what 'good collaboration' looks like. No one ever taught them how to hand off work or communicate progress. Luna: So it's a skills gap disguised as a behavior problem. Lucas: Exactly. And once you frame it that way, the intervention changes completely. You're not reprimanding someone for being difficult. You're teaching a workflow. Let me give you a real case. I worked with a marketing operations manager at a SaaS company, about 300 employees. She was brilliant, knew the data stack inside out, but the product team was constantly blindsided by her campaigns going live. They'd find out from customer emails, not from her. Luna: Classic silo. And I bet she felt like she was being efficient. Just getting things done without having to sit through status meetings. Lucas: Exactly her reasoning. When her manager finally sat down with her, she said, 'I don't want to waste people's time with updates. If they need to know, they'll ask.' The manager's move was to reframe it not as 'you need to share more,' but as 'let's define what a good handoff looks like for the product team.' Luna: That's a really important distinction. You're moving from a vague expectation to a specific standard. Lucas: Right. So they created what I call a communication charter. Just a single page document, agreed in a 30-minute 1-on-1. It listed three things: what needs to be communicated, to whom, and at what point in the workflow. For her, it was as simple as: any campaign that goes to more than 10,000 customers, you send a brief Slack message to the product lead at least 48 hours before launch. That's it. Luna: That's so clean. And it addresses the ambiguity that was causing the silo. She probably thought 'share updates' meant a full presentation. Turns out it was just a two-line Slack. Lucas: Bingo. And once you have that charter, you can make it a habit. The manager followed up in their next 1-on-1, asked 'How did the handoff go?' and then it became muscle memory. Within a few weeks, the product team was looped in naturally. Luna: But let me push back a little. What if the silo behavior is actually intentional? Like, what if the person is deliberately keeping information to themselves because they feel it gives them job security? Lucas: That's the harder case, and it does happen. But I'd say it's rarer than managers think. Before you assume malicious intent, test the skills gap hypothesis first. Have a conversation where you literally ask: 'What would make collaboration easier for you?' If they say 'Nothing, I'm fine,' then you might have a trust issue or a power dynamic. But even then, the charter approach gives you a framework to hold them accountable. Luna: Because now you have a written agreement. So when they miss a handoff, it's not about personality. It's about a broken commitment. Lucas: Exactly. And that's a much cleaner conversation. 'We agreed you'd send a Slack 48 hours before launch. That didn't happen. What got in the way?' That's coaching. The other framing is accusatory. Luna: I also think there's a structural angle. Some teams are set up in a way that actually encourages silos. Like if you have a marketing ops person who reports to marketing but spends 80% of their time supporting product. Who do they prioritize? Lucas: Great point. That's a classic org design problem. The person is getting mixed signals from two stakeholders. In that case, the manager's job is to clarify the reporting line and the primary stakeholder. You might need to sit down with the other department head and define a shared set of expectations. Luna: So your advice for a first-time manager: before you label someone as a silo worker, run through three checks. One, is it a skills gap? Two, is it a trust issue? Three, is it an org design problem? Lucas: That's exactly it. And the communication charter is your diagnostic tool. If they can't commit to simple, clear handoffs, you've identified the real issue. If they can, you've solved it. Luna: And I love that it's a one-page document. It's not another process. It's just clarity. Lucas: Right. And honestly, this ties into something we think about a lot on this show. A lot of management challenges come down to making implicit expectations explicit. The silo worker isn't necessarily a bad teammate. They just have a different mental model of what 'keeping people informed' means. Luna: If this kind of practical framework has helped you think through a management challenge at work, we'd love it if you considered supporting the show. We keep Manager Mondays ad-free and listener-supported, and contributions from people like you make that possible. You can find us at buy me a coffee dot com slash fexingo. Lucas: Yeah, honestly, every little bit helps us keep making episodes that get into the specifics—like the communication charter we talked about today. We really appreciate it. Luna: Alright, back to the topic. One thing I want to add: what about the person who works in silos but produces incredible work? Do you ever just let them be? Lucas: That's the tension, right? Deep work versus collaboration. And the honest answer is: it depends on the role. If someone is a senior individual contributor whose sole job is to produce analysis or code, and their output is stellar, you might accept a lower collaboration score. But the moment they become a bottleneck for others, you have to intervene. The charter can help there too. Luna: You mean, you set a minimum collaboration threshold? Lucas: Exactly. 'I need you to spend two hours a week on cross-functional syncs. Outside of that, you can have your deep work time.' That's a compromise that respects their working style while protecting the team. Luna: I think that's a really balanced take. It's not about forcing everyone into the same collaborative mold. It's about finding the minimum viable coordination. Lucas: Minimum viable coordination. I'm stealing that. That's the headline for this episode. Luna: And if you're a manager listening, try the charter this week. Pick one silo-y team member, sit down, and just ask: 'What would make collaboration feel easier for you?' You might be surprised by the answer. Lucas: Alright, that's it for this week. Next time, we're tackling a tough one: how to manage a team member who always volunteers for extra work but then drops the ball. See you then.