![[Home]](http://www.bayleshanks.com/cartoonbayle.png)
assumptions why? how? what? where?,when? who last, so that by the time you get to it your target market is narrowed
first, test assumptions, before introducing your product
ask potential users:
gut reaction
other competitors what u like what u hate
how much would you take if we gave it to you for free?
take user reaction with a grain of salt
if user reactions don't make sense, then go back to assumption stage; some of your assumptions were wrong do post-mortem
persistence: some older cagier clients will always say no the right time
prototype vs. MVP?
prototype is thrown away when done, MVP is something you're sticking with MVP: "minimal viable product" implement core features only alpha testing talkative, representative of core markets test usefulness of experience (not UI testing! does the product serve its function? are our assumptions correct? does it work? will ppl pay what we think?) qualitative analysis; quantitative is for beta -- at this point, check that: ppl like our idea / experience find the experience to be useful our assumptions have been reasonably tested -- if so, mb start: biz planning formal UI design branding beta testing
if you can get feedback from the same group of alpha testers outside your product over the whole lifecycle of your product, that's super valuable also, it'll be that much easier to launch
don't drink the kool-aid (great picture of kool-aid guy saying, "oh, yeaahh!"
prepare for surprises
maintain 30000 foot view does the app make the users happy? do they think it's worth more than they invested in it?
aaron stannard stannarlabs.com, @Aaronontheweb aaronstannard.com
san diego networking groups when you meet someone here, you may want to ask them: do you know anyone i could talk to? would you write him an email and tell him i'm going to call?
SCORE
startuptech sd tech scene
