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 do. Understand how your team's work affects theirs. When you ask for help, explain why the request matters. When another team is under pressure, avoid treating their delay as a personal failure. Look for ways to make collaboration easier.
This does not mean becoming political or pretending to like everyone. It means developing a reputation for being reliable, respectful and focused on solutions. When your boss considers promoting you, they will think about how you are likely to represent the team. A person who creates unnecessary conflict may be brilliant, but they are a risky choice for management. A person who can build cooperation is often far more valuable.
Relationship-building is not only about being friendly. It is about 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. The problem is not that people have different opinions. The problem is when disagreement becomes personal, hidden or unproductive. As a future manager, practice separating the person from the issue. You can challenge a proposal without questioning someone's competence or motives.
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
These conversations prevent many problems before they occur.
- Schedule a short conversation with someone from another department.
- Ask what challenges their team is facing.
- Learn how your work affects their deadlines.
- Share useful information before they have to ask.
- Give credit to partner teams.
- Invite the right people into conversations early.
- Follow through on commitments.
- Avoid blaming other departments in public.
- Thank people specifically for their help.
- Learn the language and priorities of partner teams.
- Offer context instead of sending unexplained requests.
- Keep a record of commitments and follow up when necessary.
- Introduce colleagues who may benefit from knowing each other.
- 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?" This question shows curiosity, respect and a willingness to improve the relationship.
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."
The second version provides context, makes a clear request and leaves room for an honest conversation.
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?" This keeps the discussion focused on the work rather than on blame.
Tip: build relationships before you need a favor. People are more likely to help someone they recognize as reliable and respectful. Do not wait until a deadline is urgent to introduce yourself to another team.