Three of us are building a startup and we are trying to validate a bunch of assumptions. We have an MVP in place, set up Mixpanel and have some custom-built tracking set up, so we can measure everything we want based on these assumptions.<p>However, we are having a hard time stating our goals and expectations that should come from these assumptions. In the Lean Startup, Eric Ries talks about Kodak. They were building an event photo album creator and wanted to validate if people want to create photo albums at all. They concluded that people wanted to do this, but what amount of data did they look at?<p>In general, how much data do you need to be able to make conclusions out of assumptions? When are you satisfied with the results and how do you decide to pivot or persevere?<p>I realize this is very subjective, but I was wondering if someone has some insights into this. Thanks!
I think that's pretty hard to answer shortly, but suppose you found out that from all your users, 70% of them created albums and played with it when you released that feature. Obviously this is something they want. When that percentage is lower but still significant it can be hard to tell, if that's what you mean. But then I think it depends a lot, it's very subjective indeed!