The best product feedback sometimes sounds like a complaint. “Why do I have to do this?” That's not just frustration. It's a clue.

You don't need every day to produce a breakthrough. Some days the win is simply understanding the problem a little better than you did yesterday.

One underrated advantage of talking to users regularly: You start noticing the words they use without having to think about it. Those words are often better copy than anything you could invent.

What's a product you think became worse because it tried to serve too many different types of users? Sometimes expansion creates more complexity than value.

A lot of founders ask whether an idea is “big enough.” I'd also ask whether the problem is specific enough to understand deeply.

The smaller the product, the harder it is to hide behind complexity. That's not a weakness. It's a pretty good forcing function.

Sometimes you don't need better marketing. You need a product that gives people a sentence worth repeating to someone else.

One of the hardest founder habits to develop: Stopping yourself from solving problems nobody has actually complained about.

What's a product you keep paying for even though you only use one or two of its features? There's probably a lesson in why those features are enough.

A product doesn't need to impress someone on day one. It needs to give them a reason to come back on day two.

Building in public has made one thing very obvious to me: People are often more interested in why you're making a decision than in the decision itself.

There's a difference between solving a problem once and solving it repeatedly. The second one is where a business starts getting interesting.

What's something you bought that genuinely changed your daily routine? Not something you liked. Something that actually changed what you do.

A small product with a clear purpose is easier to explain, easier to improve, and usually easier to remember. Clarity compounds.

I've noticed that building gets easier when you separate “interesting” from “important.” A feature can be fascinating to build and still be completely unnecessary.

What's a task you still do manually even though you know there has to be a better way? Those are the problems I find most interesting.