Startup Weekends attract a wide range of participants, including innovators and inventors who may be unfamiliar with the “lean startup” approach to creating a business that SW advocates. Boston EDU Startup Weekend shared this great primer that will give you a grounding in the concepts and language you’ll see at Startup Weekend Lehigh Valley. We’ll also be sharing some definitive readings as the Weekend approaches.
Lean startup model: Eric Reis turned his blog into a recently published book, The Lean Startup, which was #2 on the New York Times Bestsellers list. (Inc. Magazine featured a condensed version of Reis’s book if you want further reading. Essentially, Reis developed a business model that encourages startups to find out as quickly as possible whether or not the business idea/product/service is viable. The path to achieving this learning is to create a rough version of your product that goes into a cycle of testing, iterating, testing, iterating, testing, and iterating until the product is viable. An important part of this process is early and frequentcustomer validation. The lean startup model came out of a concept in manufacturing where small batches are created so that there is minimal loss of time and money if the market isn’t interested in that version of the product. The same lean process works well applied to technology too. When creating a web-based tool or an app, you can create a mockup to garner feedback without building the actual product or feature, for example. (I love Balsamiq for this!)
Minimally viable product or MVP: This is not the same as a prototype! In the Lean Startup model, the goal is to create and test the smallest piece of a business to see if there’s a market for it. Reis defines the MVP as “that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.” Essentially, you’re looking for the minimum set of features needed to learn from your early adopters because you want to learn early what users want and don’t want. It limits spending time and energy on products that no one really wants. Most teams try to develop a minimally viable product during a startup weekend, not the whole business. It looks great to judges if you’re able to validate your idea/product during the weekend. You may be asking, but how do I do that?
Customer validation or validated learning: There are a number of ways to learn about your customers and what they like and don’t like about your product/service. There’s also a big difference between what someone might say they like and what they’re willing to buy or do. The best validation is showing that customers/users will in fact want your product/service and be willing to pay for it.
You first want to see if there’s any interest. For example, if you already have a free product but are curious if people would pay for some additional features, you could add a button to your site that advertises the new version (which you haven’t built yet!). If a number of users click the button, then you have begun validating that customers are interested. If no one clicks, then all you’ve wasted is the time to develop the concept—you haven’t spent excessive money and time on something no one wants.
During a Startup Weekend, you’re likely to focus on establishing general interest in your product or service, and if you’re lucky, getting some users to act. There’s not a lot of time to build significant traction. One way to establish initial interest is to create a landing page.
Landing page: To test the viability of an idea, a single webpage is sometimes created to see if anyone will sign up for the product/service. There are several pre-built free pages out there. I’ve used and liked KickoffLabs and LaunchRock. Ooomf creates landing pages for mobile devices. What’s great about these programs is that they provide data: how many times the page was visited, how many visitors were unique, how many actually signed up. (There are some great programs with more bells and whistles for when your business grows and you need to track more complex user actions. At LessonCast (www.lessoncast.org), we use MailChimp (mailchimp.com)).
Here’s an example: I joined the team TeenStarter (TeenStarter.com) at Startup Weekend EDU in Seattle . The concept for this youth-only site was to provide both advice on creating a business (how to pitch, how to develop an idea, how to market) and to provide a platform for students to pitch their ideas to get seed funding (micro-financing for teens). Our hypothesis was that a student would post a video pitch and then use social media to send it out to his or her network. Friends of friends might also contribute, until the student received the money he or she needed to launch a business or community project.
Here are the steps we took to validate the concept that weekend:
- We created a landing page and used social media to blast to contacts of everyone on the team. (KickoffLabs showed 73 unique views and 17 users signed up.)
- Again using social media, our team sent out a request for any teenagers who had an idea to pitch. (One 13-year-old relative of a team member uploaded a video late Saturday night!)
- Once we had the site minimally functional, we posted the teenager’s video pitch and at uploaded a PayPal donate button. (Our featured teenager needed $60; $40 was raised before final pitches on Sunday night. She had the rest the next day!)
For a Startup Weekend, this exercise demonstrated a good conversion rate, and was a fairly solid proof of concept!
Conversion rate: It’s one thing to get users to your site; it’s quite another thing altogether to get them to act/buy/participate. For example, if you send out an email directing folks to a landing page, the first conversion rate will be how many viewers actually click on the link to that landing page. Then the next level of concept validation is how many of these users actually sign up. It’s possible to have more levels of increased engagement beyond this, of course. Each increased level of engagement provides more validated learning about what customers will do. In the Teenstarter example, one measure of a conversation rate would be that out of 73 people who viewed the landing page, 17 actually signed up by providing their emails.
There are other ways to validate what your customers like: interviews are often used.
Interviews: Interviews are a great way to gather information during and after a Startup Weekend. Just because you are an educator does not mean that you should assume that you know what all educators will want—still take the time to get feedback from other teachers and administrators. Other participants, organizers and mentors can help you get in contact with people outside your own educator circle. Asking educators on other teams is one good method to gather some immediate input. Showing two or three versions of a product works well to provide you with specific feedback about features.
Mockups: Remember that you do not have to create a full product to get feedback. A mockup can provide the same information with much less time investment. I learned how to use Balsamiq (free trial period!) at one Startup Weekend—it’s great for creating a design of a website or iPhone app.
Traction: Once you’ve validated your concept, you next want to build traction, something that’s unlikely to occur during a Startup Weekend because of the condensed timetable but definitely an area of focus as you move your business forward. Traction means building a set of early adopters and being able to get those adopters to do something. For example, if you’re building a community-based site, then your traction would be connected to how many users are interacting on your site. If you’re selling a product to schools, how many schools have signed? If you’re interested in investors, then they will be interested in your traction.
When you’re at Startup Weekend, learn as much as you can from other participants and mentors about other effective ways to develop your concept into a viable business!