This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.

Management & Leadership

Networking as an entrepreneur

I was asked at a recent startup event what I thought about networking.

I am not a fan of the concept of networking. I don’t have a LinkedIn account. I don’t score myself on how many people I know or how big my stack of business cards is. I don’t usually even carry my own cards, and when I do, they have just name and contact info on them, leaving off titles and anything else someone might use to add me to their network trophy case. When I go to an event, I don’t try and talk to as many people as possible, flitting from conversation to conversation, just so I can boost my connection count. I find it obnoxious when people fill their Twitter bio with hashtags like "#entreprenuer and startup #mentor" or focus on "power networking" techniques like follow-back policies.

Networking is useless, because it’s superficial. You may have 1000 business connections, but how many of them will jump to help you out, or even remember who you are?

Having a network is crazy important. Networking is not.

The difference is a network is an authentic thing. It’s the people that you have legitimately connected with that you have talked to and formed a relationship with over time. A network is not "how many business cards I collect at the mixer on Tuesday night." It’s not going to events and meeting as many people as I can. It’s developing deep, meaningful relationships with people without knowing how those relationships are going to turn out. A real network isn’t built by thinking about how the connections are going to benefit you. Building a network means making sure that you are providing more value to the other person that you’re getting from them. It’s constantly giving, constantly being involved, constantly making sure that you are helping them. Eventually something will come up where they’re going to help you, not because you connected with them, but because you have a relationship with them.

Recently Written

Your OKR Cascade is Breaking Your Strategy
Aug 1: Most companies cascade OKRs down their org chart thinking it creates alignment. Instead, it fragments strategy and marginalizes supporting teams. Here's what works better than the waterfall approach.
Your Prioritization Problem Is a Strategy Problem
Jul 23: Most teams struggle with prioritization because they're trying to optimize for everything at once. The real problem isn't having too many options—it's not having a clear strategy to choose between them. Without strategy, every decision feels equally important. With strategy, most decisions become obvious.
Behind schedule
Jul 21: Your team is 6 weeks late and still missing features. The solution isn't working harder—it's accepting that your deadlines were fake all along. Ship what you have. Cut ruthlessly. Stop letting "one more day" turn into one more month.
VC’s Future Lies In Building Winners
Jun 21: AI and megafunds are about to kill the traditional venture model, forcing smaller VCs to stop hunting for hidden gems and start rolling up their sleeves to fix broken companies instead.
Should individual people have OKRs?
May 14: A good OKR describes and measures an outcome, but it can be challenging to create an outcome-focused OKR for an individual.
10 OKR traps and how to avoid them
May 8: I’ve helped lots of teams implement OKRs or fix a broken OKR process. Here are the 10 most common problems I see, and what to do instead.
AI is Smart, But Wisdom Requires Judgement
May 3: AI can process data at lightning speed, but wisdom comes from human judgment—picking the best imperfect option when facts alone don’t point the way.
Decoding Product Leadership Titles
Mar 18: Not all product leadership titles mean what they sound like. ‘Head of Product’ can mean anything from a senior PM to a true VP. Here’s how to tell the difference.

Older...

What I'm Reading