Content
@
1 reply
0 recast
2 reactions
rish
@rish
(since I put my preferences out there, only fair that I put more such content in this channel) Here is something I believe in + recommend: Avoid "champagne problems" - problems that arise after customers use your product enough. _what happens if we get 100 users and don't have a glasses for the celebratory champagne? let's get the glasses first so we are ready_ this is the same as: - what if our server can't scale to N requests/min? No need to solve that till your product is at N rpm. - customers will immediately ask for feature Y after trying feature X. Yes probably, get them to try X and care enough to ask for Y. Musk is iterating on rockets that go to space. Iteration works. Do not get champagne glasses, just launch. https://warpcast.com/rish/0x10585304
9 replies
15 recasts
55 reactions
matt 💭
@matthewmorek
the counterpoint (or maybe a tradeoff in this case) might be that you have only one shot at making the first impression if you launch but your service constantly fails or your product is of subpar quality, only your biggest fans will have the stomach to tolerate this until you fix it, especially in a competitive market it’s way easier when you’re the first mover, because the tolerance is higher i think we’re blessed by all being somewhat in the first-movers market here, but we shouldn’t be blind to the flip-side
1 reply
0 recast
0 reaction
rish
@rish
Your response confuses quality with scope, I’m speaking to scope High quality is great as long as scope is small One customer won’t know the difference between 60 RPM and 1000 RPM (in most cases) 60 high quality responses will still do what you’re pointing out, quality is a whole different debate
0 reply
0 recast
1 reaction
