Feedback isn't noise,it’s a blueprint. Building ZERO in public meant letting our community tear apart our early hardware prototypes. It takes a thick skin, but co-creation beats guessing every single time. This series is wrapped, but the next chapter is massive. Stay tuned. 🚀

Stop over-engineering your startup's community. If your Discord or forum has 40 channels and a 10-page rulebook, you’re killing engagement before it starts. Keep onboarding dead simple. Lower the barrier to entry, welcome people instantly, and let the culture scale naturally.

Talking features first is the fastest way to kill interest in your product. No one cares about your specs or your engineering bay tolerances. They care about their own pain. Pitch the problem you solve first. The features are just the proof that your solution works.

5 brutal lessons learned from failing (and eventually succeeding) at building ZERO's community: 1/ Broadcasting kills engagement. 2/ Friends =/= early adopters. 3/ Target obsessions, not demographics. 4/ Gamify the experience. 5/Friction is fuel.

Our 2nd community attempt failed because we relied on friends. They wanted to help, so they broadcasted for us...sharing links and hyping us up. But they didn't engage with the product.Supportive friends =/= early adopters. You need strangers who actually need your tech.

The harsh truth of launching a product: Nobody cares at the beginning. When we started ZERO, the silence was deafening. No one is waiting for your hardware. You have to earn every single user brick by brick. If you can't survive the initial ghost town, don't build a startup.

I learnt in 1 hour more than I would expect by interviewing @saketaram a great episode coming soon!