Subscribe
Sign in
What aspects of your product must be perfect before you would release it?
Launching a product, especially in the tech space requires diligent balance between perfection and timelines!
With this discussion, I’m trying to understand the difference in how people approach releasing to the public and how that correlates with your products strategy.
It’s an exploration into the philosophy of “done is better then perfect” versus ensuring impeccable quality in certain product aspects before introducing it to the market.
How do you approach this?
16
Replies
Best
@maxjacobs does the user know how to install the API? Does he know all the functionalities of the API and how to best use them?
I would start there. Clear and concise communication 👍🏻
@visionoiry Let’s say you have to leave something not done, what would it be, what would you feather be left for last?
@maxjacobs it could be something from minor features. I believe the key features and design need to be perfect. Assuming that design can ever be perfect ))
When basic features work... best advice I got is well you will have hundreds of releases.. Simply question do you know when Zoom, Spotify, Gmail released probably not... You can probably pinpoint when you started to use them yourself after 1000 iterations and probably another 100 re-launches.
You should have a vision in your head what the end product features look like but that shouldn't stop you if not all of them in there.
