The 1:1s Nobody Schedules (And Why That's Costing You)

There's a pattern I've watched play out, and it goes like this: a manager hits a wall, something's blocked, they need a decision or a resource or a favor from someone in another department, so they send a cold Slack message or shoot off an email to someone they've barely spoken to in six months. And then they wait, and wonder why it takes so long, and complain in their next team meeting that "cross-functional collaboration is broken here."

It's not broken; the relationship is just nonexistent, and you're asking a stranger for help.

The Problem Isn't Process

Every organization I've seen has blamed process for what is actually a relationship problem. The escalation chains, the RACI matrices, the "cross-functional working groups" that meet quarterly and produce slide decks: these are what happens when people try to engineer around the absence of genuine relationships. They rarely work because the real currency in any organization isn't process, it's trust, and trust doesn't get built in a kickoff meeting.

Here's what I know from managing in large orgs for over three decades: the managers who get things done aren't the ones with the most authority. They're the ones who already have a relationship with the person they need. When they reach out, the other person responds quickly, not because of org chart proximity, but because they actually know each other. That's not a soft skill observation; it's a practical, observable advantage that competes on the same level as technical competence or strategic thinking.

And the way you build those relationships is almost embarrassingly simple. You schedule a 15-minute recurring meeting with key peers before you need anything from them.

Why Managers Don't Do This

The most common reason I hear is that it feels awkward to schedule a 1:1 with someone you don't work with directly. There's no obvious agenda, no standing reason to meet, and managers worry they'll come across as needy or political, so they skip it.

The second reason is time. Everyone's calendar is already packed, and adding recurring meetings feels like more weight on a sinking ship. Both of these are real, but they're also solvable, and the ROI makes them worth solving.

A peer 1:1 is not a status update meeting. It doesn't require a formal agenda. Its only job is to make you two people who actually know each other, which means when friction occurs between your teams, you can have a direct conversation instead of routing through your managers or waiting for the next quarterly sync. That's the whole payoff, and it's enormous.

How to Set Up Your First One Without It Being Weird

The message I've seen work best is also the most honest one. Something like: "Hey, I've been thinking about how little we actually talk, given how often our teams interact. I'd love to set up a monthly 30-minute call, not for any specific project, to stay connected and share context. Would that work for you?"

Nine times out of ten, the other person says yes immediately, because they've been thinking the same thing, and nobody made the first move. You don't need to dress it up. You don't need an elaborate pitch. You need to ask.

If you're unsure of who to prioritize, look where friction currently lives in your work, which teams you depend on the most, which partners create the most downstream complications for your team, and who you email or Slack when things go sideways. Those are your tier-one peer relationships. Start there.

What to Actually Talk About

A peer 1:1 is structured differently from a 1:1 with a direct report. You're not coaching or managing performance; you're building mutual understanding, and the conversations that do that best tend to stay close to a few recurring questions.

What's keeping you busy right now? This one surfaces priorities you might not know, which matters when you're about to ask for something or when your team is about to create work for them.

What's coming up that I should know? Upcoming launches, reorgs, resource crunches, leadership changes: the things that will affect your work before they appear on the org-wide announcement. Peers who trust each other share this information. It's enormously useful.

What can I do to make your team's life easier? This one surprises people because managers rarely ask it of peers. But it signals that the relationship is genuinely reciprocal, not just transactional, and it often surfaces small things you didn't know you were doing that were creating friction downstream.

You don't need all three every time. Some months, the whole conversation is about one of them. The point is to have a structure loose enough to follow the real conversation while tight enough to ensure you leave with something useful.

The ROI Nobody Quantifies

I want to be concrete about what this actually buys you, because it's easy to dismiss relationship-building as a soft priority when your Q3 deadline is burning.

When your team makes a mistake that affects a peer's team, and you have an established relationship, you get a direct conversation instead of an escalation. That's probably three to five days of saved time and political capital right there.

When you need a decision that requires input from someone in another department, a peer who knows you will prioritize that input differently than a stranger will. You're not at the bottom of their mental queue.

When something ambiguous needs to get resolved between your teams, you can pick up the phone and sort it out in ten minutes instead of routing it through two managers and a project manager. I've watched that particular dynamic save weeks of delay on projects that had no business taking that long.

And then there's the thing that's hardest to quantify but most valuable: when leadership is watching how you handle cross-functional complexity, the managers who are visibly collaborative, who get called by their peers, who are known across the org rather than just within their vertical, those are the managers who get the harder roles, the broader scope, the next opportunity.

Investing 15 minutes a month in a peer relationship isn't a soft strategy. It's the infrastructure your effectiveness runs on.

The Compounding Effect

Relationship capital works like financial capital in one specific way: it compounds. The peer who barely knows your name in January is a real ally by June if you've been consistent, and a genuine advocate by December. The conversations get richer. The context you share deepens. You start connecting each other to other people, and your network of actual working relationships inside the organization grows without you having to manufacture it.

The managers who feel stuck, who complain that they can't get traction, who constantly run into the same cross-functional walls: they're almost always managing vertically and ignoring horizontally. Their relationships go up and down the org chart, but not across it, and so every cross-functional interaction starts from zero.

Schedule the 15 minutes. Do it this week, before there's a fire to fight, before you need something, before the quarter gets hard. Build the relationship when there's no pressure, because that's the only time you actually can.