This session provided an interesting comparison and contrast of start-up businesses and libraries. In the list below, the first option is what libraries typically do, and the second option is what start-ups do:
Test the product vs. test the problem (find the problem first before determining solution, and ask is it worth solving?) Example - Library catalog – what are people trying to do or solve? What do they use instead?
Stay in the building vs. get out of the building. Example - User services review. Who’s not coming in? How are they solving information problems outside library? Check with extreme users and with non-users.
Build it and they will come vs. build it when they come (try on small scale first to make sure there's a demand)
Build for the many vs. build for the few. Not all services need to be for everyone. Smaller groups w/shared needs are easier to define and address.
Learn then build vs. build then learn. Put up quickly then learn from mistakes, rather than doing elaborate study beforehand, building and then never adjusting afterwards.
Pilot projects vs. iterative design. Example – streaming video service. Startups better at killing unneeded projects than libraries. Start with minimum viable project (MVP), which is faster to market and cheaper, and only develop services that are needed.
Collect all data vs. use key data. Don't get lost in too much data that's not meaningfully differentiated. Dashboarding can track key metrics in a transparent fashion.
Execute the plan vs. adjust the model. Be flexible enough to make course corrections as needed.
Focus on features vs. focus on value. Example – for instruction workshops, answer the question why should I take the workshop?
Also important to start-ups is the pitch – a concise and convincing summary which communicates value and concludes with a call to action.
- Understand the problem
- Validate the solution
- Communicate the value proposition
- Compel the listener
No comments:
Post a Comment