This transcript was produced by robots and left as-is. Accuracy and elegance are not guaranteed.

In the last episode, we talked about the upward signal, managing your relationship with your boss as a deliberate act of information engineering. This episode is a little harder. At least your boss has an organizational stake in your success. When you win, they win. On the other hand, peers, contractors, cross-functional teams don’t.

You can’t set their priorities. You can’t assign them tasks. And the more senior you get, the more of your real work runs through people who owe you absolutely nothing. Most engineers end up in one of two failure modes when this happens. The first is logic and persuasion. Build an airtight case, present it, and watch it create resistance.

Because nobody likes being told what to do even when the logic is sound. The second is avoidance. You don’t want the friction of that awkward conversation, so you just absorb the work yourself. You become the bottleneck. Now we covered that trap in episode four, but this version is worse because you didn’t inherit it from your team. You built it yourself.

So here’s the mechanic. Lateral influence runs on shared stakes, not persuasion. You’re not convincing someone to care about your problem. You’re finding the version of the problem that’s already their problem and naming it out loud. Engineers are actually well equipped for this. They just don’t recognize it as a design task. There’s three inputs. Stake identification,

low cost entry and a clear reciprocity signal.

For the last two summers, I was filling in as a construction manager for a client. The client didn’t report to me, it was very much the opposite, and all of the contractors worked directly for the client. None of them reported to me. The authority gap was total. So what I did instead was look for the thing that was already true for everyone on that job. Permits take a long time to write and issue.

Time in the window matters. And weekends are nobody’s friend. Nobody showed up Saturday morning with plans to be there. At various points during the project, I came back to a couple of lines. One was, if we finish this up today, it’s under the same permit. We don’t have to write a new one tomorrow for the same work. The other one that was way more important,

is if we finish this up today, nobody has to come in tomorrow on Saturday. And things moved at that one. The pace picked up. People pushed through to close out the day’s work. Not because I asked them to, because they already had plans. And if they could avoid the weekend, so could I. That’s not motivation. That’s stake identification, delivered as a statement of fact. The stakes were already there.

Shared, real and sitting in plain sight. I just named them. I didn’t ask them to care about my schedule. They didn’t ask me to care about theirs. But when I found the thing that was already true for everyone in the room and said it plainly, the low cost entry took care of itself. Nobody had to change their position, take a risk or do me a favor. They just had to keep doing what they were already doing,

albeit slightly faster for a reason that was already theirs. So before your next lateral ask, run three questions. First, what does this person actually care about in their work right now?

Next, where does that overlap with the outcome that you need? And finally, what’s the easiest possible first move for them? You’re not looking for leverage, you’re looking for a shared stake that’s already sitting right there.

Next episode, we’re going to talk about what happens when the relationship system breaks down. Not because the stakes weren’t shared, but because the friction got avoided for too long.