you know what they say about assuming.....soo validate 'em
3 ปีที่แล้ว
I have a question: How do you decide if it is risky or not? I don't understand why it is risky and easy to validate "want to meditate", "use phone to meditate". I mean, I understand it is easy to validate but why is it risky? Thank you in advance :)
One example would be sinking a ton of time time into developing a feature (that's the risk) when it turns out no one would use it (that's if its unvalidated). Perhaps a low risk assumption would be feature that is very basic to the app that everyone knows and agrees is needed and there is some peripheral proof that it would be used/desired.
3 ปีที่แล้ว +1
@@bweb778 Thank you so much, Yeah I see it now. :)
you know what they say about assuming.....soo validate 'em
I have a question: How do you decide if it is risky or not? I don't understand why it is risky and easy to validate "want to meditate", "use phone to meditate". I mean, I understand it is easy to validate but why is it risky? Thank you in advance :)
One example would be sinking a ton of time time into developing a feature (that's the risk) when it turns out no one would use it (that's if its unvalidated). Perhaps a low risk assumption would be feature that is very basic to the app that everyone knows and agrees is needed and there is some peripheral proof that it would be used/desired.
@@bweb778 Thank you so much, Yeah I see it now. :)
Is there anyone who tried this with and can share his/her experience with it?