Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / How New Managers Can Navigate Cross-Functional Conflict
Transcript
- Lucas: Let me paint a picture. It's your third week as a new product manager. Engineering tells you the feature you promised the CEO for next quarter will take twice as long as you planned. Your old peer—now a peer in a different silo—says your timeline is unrealistic. You feel stuck. You don't want to escalate. You also don't want to fail. Luna: That's a specific kind of knot. It's not just a scheduling problem—it's a relationship problem with someone you used to grab lunch with. Lucas: Exactly. And most new manager training skips this entirely. They'll teach you how to delegate, how to give feedback, how to run a meeting. But cross-functional conflict—where you have no authority over the other person, but you need them to move—that's the gap. Luna: So what do we actually do when we're in that chair? Lucas: I want to walk through three moves. First, separate positional from personal stakes. Second, find the shared metric. Third, escalate if you must—but do it without burning the bridge. Let's take them one at a time. Luna: Start with the first one—positional versus personal. What does that look like in practice? Lucas: When the engineering lead says your timeline is unrealistic, they're defending their team's capacity. That's positional. But underneath, they might also feel micromanaged or worry that saying yes means their team crunches for months. That's personal. If you only argue about the timeline, you miss the emotional layer. Luna: So you have to name both. Something like, 'I hear you that the timeline is tight. And I also wonder if you're worried about burnout.' Lucas: That's exactly the move. The Harvard Negotiation Project calls it 'separating the people from the problem.' In a cross-functional conflict, the person isn't the enemy—the constraint is. By acknowledging their position and their feelings, you lower the temperature. Then you can actually problem-solve. Luna: And the shared metric—that's the second move. What does that mean? Lucas: Every department has a north star. For product, it's often customer impact or revenue. For engineering, it might be code quality or system reliability. But there's usually an overlap. In our scenario, both the product manager and the engineering lead care about the product launching successfully without a major outage. That's a shared metric—'successful launch with zero P0 incidents.' If you can frame the conversation around that, you're on the same side. Luna: So instead of 'I need this by November 1,' it's 'How do we get this out safely before the end of the year?' Lucas: Right. And once you agree on the shared metric, you can negotiate trade-offs. Maybe you cut scope. Maybe you add a phased rollout. Maybe engineering gets an extra sprint, but you commit to a beta in Q4. The shared metric gives you a compass. Luna: Okay, but what if that doesn't work? What if the other person is dug in and won't budge? Lucas: Then you escalate. But here's the nuance—you escalate the problem, not the person. You go to your boss or their boss and say, 'We have a disagreement about how to achieve our shared goal of a successful launch. We've tried to find a middle ground, and we need help breaking the tie.' That frames you as collaborative, not combative. Luna: And you don't blindside them. You say, 'I'm going to loop in our managers because I want to get this unblocked. I'll tell them we both want the same outcome.' Lucas: Exactly. A 2025 study from the Project Management Institute found that cross-functional projects fail 40 percent more often when conflicts are escalated without prior notice. The act of telling the other person you're escalating—and why—preserves the relationship. Luna: That's a specific number. Forty percent. It's worth the five-minute conversation beforehand. Lucas: Honestly, if today's episode helped you think through a tricky cross-functional situation, that's exactly the kind of practical takeaway we hope you get. And if it was worth a coffee to you, that's the link—buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small gesture that keeps this show ad-free and focused on real, usable advice. Lucas: So back to that conflict—let's talk about a real example. I spoke with a product manager at a mid-size SaaS company last month. She was new to the role, and her engineering counterpart was a ten-year veteran. He told her her roadmap was 'fantasy land.' Luna: Ouch. How did she handle it? Lucas: She used all three moves. First, she acknowledged his position—his team was already overcommitted. She also said, 'I can imagine it's frustrating to have a new PM come in and push for aggressive dates.' That's separating positional from personal. Then she found the shared metric: both of them wanted a feature that would reduce customer churn. That was the north star. Finally, they agreed on a phased approach where engineering would deliver a minimum viable version in Q4, and the full scope would come in Q1. Luna: Did she have to escalate at all? Lucas: No. The shared metric did the heavy lifting. But she told me she was ready to escalate if needed. Having that plan gave her confidence. And the engineering lead actually thanked her afterward for listening. Luna: That's the dream outcome. But what about cases where the other person is just not acting in good faith? Maybe they're protecting their turf or they have a personal grudge. Lucas: That's a different beast. If you suspect bad faith, document everything. Send a follow-up email after every conversation summarizing what was agreed. Use language like, 'Just to confirm, we discussed X and you committed to Y by Friday.' That creates a paper trail. If the pattern continues, you escalate with evidence. Luna: And you keep the conversation focused on the shared metric. Even if they're playing politics, you stay on the high road. Lucas: Exactly. Because at the end of the day, your reputation as a new manager is built on how you handle these moments. Cross-functional conflict is a test of your leadership—not just your project management skills. Luna: Let's talk about the emotional side too. When you're a new manager, you might feel like you're not allowed to push back. Imposter syndrome whispers, 'Who are you to challenge the engineering lead?' Lucas: That's real. And it's why move one—separating positional from personal—is so important. It gives you a script. You're not attacking them. You're saying, 'I see your constraint. Let's find a way together.' That's not aggressive. That's collaborative leadership. Luna: And if they still don't budge, you have the escalation path. But most people will respond to the collaborative approach. Lucas: A quick framework to remember: p s e. Position, Shared metric, Escalate. It's not perfect for every situation, but it's a starting point. And it beats getting stuck in a cycle of resentment. Luna: I like that. p s e. Easy to recall when you're in the moment. Lucas: So next time you're a new manager staring down a cross-functional standoff, try it. Name the position. Find the shared metric. And only escalate if you have to. Your relationships—and your career—will be better for it. Luna: And if you have a story about a cross-functional conflict you've navigated, we'd love to hear it. You can reach us at the show's page. Lucas: We'll be back next episode with another practical leadership conversation. Until then, take care of yourself and your team.