Saved by phoebe and
Too many understand quality as polish. It's not the same thing.
If build something good, even if it’s a bit rough. That’s great. But don’t fall into the mindset of “just ship it.”
When “just ship it” is the default, you stop asking if this is actually good for users. You move
Karri Saarinenx.comOur “small giants” approach optimized for mojo over growth. We wanted a small, talent-dense team with a focus on craft, autonomy, and quality of life for all team members. We banished the term “founder” in favor of “partner” and tried to be transparent with all business matters across the team.
We took some capital from investors in order to invest ... See more
We took some capital from investors in order to invest ... See more
Muse Retrospective
I think most companies start to explicitly encode and articulate their principles or values too late. I would try to produce a provisional revision literally when you’re just a handful of people. Then continue to update it on an ongoing basis, because assuredly there will be things you realize or come to appreciate are wrong over the course of the ... See more
Elad Gil • An interview with Patrick Collison – High Growth Handbook
I understand the argument for shipping early and often. But I also believe that we should aspire to build lovable products, not viable products. And lovable products take time to build and polish.
the startupy newsletter • Things I'm Thinking About
The prevailing dogma is that startups should ship and iterate as quickly as possible. Scott believes that’s often counterproductive. You need to “surprise and delight” your customers to create a product that grows organically. You can’t do that by simply meeting a user’s expectations; you must surpass them. Doing so takes time and polishing.