You need something. A reference for a job application, an introduction to someone at a company you’re trying to get into, a piece of advice from someone who’s done the thing you’re about to try. You open your network to see who might help, and the list is people you haven’t spoken to in three years. A few connections you can’t place at all. A profile picture you don’t recognize the name attached to. The network exists, technically. It just isn’t warm enough to actually ask anything of.
This is the moment most people discover their professional networking has been either completely dormant or active only in short, obvious bursts — a flurry of connection requests sent out during the last job search, then silence again until the next one. Both patterns produce the same result: a network that has no idea who you are when you finally need it.
Why does networking usually fail even when you technically “do it”?
Most people’s professional networking activity falls into one of two modes. The first is total silence — a profile that was set up once, filled in reasonably well, and then never touched again. No posts, no comments, no outreach. It exists as a static résumé and nothing more.
The second mode is a burst of activity that only happens when actively job hunting. Connection requests go out to dozens of people at once, often with no note attached, often to people the sender has no actual connection to beyond a shared industry or a mutual contact. Messages get sent asking for referrals, introductions, or “quick calls” from people who haven’t heard from this person in years, if ever.
Both approaches fail for the same underlying reason: there is no existing relationship or context when the ask finally comes. A connection request with no relationship behind it is easy to ignore. A message asking for a favor from someone who has never engaged with you before reads as exactly what it is — a transaction, initiated only because you need something, aimed at someone who has been given no reason to care.
The people who seem to have “good networks” usually didn’t do anything more sophisticated than this: they engaged with people’s work over time, shared their own thinking occasionally, and reached out with real reasons before they needed anything. When they eventually did need something, there was already a light relationship to draw on. That’s the entire mechanism. It isn’t a trick. It’s just slower and less exciting than a targeted campaign of cold messages, which is exactly why most people skip it.
What does genuine engagement actually look like?
This is the part that carries the most weight, and it’s also the part people do worst, because it’s easy to fake badly. Commenting “Great post!” or “So true!” on someone’s update isn’t engagement — it’s noise. It’s instantly forgettable, it signals nothing about you, and the person receiving it can tell it was written in five seconds without reading past the first line.
Real engagement means responding to the actual substance of what someone said. If someone shares an opinion about a shift happening in your industry, respond to the opinion — agree with a reason, push back with a reason, add a detail they didn’t mention, ask a question that shows you actually read it. This takes thirty seconds longer than a generic comment and is worth roughly a hundred times more, because it’s the only kind of comment a person actually remembers who left it.
Sharing something genuinely useful occasionally works the same way. It doesn’t need to be original research. It can be a resource you found helpful, a lesson from something that went wrong on a project, an observation about a change in your field that other people in it would want to know about. The bar isn’t brilliance — it’s usefulness and honesty. A post that’s obviously trying to perform expertise reads as performance. A post that’s just genuinely trying to help or share something true reads as exactly that.
None of this needs to be constant. You don’t need to post every day or comment on everything in your feed. What matters is that there’s some ongoing signal — enough that when your name comes up, or your profile gets a second look, there’s something there beyond a static list of job titles.
How should you actually send a connection request?
A generic, unexplained connection request is easy for the other person to ignore, and even when it gets accepted, it’s easy for them to feel a little odd about having accepted it — they don’t know why you wanted to connect, and neither, really, do you, three weeks later.
A request with one specific, genuine reason works completely differently. It doesn’t need to be long. A sentence or two naming the actual reason is enough: you read something they wrote and had a specific reaction to it, you’re both connected to the same person and working in overlapping areas, you noticed a piece of their work that’s directly relevant to something you’re doing. The point isn’t the length — it’s that the reason is real and specific to them, not a reason that could be copy-pasted onto a hundred other requests unchanged.
This matters for two separate reasons. It’s more likely to get accepted, because a specific reason gives someone an actual basis for deciding you’re worth connecting with. And it’s more likely to lead anywhere afterward, because a connection formed around an actual reason has somewhere to go in conversation — you already have a starting point instead of a blank thread with a stranger.
What makes an outreach message land instead of getting ignored?
The same principle applies to a first message, whether or not you’re already connected. What separates a message someone wants to respond to from one that reads as mass-sent isn’t politeness or formality — plenty of ignored messages are perfectly polite. It’s specificity.
A message that could be sent to fifty different people unchanged reads as exactly that, even if it’s technically addressed to one person by name. “I’d love to pick your brain about your career path” could go to anyone in a similar role. A message that names something specific — a particular project they worked on, a specific transition they made that you’re curious about for a specific reason of your own, a specific question that only makes sense given who they actually are — reads as written for them, because it was.
This takes more effort per message, which means sending fewer of them. That’s the right trade. Ten specific, well-considered messages will produce more real responses and real relationships than a hundred templated ones, and the hundred templated ones will do something worse than nothing — they’ll mark you, in a small way, as someone who sends mass outreach, which is exactly the reputation that makes people stop responding to you at all.
How do you get an informational conversation right?
If someone agrees to talk with you — a call, a coffee, a short meeting — the way you handle it determines whether it becomes a relationship or a single, forgettable interaction.
Start with a genuine, specific question rather than a vague request to “pick their brain.” A vague request puts the entire burden of the conversation on the other person — they have to figure out what you actually want to know and then generate it from nothing. A specific question does the opposite: it shows you’ve thought about what you actually need, and it gives them something concrete to respond to.
Respect their time. Keep the conversation to the length you asked for, come prepared so you’re not wasting minutes figuring out what to ask, and don’t quietly extend a fifteen-minute call into forty-five because the conversation is going well — ask if they have time to continue, and take a genuine no gracefully.
Then follow up afterward. This is the step almost everyone forgets, and it’s where the actual relationship-building happens. A short note thanking them, mentioning something specific from the conversation that stuck with you, or telling them what you did with their advice, turns a single conversation into the start of an actual connection. Without it, the conversation ends where it ended, and there’s nothing pulling it forward. The follow-up costs five minutes. Skipping it is the single biggest reason informational conversations don’t turn into anything.
Why does sharing your own thinking matter if you’re not trying to be an influencer?
Not everyone needs to post constantly, and trying to force a posting habit that doesn’t fit you usually produces content that reads as forced. But a profile that’s been completely silent for years gives people nothing to respond to and nothing to remember you by. When someone looks you up before a call, or scrolls back through your activity after you comment on their post, silence tells them nothing except that you exist.
Occasional posts — a lesson learned, an opinion on something happening in your field, a resource you found useful — give people a sense of how you think, which is often more useful to a potential connection than your job history alone. This is really one instance of the broader practice of building a personal brand online: having a visible, consistent sense of what you know and care about, so that the people you interact with have something to go on beyond a title and a company name.
What’s actually wrong with only reaching out when you need something?
This deserves to be named plainly because it’s the pattern almost everyone falls into without meaning to. Reaching out only when you need something — a job lead, a reference, an introduction — is detectable. People notice when the only messages they get from someone arrive attached to a request, and they notice the absence of any contact in between. It doesn’t take a particularly perceptive person to register the pattern after it happens once or twice.
It also puts the other person in an awkward position. They’re being asked to spend effort or use their own credibility on your behalf, from someone who hasn’t shown up in any other context. Saying yes feels like an obligation rather than something they want to do. Saying no feels uncomfortable given the personal nature of the ask. Neither position is one you want to put someone in, and neither produces the kind of enthusiastic help that actually moves things forward.
And it burns whatever light relationship existed. Even a thin connection — someone who vaguely remembers you from a shared project years back — gets used up by a purely transactional ask with nothing behind it. If you ever want to reach out to that person again, you’re starting from a worse position than before.
The honest fix here isn’t a better way to phrase the transactional ask, or a trick for making a cold request land warmer than it is. There isn’t one. The fix is starting the ongoing version of networking earlier — before you need anything — so that by the time you do need something, it isn’t the first contact in years.
What about people you already know but have lost touch with?
This is usually the highest-value, lowest-effort part of a network, and it’s the part people neglect most, because it doesn’t feel urgent the way meeting new people does. Former colleagues, people from past roles, classmates, people you worked alongside briefly on a specific project — these are people who already have real context on you. They don’t need to be convinced you’re worth talking to. They already know.
Staying in touch with this group doesn’t require much. An occasional message when you see something relevant to them, a congratulations on a role change, a check-in with no agenda attached. It’s a fraction of the effort required to build a relationship with a stranger from nothing, and the resulting relationship tends to be more durable, because it’s built on actual shared experience rather than a few exchanged messages.
Before spending significant effort trying to build new connections with strangers, it’s worth going through your existing network and reconnecting, lightly and without an agenda, with the people who already know you. This alone often does more for the actual usefulness of your network than any amount of new outreach.
What does “give before you ask” actually mean in practice?
It’s a phrase that gets said often enough to become a platitude, but the practice behind it is real and specific: share something useful to a particular person, unprompted, with no ask attached. An article that’s directly relevant to a problem they mentioned. An introduction to someone else in your network who could genuinely help them with something. A piece of information you happen to have that saves them time or effort.
The key word is unprompted. This isn’t a favor done in anticipation of one being returned, and it shouldn’t be framed or timed that way. It’s simply useful, offered because it’s useful, with nothing attached. This builds real goodwill in a way a cold ask never does, because it demonstrates — rather than states — that you’re paying attention to what someone actually needs, and that you’re willing to spend effort on their behalf before there’s anything in it for you.
You don’t need to do this constantly or for everyone. A handful of genuine instances of this, spread across the people in your network over time, does more for how you’re perceived than a much larger volume of requests ever will.
How do you keep a relationship going after the first conversation?
One conversation, however good, rarely becomes a real professional relationship on its own. Relationships are built cumulatively, through repeated light contact over time, not through a single well-executed interaction. A great first call that’s never followed by anything else fades into a name you vaguely recognize a year later, which is close to where you started.
Occasional, genuine check-ins are what actually sustain this. Not a scheduled cadence of touching base for its own sake, but real moments — something happened that relates to a conversation you had, you saw news about their company or role, you have an update on something you discussed. These don’t need to be frequent. They need to be real, and they need to happen more than once.
This is the same underlying discipline as the engagement described earlier — showing up with something genuine rather than something performative — applied over the longer arc of an actual relationship instead of a single post or message.
What should you honestly expect from this?
This is slow. It’s cumulative, in the same way most relationship-building in any part of life is cumulative — a scattering of genuine, low-effort interactions over months and years, most of which don’t lead anywhere identifiable on their own, adding up eventually into a network of people who actually know who you are and are inclined to help when asked.
Expecting fast results from an occasional post or a handful of connection requests misunderstands what actually builds a network. A single well-written post won’t produce a job offer. A few thoughtfully worded connection requests won’t produce a referral by next week. What produces those things is the accumulation, over time, of a lot of small, genuine interactions that eventually mean there’s a real relationship in place by the time you need to draw on it.
The uncomfortable version of this is that if your network is cold right now, there’s no shortcut back to warm. The only fix is starting the ongoing version of this today, not scrambling to compress two years of relationship-building into two weeks of urgent outreach. Start now, expect it to be slow, and the next time you need something, the network will actually be there.
The National Careers Service offers free advice on the wider job search this sits inside.
Frequently Asked Questions
How often should I post to keep my network engaged?
There’s no fixed number that works for everyone. What matters more than frequency is that there’s some ongoing signal of what you think and know, rather than total silence for years at a time. A post every few weeks, done with actual substance, does more than a rigid daily schedule of low-effort updates.
Is it okay to reconnect with someone I haven’t spoken to in years?
Yes, and it’s usually easier than it feels. A short, genuine message acknowledging the gap and mentioning something specific — a shared memory, something relevant you saw about their work — tends to be well received. What doesn’t land well is reaching out after years of silence with an immediate ask attached and nothing else.
Should I connect with people I’ve never met in person?
That’s fine, as long as the connection request names a real, specific reason for reaching out. The relationship doesn’t need to start in person. It needs to start with a genuine reason rather than a blank request.
What if someone doesn’t respond to my connection request or message?
It happens often and usually isn’t personal. People are busy, messages get buried, and not every reasonable request gets a response. One follow-up after a reasonable gap is fine. Beyond that, it’s better to let it go than to send repeated messages, which tends to have the opposite of the intended effect.
How do I network if I genuinely don’t enjoy self-promotion?
Most of what’s described here isn’t self-promotion. Commenting thoughtfully on someone else’s work, asking a specific question in a conversation, following up after a call, sharing something useful unprompted — none of that requires promoting yourself. The version of networking that feels uncomfortable to most people is usually the transactional version, not the genuine one.
How long does it actually take to build a useful professional network this way?
There’s no fixed timeline, and it depends heavily on how consistently you keep at it. What’s consistent is that it’s measured in months and years, not weeks, and that it depends on starting before you urgently need it rather than after.