Chapter 20: The Network You Build Before You Need It

Back in chapter thirteen, you mapped who actually holds influence around a specific project. That map was reactive by design, built because you needed something from a particular effort, right then. This week is different. You're building relationships before you need anything from them at all, which sounds backwards, but is actually the only way this kind of thing ever works.

Here's the pattern worth noticing. Most people only reach out across departments when they need something. A favor, information, a quick yes on something time-sensitive. The message practically announces itself as transactional, because it is one. The person on the receiving end can tell, and even if they help, it rarely turns into anything more than a one-off.

The people who build real internal capital do something different, almost invisibly. They show up in other people's inboxes with something useful, and no ask attached. A piece of information relevant to someone else's project. A quick introduction that costs you nothing but helps two people who didn't know they needed to meet. A genuine question about how someone else's work is going, asked because you're curious, not because you're softening them up for something later.

This isn't about being likeable for its own sake. It's about the simple mechanical reality that when you eventually do need cross-departmental support, whether that's for a bigger initiative, a resourcing ask, or just information nobody else will hand you quickly, you're not starting from zero. You're drawing on a relationship you already built, back when there was nothing in it for you.

When you genuinely don't know where to start

All of this assumes you have someone in mind. Often, you won't. If you're in analytics, and you've never had a real reason to talk to anyone in operations, "reach out to someone in a different function" is a fine instruction that doesn't actually tell you who to email.