Managers rarely succeed through technical ability alone. They succeed because they can work with people across different teams, priorities and personalities.
Start building those relationships before you need them. Learn what other departments actually do, and how your team's work affects theirs. When you ask for help, explain why the request matters, and when another team is under pressure, don't treat their delay as a personal failure. Look for ways to make collaboration easier instead.
"I don't know much about how your team actually works day to day, and I'd like to. Do you have twenty minutes sometime this week?"
You don't have to get political. Nobody's asking you to pretend to like everyone. What actually earns you a reputation is being reliable, respectful and focused on solutions.
Your boss is thinking about how you will represent the team. The brilliant person who creates unnecessary conflict everywhere they go is a risky bet for management. The person who can get two teams to actually cooperate usually gets picked instead, brilliance or not.
Friendliness helps, but it won't carry you by itself. What carries you is understanding incentives, communicating clearly and following through. People trust colleagues who do what they say, raise concerns early and avoid creating surprises.
You should also learn to distinguish disagreement from conflict. Healthy disagreement can improve decisions. Different opinions aren't the problem. Disagreement turns into conflict when it:
- goes personal
- gets hidden
- drags on unproductively
As a future manager, practice separating the person from the issue. You can challenge a proposal without questioning someone's competence or motives.
Ask these before the project starts, not after the two teams are already blaming each other. When working across teams, clarify:
- What each team is responsible for
- What each team needs from the other
- Which deadlines are fixed
- Which deadlines are flexible
- Who has decision authority
- How changes will be communicated
- What happens when priorities conflict
"Heads up before this lands on your side, we're shipping the pricing change Thursday. Let me know if that creates any problems on your end before then."
- Learn their world. Schedule a short conversation with someone from another department, ask what challenges their team is facing, learn how your work affects their deadlines, learn the language and priorities of partner teams.
- Be useful. Share useful information before they have to ask, invite the right people into conversations early, offer context instead of sending unexplained requests, introduce colleagues who may benefit from knowing each other.
- Be reliable. Follow through on commitments, keep a record of commitments and follow up when necessary, thank people specifically for their help, give credit to partner teams, avoid blaming other departments in public, ask for feedback after a difficult collaboration.
"I would like to understand how our team's work affects yours. What information or support would make collaboration easier for you? Are there any recurring problems in the way we work together that I should be aware of?"
Instead of writing, "I need this by tomorrow," try giving context and room to respond.
"We are preparing the client response for Friday, and your team's data is needed for the final section. Would it be possible to receive it by Thursday at noon? If that timing is difficult, please let me know what date is realistic so we can adjust the plan."
When two priorities conflict, try: "It sounds like we are optimizing for different outcomes. Our team is focused on [priority], while your team needs [priority]. Can we clarify which constraint is fixed and where we have flexibility?"
Tip: build relationships before you need a favor. People are more likely to help someone they recognize as reliable and respectful. Don't wait until a deadline is urgent to introduce yourself to another team.
This week: book twenty minutes with one person on another team and send them the script from Starting the Conversation.