First up is John Liebhardt, JohnLiebhardt.com
"The Lean Startup" book - three tenets:
Design products and services that people want to use
Tweak to make the products and services better
Use data to understand how well you're doing
Get customer feedback fast.
build -> measure -> learn
Creativity is required.
"Creative Competence" book by IDEO
Is it technically feasible?
Is it feasible from a business sense?
Does it have people sense? Do people really want it? <- customers="" p="" want.="" what="" your="">
Organizations need to empathize with user needs.
Patron needs: connecting the dots
Some people don't have the vocabulary to describe their needs.
Create an 80% solution and use that to get customer feedback. Then make changes or improvements. Need to test your assumptions. Test customer behaviors. Do a controlled test, so that you understand the impact of your service/product.
Make sure that you can capture data about the new product and service. You will need to decide your assessment criteria in advance.
James Stephens (next speaker) talking about his experience in moving ideas forward. His specific example was around a technical implementation.
First, identify a problem that you need to solve. Find the problem first. Don't find the solution first (that is in search of a problem).
Used a Raspberry Pi kiosk to provide information on room reserves...providing information at the point of need.
Second, do research.
Is the idea possible?
Is the idea feasible?
Is the idea practical?
Third, Next what decisions need to be made?
Fourth, what approvals do you need?
Rethinking - what can I do that is better than what is occurring now?
Implementing quickly allows you to see the problems that you're going to run into. How do you mitigate those problems?
Interesting that Raspberry Pis have inherent problems, but those problems can be overcome. This is a place where people should look to their network (or the CILDC network) for help.
One lesson that Stephens learned is to have lots of backups.
Question - does the hardware exist that you need? Do you need to modify what's available? Should you create a custom solution?
Wait...are you really pursuing the right solution? Always good to check.