Yes, we are meeting tonight at 5:30 - minus Dani and Andres :-(.
We should use tonight to discuss how we want to organize ourselves, assign tasks, and measure results.
I've been reading the book
The Lean Startup, and I am a big fan of
those methods. I would propose we use that as a framework to define the "validated learning" that we want to do as our top priority.
We want to get into a "Build" - "Measure" - "Learn" loop. We have some leap-of-faith assumptions right now that we need to validate:
- Homeless people will ask for donations via QR Code.
- Homeless people will share some personal information with strangers in order to promote donations.
- Donors will give to homeless people (or their sponsoring organizations) via a QR-Code phone donation.
-
Partner organizations will provision homeless people with StreetCodes accounts, profiles and kits.
- Partner organizations will fulfill the donated items to the homeless that donors have purchased.
These are all questions beyond our control (no amount of efficient execution or progress on are part can change the answers). But if any of them are not true - our original idea will not succeed. The thing that Eric Ries's book has impressed on me, is that you can't find out the answers to these questions, generally, by just asking people. You have to created a controlled "experiment", where you present the person the opportunity to either accept or reject the offer you give them. You can then measure how true each of the assumptions are (if 50% of donors are willing to donate via QR-Code, we could still have a successful launch).
The essence of the Lean Startup is the Minimum Viable Product - it is our job to build the smallest possible experiment (product/service), that can answer each of these questions. So, for example, we need not ACTUALLY IMPLEMENT a payment system to know if people click on a "donate" button, and complete the form "as if" they were about to donate money.
I would propose the way we set our goals and priorities, is to identify the most critical untested assumptions we rely on, and then make it our goal to find out if they are "true". We will then incrementally, and smartly work our way toward a successful product that will grow to fill a need in available markets around the country (and world).
See you tonight!
P.S. Call the office phone if the front door is locked and I'll come down to let you in - it should be open until 6pm.
Mike Koss
StartPad.org
Seattle Software Development Offices
(206) 388-3466Twitter: @mckoss @startpad