2 ms·
Maybe. Maybe a feature-rich but rough and unpolished prototype is what will delight customers the most. Or maybe focusing on an absolutely minimal core, but ex
by kqr 6y ago
Maybe. Maybe a feature-rich but rough and unpolished prototype is what will delight customers the most.
Or maybe focusing on an absolutely minimal core, but executing it really well with high performance and having it run rock-solidly will attract the potential customers more.
I think this depends a lot on demographics, but in broad strokes, I think the former is overvalued compared to the latter. I.e. contrary to your experience!
- ralphstodomingo 6y agoI would be inclined to agree except people generally have low standards of performance (ofc depending on the industry!). People also rarely care about the hand of the puppeteer, what keeps the lights on parts especially if we're talking about a prototype.
- kqr 6y agoI think people care a great deal more than they have words to express. We're not very good at educating our customers in ways to discuss and analyse technical performance. We're getting better at it when it comes to uptime, but latency discussions still lag (hah!) behind. (This is from purely personal experience. I have only had one customer ever, when asked about performance requirements, who could list some. Everyone else has been "I guess I want it to be... good?")
- gridlockd 6y agoThe prototype serves to figure out what the customer does not need as much as what they do need. Polishing the wrong thing is a waste of time.