Crafting first products with key philosophies
In today's fast-paced market, the expectation for first product versions has evolved. This discussion explores the importance of focusing on key philosophies rather than releasing subpar initial versions. Emphasising consumer-friendly features can set a product apart and buy time for further development.
Key takeaways
- Avoid shipping truly embarrassing first versions.
- Focus on key philosophies for initial product launches.
- Consumer-friendly features can differentiate your product.
Topics
- Product Development
- User Experience
- Innovation
Transcript
Absolutely. Yeah, yeah. I think there's an interesting, I saw an interesting tweet the other day which said, like, the days of, like, you know, ship your first crappy, embarrassing product are over. And I sort of agree. I kind of think that actually no one really should ship anything truly embarrassing. I think the tolerance for, like, terrible first versions is pretty low because, I mean, like, really life's too short to just be testing out terrible products and have them kind of fail on you. So I think that was a bit of an old trope. But what I think, how I think it really should be at the moment is that you should probably hang your first product on a couple of these key philosophies. So, you know, what I was talking about there was we worked with consumer hardware. It's really nice and intuitive interface, and it has this real-time magic moment. And then, to be honest, the fact it didn't support vertical screens, didn't support, like, zones, it was only full screen, and all of that other stuff, which was kind of table stakes, didn't even work offline originally, which is quite important in that environment. But all of that stuff was, like, to be added, and people were, like, fine with that because they could see that your product philosophy stood out as something slightly different. So that bought you the time. At that point, apart from them saying, you need to do the table stakes of work, which everyone just kind of usually intuitively knows, then you start getting that feedback loop.