Showing posts with label How To. Show all posts
Showing posts with label How To. Show all posts

Smoke (and other) tests: smoke in your face? Pitfalls of lean start-up testing

by Lauren Miller

The lean start-up approach has the advantage of using genuine customer feedback as a means of improving the entrepreneur’s product specifically for those perceived as the niche consumer, but numerous stories from entrepreneurs and case protagonists about acting on false positives and negatives has caused me to wonder: can smoke and other lean start-up tests just end up being smoke in the entrepreneur’s face?” I question whether an entrepreneur should take the results of his or her tests as “gospel” since pitfalls in the experiment design and interpretation of results can be numerous. I will focus on a few of these potential pitfalls.

Focus groups
Steven Carpenter shared in the Cake Financial case that he has “learned that focus groups… can be unreliable because people can’t always say what they want until they can actually see it and play around with it.” This highlights the fact that customers often can’t or won’t tell you what they want or need and are often limited in what they can even think to ask for. It further underscores the important lessons revealed in Dropbox and Aardvark. Be careful in design of focus groups to utilize the most valuable feedback, as it is not all created equal. Also, make sure to listen to your customers but don’t simply obey them.

Usability tests
Martin Kessner’s study reveals the necessity of running usability tests iteratively. In his study, six usability teams could not find a single common usability problem when independently testing the same product, and no team found 50% or more of the total problems found by all. This should be a sign of caution to the entrepreneur. Though there are a plethora of studies and start-up case examples that document the improvement achieved from usability testing, Kessner’s work could show that in testing products or usability, the iterations make the test more reliable and decrease the likelihood of wide variations in responses. My takeaway: the repetition of usability tests allows an entrepreneur to better qualify the feedback he or she receives and in turn use it as a better determinant of when and how to pivot in hopes of achieving product-market fit.

Feature lists
I am working on an education software start-up, and we currently have a survey on our site that asks teachers which features they would like. Results have been great, as teachers seem to want all of the features we plan to create. Nevertheless, I have recently begun to question the reliability of their responses. I hypothesize that if we added fifteen more features, teachers would likely indicate that they want all of those as well, but the famous Columbia University marketing study implies that products with too many features often overwhelm customers. So how much should an entrepreneur trust customers when they say they want everything? Cindy Alvarez, formerly of KISSmetrics, says that customers want everything because “wanting” is free. Testing how much value features provide by adding a cost to additional features may yield more accurate results. If entrepreneurship is an art and a science, utilizing results of tests like this is the science and the decision of whether to follow them and how is the art.

I advocate that in the lean start-up model, focus should be placed as highly on test design and accuracy in feedback interpretation as it is on running tests. This way, entrepreneurs will avoid smoke-hazed and unreliable results that end up leading to pivots that could destroy their ability to connect with and address the needs of their potential consumer base. However, I’m interested in your thoughts. What other reliability traps have you seen entrepreneurs fall into when using various mechanisms to get customer feedback?

Don’t code: 5 steps to an outsourced MVP

by Matthew Thurmond

Don’t spend months learning to code or looking for a technical co-founder. My interviews with Harvard Business School entrepreneurs and outsourcing industry experts reveal a new playbook for early-stage ventures that replaces the “shut the door and learn to code” ethos with an “outsource early and hire late” strategy. A handful of web-based tools and services are enabling this shift and savvy entrepreneurs are using them to quickly and cheaply bring minimum viable products (MVP) to market.

The 5 steps below describe an easier way to create MVPs:

1) Mock it up
First things first. What, specifically, do you want to build? If it’s a website, skim similar sites and draw up the main pages with your desired logo. After a few iterations on paper, you should have a general outline. Now use Balsamiq to do a more formal mock-up. The end result will be a shareable pdf that looks like a pencil sketch.

2) Design the graphics & specs
Now you want to add color and interactivity. Use Adobe Photoshop or Fireworks for this. You can download a trial version and can take lessons on Lynda.com if needed. The end result is a pdf that looks like the actual site or app and has clickable links that allow you to experience the navigation.

3) OR, skip 2 and outsource the design
If you have no interest in design you can just skip step 2 and outsource the process entirely. DesignCrowd and 99designs let you run “design contests” based on the product specifications you set. Multiple designers will submit graphical ideas and you pick the best. The process can take 3 days – 2 weeks and costs $250-$750. In return, you get a professional pdf prototype of your MVP that is colorful and clickable.

4) Hire a freelance developer
Now go to oDesk or Elance and post a job with your design linked to the description. Expect 10-20 developers to apply and proactively send your job to 5-10 others on the site. Each developer will have feedback from previous buyers and you can conduct a few interviews to narrow it down. Most of the bids will come from off-shore developers and the good ones will charge $20+/hr. You can also outsource complex MVPs to a U.S. development agency like Elm City Labs. The work quality is higher but these agencies cost more or want equity.

5) Manage the developer
You will need to manage the development process and constantly convey what features/bug fixes you want the developer to accomplish. Use Pivotal Tracker to manage the work queue and use Word and/or Photoshop to send visual aids with clear instructions. Make sure you have ownership of the code, hosting service and domain and set up bonus payments that line up with quality targets and deadlines.

That’s it. If you’ve done the process right you should have a functional web site or application. Now you can test the product with customers and, if successful, start approaching technical co-founders and angel investors. Expect the entire outsourced MVP process for basic websites to take 1-3 months and $1,000-$5,000. Expect more complex apps to take 3-6 months and $5,000-$15,000.

For examples of recent HBS startups that have outsourced development via oDesk and Elance, check out Vaiad and Northwestern University Store.