Clear why beats detailed how

If everyone has an understanding of why we're doing this, what problem we're solving, then people can make really great decisions. It's the only way you can really scale.

The biggest one I think is, the founder becomes too tactical and disempowers their team. I think the founder thinks they know what customers want and they basically just tell the engineers what to build.

We get a lot of requests for features and a lot of them are basically about opinions, some way to record opinions. We're not going to do those.

One of the things I think that happens is when you build a team and you start creating these very specific roles for everything I think that often the PM can be the ones figuring things out and making decisions and guiding the team, but they're not the ones building the feature. They're not there looking at it the whole day like where does this button go or how does it work?