Cross-functional work often looks simple on the project plan and complicated in real life. You need another team to prioritize something. A peer manager owns a dependency. A designer, product person, engineer, or operations lead sees the problem from a different angle. Nobody reports to you. Nobody has to obey your timeline just because your work feels urgent.
This is where leading across becomes very practical. The 360° Leader treats peer influence as one of the hardest and most important forms of leadership, precisely because positional authority is mostly absent. You cannot command your peers into trust. You have to earn it.
There is no shortcut through authority
When you lead across, the usual shortcuts do not work. You cannot rely on hierarchy. You cannot force motivation. You cannot simply escalate every disagreement and call that collaboration. With peers, your real tools are credibility, respect, consistency, and the ability to make cooperation worth their effort.
This starts with understanding their pressure. Before asking another team to prioritize your request, it helps to know what they are measured by, what constraints they are under, and what would make the work easier for them. A request that ignores their context often sounds like noise. A request that shows you understand their world has a better chance of being heard.
Care before influence
Maxwell's model of leading across includes a progression: care, learn, appreciate, contribute, and win together. The order matters. Many people try to start with contribution or persuasion before they have shown any real interest in the other person. That makes the relationship feel transactional.
Caring does not have to be dramatic. It may look like remembering what a peer team is carrying this quarter, giving credit publicly, asking what would reduce friction, or noticing the invisible work that keeps your own project moving. Appreciation, when it is specific and honest, lowers defensiveness. It says: I see your work as more than a dependency on my board.
Only after that does contribution become natural. You help because the relationship is not merely a negotiation. You share context, remove friction, lend people, adjust a timeline, or protect a shared priority. Influence across the organization grows from repeated evidence that working with you makes the system better.
Healthy competition raises standards; politics lowers trust
Peer relationships often contain competition. That is not automatically bad. Healthy competition can raise the standard. A strong peer can make you prepare better, think sharper, and refuse lazy work. The problem begins when competition becomes political: making someone else look smaller so you can look larger.
Political behavior may create a short-term advantage, but it damages the trust needed for cross-functional work. People remember who took credit, who withheld context, who used escalation as a weapon, and who disappeared when the work became difficult. Leading across requires the opposite pattern: protect the shared goal even when it does not make you the main character.
Protect the best idea, not only your idea
One of the clearest tests of peer leadership happens in meetings. If your peer offers a better approach than yours, can you support it? If the answer is yes, your influence often grows. People learn that your goal is not to win every argument; your goal is to help the work win.
This is especially important in technical and product teams. The best idea may come from someone outside your function. A designer may see adoption risk. A support lead may see the customer pain more clearly. An engineer from another team may notice an operational cost you missed. Defending your own idea after it is no longer the best one is not leadership. It is ego with a roadmap.
You do not need to perform perfection
Leading across also becomes easier when you stop pretending to be flawless. Peers do not need a perfect person. They need a trustworthy person. Someone who can say, "I missed that," "I need your view," or "your approach is better" often becomes easier to collaborate with than someone who has to protect an image.
Vulnerability does not mean oversharing or lowering standards. It means being honest enough that other people do not have to spend energy decoding you. In peer relationships, that kind of ease is valuable. It makes disagreement safer and collaboration faster.
Leading across is not about becoming more charming. It is about becoming the kind of peer whose presence makes shared work clearer, fairer, and more likely to succeed.
Key Takeaways
- Leading across has no authority shortcut. When you cannot command a peer, your influence comes from credibility, respect, and helping them win too.
- Peer influence begins with understanding pressure. Before asking another team to prioritize your request, learn what they are measured by and where they are blocked.
- Appreciate before you demand cooperation. Specific recognition makes collaboration less defensive.
- Healthy competition raises standards; politics lowers trust. Good competition makes the product better. Bad competition makes another person look worse so you can look better.
- Protect the best idea, not only your idea. Supporting a peer's stronger proposal can build more trust than winning the argument.
- You do not need to perform perfection. Owning mistakes, asking when unclear, and inviting feedback often create more durable influence than never appearing wrong.
- Small exercise: choose one peer you work with often and ask, "what is one thing from my side that would make your work easier this week?"
Leading across is slow because it is built relationship by relationship. But that is also why it lasts. A peer who trusts your intent and your competence will often move with you faster than a person who merely receives your request through a process.