Kill Your Own Darlings Before Someone Else Does

We spend a lot of time talking about communication in startup communities. The newsletter. The Slack updates. The meetup events. The carefully worded email announcing the new accelerator. Awareness is so important that we broadcast in as many vehicles as we can manage. We are so proud of the darlings that we worked so hard to produce.

That's all output. And output is only half the job.

The other half is listening. Feedback. Making sure the signal runs both ways. And that's the half most of us community leaders skip. You see, we think to ourselves, we did all the work we are supposed to do. We talked to other builders. We attended one of the startup community conferences. We have read the books and the newsletters.

Here's why that matters more than you think. Startup communities aren't static. Founders change. Funders change. What worked three years ago quietly stops working, and nobody sends a memo when it happens. It just fades. The event that used to pack the room now draws only 12 people and 2 boxes of cold pizza. The program you built with real care becomes furniture. Everyone's used to it being there. Nobody's getting much out of it anymore.

So here's the question I want you to sit with: how open are you to hearing that your baby grew up and isn't relevant anymore?

I ask because I've built things I was proud of. Programs, events, whole initiatives. And I've watched some of them outlive their usefulness while I kept defending them, because I built them, they used to work, and surely they still mattered. That's not stubbornness. That's just what happens when you stop listening for the feedback.

Real two-way communication means creating space for people to tell you something isn't working, and then actually believing them when they do. It means asking founders what they need instead of announcing what you're offering. It means noticing when attendance drops and getting curious instead of defensive. It means treating "this doesn't serve me anymore" as useful information rather than an attack on your legacy.

This is uncomfortable, because most of us built our identity around the thing we made. Killing a program can feel like killing a piece of yourself. But community leadership isn't about protecting what you built. It's about staying useful to the people you built it for, even when that means admitting the thing you're proud of has run its course.

The best community builders I know aren't the ones with the loudest newsletter. They're the ones who ask a lot of questions and actually change course based on the answers. They treat feedback as data, not criticism. They kill their own darlings before someone has to tell them to.

So next time you're drafting the update, the announcement, the pitch for what's next, pause first. Ask somebody what they actually think. Then do the hard part: listen like you mean it, even if what you hear is that your baby's all grown up and doesn't need you the way it used to.

That's communication. Not the talking part. The other part.