4 ms·
Is it really broken for the users or broken is your definition of broken because that's your baby and your dreams etc etc etc? If this 25% working part represen
by caio1982 12y ago
Is it really broken for the users or broken is your definition of broken because that's your baby and your dreams etc etc etc? If this 25% working part represents something that users could actually use, and you are all under pressure (for whatever reason), than ship it but ship it with a plan. E.g. let the users know what's missing and what's your plan to ship the rest of the service, and possibly show them a milestones timeline so they see this is not the crappy final version of the whole thing and that you are working hard on the other 75%. That will also help with the thing about your investors by the way, I guess. Of course, that's only a very personal opinion. I have never shipped a service or product like that but as a paying user/customer I would appreciate this approach.
- flounderfounder 12y ago>Is it really broken for the users or broken is your definition of broken because that's your baby and your dreams etc etc etc? That is a part of it certainly but when we are doing our unit tests about 1/2 to 3/4 of the time the service doesn't do what it should and the user has to reload all their data from scratch (takes about 15-20 minutes). >let the users know what's missing and what's your plan to ship the rest of the service, and possibly show them a milestones timeline so they see this is not the crappy final version of the whole thing and that you are working hard on the other 75%. I like that approach - largely because all of our first customers have been really enthusiastic and engaged in the product development. Thanks.