Design thinking and lean startup: a process to design, test and launch your startup
Startup Garage is an experiential entrepreneurship course I teach at the Stanford University Graduate School of Business. Each year, about 50 teams go through that course and between 5 and 10 teams end up launching a venture based on the work they completed in the course. Companies such as ePocrates, Trulia, SoFi, DoorDash, and BipSync came from the course. Importantly, numerous other aspiring entrepreneurs launched their careers using the process and tools they learned in the course. In this short chapter, I want to share with you the key elements of the process— we call it the Startup Garage process—we teach in that course. This chapter begins with a description of the two key methodologies that provide the building blocks for the Startup Garage process: Lean Startup and Design Thinking. It then provides a description of the integrated Startup Garage process that combines these two building blocks and concludes with a description of the role of the team in the process.
Lean Startup begins with the premise that a startup is a set of hypotheses about the startup’s business model. The entrepreneur’s goal is to prove or disprove these hypotheses using experimental data. The methodology proceeds in a cycle as follows: Formulate the key business hypothesis, identify the key risks in your business hypothesis (i.e., critical assumptions on which the viability of the business rests), design an experiment to collect data to assess these risks, collect the data, analyze and determine whether they prove or disprove the key business hypothesis, and then decide whether you will persevere (continue on the same path), pivot (make a critical change in the business hypothesis), or abandon the project.
The key principle behind this methodology is that it is impossible to know whether your hypothesis about the business is correct unless you test it and collect real data. The methodology is an antidote to a common form of bias that plagues entrepreneurs, unbridled optimism that disregards any data that contradict the entrepreneur’s hypothesis until it is too late. The methodology aims to balance that optimism with rigor and data that can guide the entrepreneur and his or her team through the process of starting a business.
The key elements of this methodology are first, the business hypothesis, which is typically framed using a versatile tool called the Business Model Canvas. This tool provides a common language for summarizing how the business will create and capture value, and it divides the business model into its key elements. Second is the minimal viable product: a minimal version of the product that gains customer traction. The goal of the entrepreneur is to discover this minimal viable product through a series of experiments. Third is the pivot or persevere decision, a decision to either stay the course or make a radical change, informed by the data gathered through the experiment.
Wealthfront: A lean startup case study. Wealthfront was cofounded by Andy Ratchleff in 2008, and it initially operated as an investment manager marketplace in which clients would find outstanding managers to manage the U.S. public equities portion of their portfolio. In early 2011, Wealthfront’s managers outperformed the U.S. market by 4%. However, this was not impressing its customers and Wealthfront was not gaining adequate traction. Andy picked up the phone and spoke to some of its customers to find out what was going on. He learned that they did not want someone to manage part of their portfolio exceptionally well but rather someone to manage their complete portfolio adequately and inexpensively. Andy and his team developed a paper prototype of an automated financial advice service that would do exactly that. They shared the paper prototype with roughly 40 potential customers and walked them through the specific advice the tool would provide to them using paper and pencil (this is referred to as the concierge minimal viable product). They received consistent and enthusiastic feedback. With that information at hand, Andy refocused the team on the development of an online financial advisor that was launched in December 20115. The product was exceptionally well received, and the startup is now growing and thriving.
This short case demonstrates how Andy tried to understand why the first generation of its service was not gaining traction. He used the data to propose a new service and value proposition which he tested using low-resolution concierge minimal viable product. Armed with that information, Andy led the company through a successful pivot.
This methodology brings a much needed rigor into the process of starting a new venture, but it is not without its limitations. First, it is unclear how the original hypothesis is to be generated. And second, there is a lot of ambiguity in how the pivot-or-persevere decision is to be made.
Design thinking, the second methodology we will introduce, provides a process for generating the original hypothesis and also a high-level vision that can guide the pivot or persevere decision.
Design thinking is a process developed by the design firm IDEO and taught extensively at the Stanford design school (affectionately referred to as “d.school”). It focuses on understanding the customer deeply through meaningful empathetic interactions and using low-resolution, rapid prototyping to develop and test solutions.
This process relies on the following principles:
- Do not solve your own problems—solve someone else’s To be able to do that, you need to spend time with your potential customers and understand their day and their workflow and their experience from their perspective, not yours.
- Do not jump into solutions before you can define the problem. Be clear what is the problem you want to address and maniacally focus on solving it.
- Do not let the perfect be the enemy of good. At early stages of the development of a new solution, you do not know enough about the problem you are trying to solve. Low-resolution prototypes can help you quickly discover the problem and the solution.
- Bias for action. You want to maximize your learning by accelerating the time to a prototype and testing multiple prototypes rapidly.
- Divergent thinking—encourage wild, even crazy, solutions to open up the space of possible solutions and thus create unique and unpredictable approaches to the problem.
This process can be viewed simultaneously as a problem-definition/problem-solving methodology and a toolbox for stimulating creativity. Specifically, the empathize and define steps in the process focus on problem definition and the ideate and prototyping steps focus on problem solving. And the test step simply tests to see whether the solution solves the problem. In this last step, you can discover that the solution works but needs changes or it doesn’t. The testing stage may highlight the need to change the solution completely, but oftentimes it leads to rethinking the problem statement. As a toolbox for stimulating creativity, design thinking relies on an approach that considers multiple alternatives in both defining the problem statement and generating solutions. This is known as divergent thinking and is central to the design thinking process.
Design thinking relies on intuition, insights, and small scale qualitative interactions between the “designers” and their “customers” to uncover unmet customer needs and explore new ways to solve them. It allows rapid progress and provides the basis for gaining deep customer insights. However, it also has its limitations: it does not provide clear guidance to determine when a solution is good enough, and it does not provide tools to consider the business aspects of the solution. Questions like what is the business model, or is the solution economically viable, cannot be addressed effectively with design thinking.
The Startup Garage Innovation Process: Integrating Design Thinking and Lean Startup
At Startup Garage, the course I teach at Stanford, we have merged the two processes into an integrated process, called the Startup Garage Innovation Process, in which the students begin with design thinking to identify an unmet customer need and develop low-resolution prototypes and then progress into lean startup, in which they translate those needs and prototypes into business model canvases, minimal viable products, and experiments that supplement qualitative responses to few prototype tests followed by quantitative responses in more extensive tests. Our intention is to use the best of both worlds and develop an approach that leverages the strengths of the two foundational processes (design thinking, lean startup) and use each one to address the limitations of the other.
We will now provide more details about the steps of this integrated process.
Explore and deepen our understanding of the need
The purpose of this stage in the process is to develop an understanding of the customer, his or her needs, and develop a range of possible solutions with associated business models. The entrepreneur and his or her team spends the first month learning about the customer through direct observations, interviews, and immersion in the customer’s environment. Teams spend time with customers at their place of business or at their homes, they ask questions, make observations, gather data. At the end they summarize the information they have gathered into a list of pain points and a description of customers and their behaviors. This culminates in multiple points of view describing the customer’s problems. These points of view include a description of the customer, his or her pain point, and why this pain point is compelling. An example of a point of view is as follows:
George, a conscientious knowledge worker with average computing skills, needs an easy and seamless way to share electronic documents with his coworkers, because existing methods are becoming increasingly cumbersome and frustrating in accommodating the proliferation of computing platforms and are making him feel inadequate.
This point of view represents the customer problem solved by cloud-based document sharing and storage solutions such as DropBox and Box. It can serve as the starting point for understanding the underlying customer pain and generate possible solutions.
Teams usually generate multiple points of view, and then they focus on one based on their subjective assessment of how actionable the point of view is and how big the pain point is. No consideration for market size is made at this point.
The teams then use brainstorming to generate tens of different ways to address the selected pain point and then select one or two approaches based on team excitement, how well the approach fits the need, and team ability to develop a solution. Low-resolution prototypes of the solution are then developed in the form of storyboards, mock-ups, or videos. The team also develops a business model for each of the two solutions using the business model canvas and then performs a very rudimentary market size calculation using a top down market size formula:
Total # of Customers x Market Penetration x Revenue per Customer per Year
This calculation helps the team determine the magnitude of the opportunity.
The team then shares prototypes and basic pricing information with potential customers. Engaging in open-ended discussions, the team aims to understand whether the proposed solution resonates with the customer. At the first iteration, the most likely outcome is that the team discovers that it did not fully understand the customer need. This can send the team back to the drawing board to refine its points of view. Two or three iterations are typically needed until the team starts receiving consistent responses from the users that the need they are addressing is compelling and the solution is promising. Positive customer response takes the form of consistent willingness from the customer to engage in meaningful value exchanges with the team: sign up to be a beta tester, commit to codevelop the product, pay a small fee to reserve a fully developed product, or join a customer waiting list. In the absence of evidence of strong positive response, the team keeps iterating but is encouraged to stop after the third iteration and pivot to a different opportunity identified in the early interviews.
When a positive response is obtained, the team now moves to the Test and Validate the Solution phase. The first step is to develop a more elaborate model of the business unit economics: the lifetime value of each customer minus the customer acquisition costs. By comparing this calculation to comparable metrics in the industry and customer segments the team is targeting, the team is able to determine key assumptions that would lead into attractive and positive unit economics, and they then design experiments to gather data to support these assumptions. Common assumptions have to do with attrition rates in the customer funnel, customer repeat purchase decisions, etc. The team’s goal is to identify the two to three tipping point assumptions, assumptions that can tip the profitability equation with the least change in the underlying assumption. And then the team runs experiments to test these assumptions. These experiments usually take the form of engaging in meaningful value exchanges with customers using a more elaborate prototype, now referred to as the minimal viable product.
As an example, one of our teams wished to develop a turnkey forecasting tool, powered by artificial intelligence tools, to help container transportation companies better match supply and demand. Their minimal viable product took the form of consulting engagement: identify a client and work closely to analyze the client’s data and provide a manual solution that demonstrates the potential financial benefits in the context of the client’s operations for a given month. The team managed to secure such a client and demonstrated the potential benefits before engaging into the development of the actual tool. This enabled them to launch their sales effort to other potential customers.
Teams are also encouraged to be clear ahead of time what response will be considered affirmative for their assumptions and support that target response using a statement that “if we get X positive responses we know this will lead to a profitable business because it would support the following unit economics.” One of our teams that ended up launching as the company Doordash used a spreadsheet to model their profitability, and they then designed experiments to test assumptions in the spreadsheet. Their target was getting responses that were compatible with the assumptions in their profitability spreadsheet.
The pivot decision: Nothing illustrates the process more succinctly than the pivot decision. Once data from experiments are collected, the team meets to decide whether it is time to change directions—make a pivot. The team summarizes all the data supporting the current hypothesis as well as risks to the business model identified either previously or as a result of new data gathered. The team then also considers one or more pivots: changes in key elements of the Business Model Canvas that would address the risks uncovered so far and possibly open up opportunities for more rapid growth. The pivot decision also highlights the iterative nature of the process. It is common to see 10 teams that started at the same point to be at very different steps of the process 2 months later, based on the data they have collected and pivots they have made.
The team: Building a venture and running the Startup Garage process is a team sport. As part of the process we are encouraging our teams to spend time on basic team activities: discussing and deciding on team norms and processes, spending time to understand each other’s values and beliefs and what motivates each team member, and revisiting team norms and processes and their relationships to each other in periodic intervals. Failure to make progress in the process is sometimes due to the opportunity that the team explores but other times is the result of team dysfunction. Teams should be mindful of the process but also of their team dynamics and pay attention to both.
It is becoming increasingly recognized that startups that succeed follow a systematic, rigorous process of customer need identification, business model hypothesis generation, testing, learning, and iteration. This short chapter has summarized the key steps of the process as used at Stanford’s Startup Garage and as practiced by several startups that were successfully launched from that program.
Stefanos Zenios, Co-Director, Center for Entrepreneurial Studies, Graduate School of Business, Stanford University
- Eric Ries, The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses, Crown Business, 2011.
- Steve Blank, The Four Steps to the Epiphany, K&S Ranch, 2nd Edition, 2013.
- Steve Blank, Why the Lean Start-Up Changes Everything, May 2013 issue of Harvard Business Review.
- Alexander Osterwalder and Yves Pigneur, Business Model Generation: A Handbook for Visionaries, Game Changers, and Challengers, Wiley, Jul 13, 2010
- https://blog.wealthfront.com/introducing- online-financial-advisor-built-silicon-valley- silicon-valley/
- Design Kit: The Human-Centered Design Accessed at https://www.ideo.com/post/ design-kit
- Jon Kolko, Design Thinking Comes of Age, September 2015 issue of Harvard Business Review.
- Design Thinking: A Unified Framework For Innovation. http://www.forbes. com/sites/reuvencohen/2014/03/31/ design-thinking-a-unified-framework-for- innovation/#7e244dcc56fc