Reid Anderson

Someone used our product for about five minutes and wrote a short, calm message explaining what they were trying to do and why our approach didn't fit. No feature request, no complaint, no suggestion. Just a clear "not a match." It did more for our direction than a year of "looks cool" and "nice idea." It made us realize we'd been sanding the product down to accommodate people who were never going to stay, while the people who actually needed it got a diluted version. The rejection was honest, and honesty is rarer than praise. How do you tell the difference between a user who's wrong for the product and a user who's telling you the product is wrong?

A while back, I threw together a tiny script in a couple of hours just to fix a small personal annoyance. No long-term plan, no roadmap. Years later, it s still running, and I still get occasional emails from strangers using it. Meanwhile, the bigger startup ideas I spent months planning with actual business models ended up going nowhere. It taught me that you really can't guess what will resonate until you just put stuff out there. Have you ever had a tiny weekend build outlive your actual planned projects?

I used to keep my chat apps open all day replying to every ping within five minutes because I thought it showed dedication.

All it really did was chop my day into tiny useless pieces where I couldn't focus on anything meaningful. The day I started batching my replies to just twice a day my anxiety dropped and I actually finished things on time. Nobody got mad and the world didn't end.

How do you manage your communication loops without letting constant notifications wreck your focus?