6 ms·
>Your friend’s terrible prototype is worth 100x more than your great idea. >Why? Because your friend actually did something with their idea. They created somet
by duxup 5y ago
>Your friend’s terrible prototype is worth 100x more than your great idea.
>Why? Because your friend actually did something with their idea. They created something. It may be terrible, but at least it exists. They’re now informed about how to proceed based on something real, something tangible.
I recall an article (or maybe it was a comment) posted on HN about someone who was very engineering focused about their start up. They focused heavily on code quality and product quality. Their product was said to be rock solid.
They had a good thing going in a space they believed would be huge.
Then over a few months a competitor showed up with a janky / flaky product and took all their customers. This new competitor output new features left and right, they often didn't work well, but they existed (unlike the startup in question).
It janky product, it was Salesforce.
Finding that 'executed well' in this case was getting features out the door.
"Executed well" could just be a matter of recognizing "right now we need to get these features out the door". How / when ... who knows how you figure that out.
- MattGaiser 5y agoThat and customers don't seem to care about bugs either. We have reached the point where buggy, glitchy software is considered the norm.
- duxup 5y agoI also think customers ... many are picking buggy products or not caring about quality, possibly for good reasons. They want to do their job already. Granted I have my experience with plenty of customers who really are making random decisions, but I'm constantly surprised how often I'll review some feature limits with a customer and they're all "yeah we'll need those". But then we'll give them a beta without those features, it's kinda buggy..... and they love it. The quality and utility ratios are a spectrum and finding those for a given widget is an unknown for me.
- MattGaiser 5y agoTrue. Crap now is better than a good product later. And I don't have customers, but deal with this with my product manager. He just won't stop adding stuff to the backlog.
- whymauri 5y ago>"Executed well" could just be a matter of recognizing "right now we need to get these features out the door". How / when ... who knows how you figure that out. Product-market fit and feature velocity is like 50+% of the execution advantage of startups.
- duxup 5y agoYeah I've spent weeks on a project, it goes semi unused despite lots of attention from customers. A few hours on widget ... suddenly customers grapple onto this simple widget as a big reason to buy. Who knows how you figure that out...
- cornel_io 5y agoIt's also why companies like Google can't effectively develop new products as a rule: they have internal processes, people, and cultures that support keeping a mission-critical money-printing machine running perfectly smoothly at all times with as close to zero defects as they can possibly come. It's really hard to flip all that human and technical infrastructure into a mode where you're cranking out half-busted features as fast as possible just to see what sticks with your customers, code quality be damned, sell-first-fix-later style. "Worse is better" is something big companies can't do very well, and it's why they usually end up buying their innovations from the small companies that still can (until they're fully swallowed up and lose the ability to innovate, too, at which point there are always more startups to buy!).