Henrik Berglund, Presentation at Venture Cup, feb 2013.
This presentation is based on the Customer Development theory developed by Steve Blank and Bob Dorf (http://www.steveblank.com), and is based on slides developed by Steve Blank and Bob Dorf (http://www.slideshare.net/sblank/).
The document contrasts the search and execution phases of a startup. In the search phase, startups focus on developing a business model and hypotheses through customer development and agile processes. They use a founder-driven organization and experiential education strategies. In the execution phase, startups shift to operating plans, product management, and functional organizations as they scale, using more traditional education strategies like lectures.
This document discusses customer development and company building. It covers moving from early adopters to mainstream customers by managing sales growth based on market type. It also discusses crossing the chasm between early adopters and mainstream pragmatists. Strategies for crossing the chasm include creating a "whole product", focusing on one or two market segments, and becoming a market leader in a niche. The document also discusses evolving management and developing a mission-centric culture as a company grows.
This document discusses the differences between how startups and large companies operate. It states that startups are temporary organizations that search for a repeatable and scalable business model through customer validation and pivoting if needed, while large companies execute known business models through processes like sales, marketing and engineering plans. The document advocates that startups require different tools than large companies since they are searching for an unknown business model rather than executing a known plan.
This document discusses three types of markets that startups can enter: existing markets, resegmented markets, and new markets. It defines each market type and discusses the risks associated with each. Existing markets involve competing with incumbents for performance-seeking customers. Resegmented markets involve targeting underserved customer niches or a lower price point. New markets serve customer needs that have never been addressed before. The risks vary depending on the market type and how incumbent companies may respond. Overall, understanding the market type is important for developing the right business model and execution strategy.
This document discusses customer development as an important parallel process to product development for startups. It argues that startups often fail because they focus on product development without adequately engaging customers. The document introduces customer development as a process involving customer discovery, customer validation, and customer creation that should be synchronized with and guide product development. It emphasizes the importance of learning from customers over linear execution and achieving customer-centric milestones rather than focusing on the first customer ship date.
Managing the flipped classroom llp educators course jan 2013
The document provides an overview of how to structure and teach a Lean LaunchPad flipped classroom. It discusses determining what type of students the class is for, how to structure the class into teams, emphasizing an experiential and immersive approach. Key concepts covered are searching for problems versus executing solutions, using the Business Model Canvas as a scorecard, and making customer discovery the heart of the class. It also provides resources for teaching including recommended co-instructors, a faculty handbook, and the instructor's website.
This document discusses customer development and outlines its key steps and methodology. It begins with an agenda that includes discussing the WebVan case study, testing problems and product concepts with customers, and establishing a customer development team. The rest of the document provides details on the customer development process, which involves testing hypotheses with customers through iterative phases of discovery and validation over several months or years. It emphasizes the importance of listening to customers, testing problems and products, and modifying the process for each individual company's needs.
The document provides an overview of customer development and discovery phases for a high tech startup. It discusses testing hypotheses about customers, problems, products, distribution, pricing, demand creation and competition. The key phases covered are authoring hypotheses, testing the problem hypothesis by talking to customers, presenting the problem, and testing the product hypothesis by getting early feedback and iterating before moving to customer validation.
Customer Assistant: Product Assistant: Marketing Assistant: Sales
Discovery Development & PR & Distribution
! Titles describe learning tasks not execution functions
! CEO + 4 Assistants focused on learning not execution
! Small, focused on getting out of the building
Customer Development in the High-Tech Enterprise Fall 2009
Customer Development Team
! CEO - Oversees entire Customer Development process
! Assistant: Customer Discovery
' Tests customer/problem hypotheses
! Assistant: Product Development
' Tests product hypotheses
! Assistant: Marketing & PR
' Tests demand creation hypotheses
! Assistant: Sales & Distribution
'
This document discusses how to build a startup by focusing on customer development rather than plans or forecasts. It recommends:
1) Viewing the business model as hypotheses to be tested rather than plans to be executed.
2) Using customer development, not product development, as the strategy by testing problems and solutions with customers.
3) Pivoting the business model based on customer feedback through iterative customer discovery and validation processes.
Customer Development/Lean Startup 092609 class 7 and 8
This document provides an agenda and materials for a customer development class focusing on customer validation. The agenda includes reviewing two case studies of HP Kittyhawk and Wildfire, as well as a discussion of customer validation. The materials include slides on the HP Kittyhawk case, an overview of the customer validation phase, and details on getting ready to sell including articulating a value proposition, developing sales collateral, mapping channels and sales, hiring a sales closer, and formalizing advisory boards.
The document discusses six ways startups can fail and provides tips for success. It begins by outlining traditional models that implicitly assume the customer problem and product features are already known. However, the document argues startups should not assume they know these things and should instead search for an unknown business model. It recommends using customer development to test hypotheses about the problem, customer, and solution through interviews and iteration. The document advocates developing minimum viable products and being willing to pivot based on what is learned from customers.
The document discusses different types of startups and lessons learned about building startup ecosystems. It outlines four main types of startups - lifestyle startups that allow owners to pursue a passion, social entrepreneurship startups that solve social problems, small businesses that support families, and scalable startups designed for growth. It also examines the factors that contributed to the success of Silicon Valley's ecosystem, including government investment, university research, a culture that embraces risk, and the necessary infrastructure, culture, tools, and motivations.
The document provides advice for creating a successful startup. It discusses that Mike, an experienced executive, had a great idea for a product but some key mistakes. It outlines 5 lessons: 1) No business plan survives customer contact. 2) Have a clear business model. 3) Consider alternative models. 4) Treat your model as hypotheses to test. 5) Verify your model before building your company to avoid wasting money. It emphasizes the importance of testing assumptions through customer development and pivoting the model until it is proven.
- Startups are focused on searching for a scalable and repeatable business model through continuous customer validation and pivoting if needed. In contrast, large companies execute established business models through planning and accounting.
- Traditional processes like marketing, sales, engineering are inappropriate for startups still searching for a model. Startups require agile development and customer development focused on hypothesis testing.
- Once a startup finds product/market fit and a repeatable sales process, it transitions to a large company focused on growth, processes, and management over leadership. Accounting takes priority over metrics like in large companies versus the search focus of startups.
This document discusses customer creation strategies for startups. It outlines four key activities for customer creation: setting year one objectives, positioning, launch, and demand creation. It notes that customer creation strategies should differ depending on whether the startup is targeting an existing market, resegmenting an existing market, or entering a new market. The document also discusses using influence maps, sales roadmaps, and marketing metrics like the AARRR framework to track customer acquisition and retention.
From a concept to viable business — How do we know if we are building the rig...
This document discusses building the right product by focusing on problem/solution fit, business model/market fit, hypothesis/experiment fit, and user needs/service fit. It emphasizes the importance of validating your concepts by talking to customers and measuring results rather than assuming you know requirements. The key steps outlined are drawing a business model canvas, stating hypotheses to test, and getting customer feedback through discovery and validation. Pivoting based on learnings is important rather than prematurely scaling execution without verifying the business model. Overall the message is to interface business, design and engineering to create successful businesses by making the business the driver.
Cbi Day Henrik - Introduction - Users and Radical Innovation
The document discusses the relationship between invention, innovation, and customers. It argues that while invention creates something new, innovation requires widespread adoption, which necessitates understanding customers. However, simply listening to customers may not lead to radical innovations if customers cannot envision solutions to problems they face. The document suggests that the wise approach is not to just listen to customers, but to understand the problems they experience and their goals, which can provide insight even if customers cannot envision specific solutions. It advocates approaches like design thinking and customer development to properly leverage customer input for innovation.
Review of Israel Kirzner's work on entrepreneurship, and of related work by entrepreneurship researchers.
Paper now forthcoming in Entrepreneurship Theory and Practice
http://henrikberglund.com/A%20Tale%20of%20Two%20Kirzners.pdf
This document discusses the differences between startups and companies, clones and innovators, and metrics. It defines startups as temporary organizations that search for a repeatable and scalable business model under uncertainty, whereas companies execute established business models. It recommends that startups clone existing ideas 80-99% and only innovate 1-20% by picking a clear competitive dimension for users to experience. The document also stresses the importance of using appropriate metrics and only innovating on essential aspects as a startup.
This document introduces the concept of customer development and summarizes its key phases over the past decade. It begins with describing how traditional product development models made incorrect assumptions about knowing customer problems and product solutions. It then outlines Steve Blank's customer development model, including the phases of customer discovery, customer validation, customer creation, and company building. It emphasizes the importance of getting outside the building to test hypotheses through customer feedback in early phases via continuous discovery and "do-over" iterations until a repeatable and scalable business model is proven.
The 12-step document outlines a process for becoming an entrepreneur. It begins by distinguishing between different types of entrepreneurs and startups, such as lifestyle startups, small businesses, social enterprises, and scalable startups. It then discusses finding an idea of sufficient size by considering idea sources and sizing market opportunities. The document also covers crafting hypotheses about the business model, building a basic website, getting early customers, and testing the problem and solution with customer feedback through iterative development.
Henrik Berglund - Customer Development for startups
Customer Development in start-ups, with Boo.com as an example of what may go wrong, Palm Pilot as an example of a demo prototype (early MVP), and Groupon and YouTube as examples of pivots.
This presentation is based on the Customer Development theory developed by Steve Blank and Bob Dorf (http://www.steveblank.com), and is based on slides developed by Steve Blank and Bob Dorf (http://www.slideshare.net/sblank/).
Workshop at Chalmers Innovation Startup Camp 2013.
This presentation is based on the Customer Development theory developed by Steve Blank and Bob Dorf (http://www.steveblank.com), and is based on slides developed by Steve Blank and Bob Dorf (http://www.slideshare.net/sblank/).
Customer Development - Identifying and Testing Startup Hypotheses
Presentation for VCs, angels and incubator coaches on how to help startups implement customer development, specifically how to identify and test startup hypotheses.
Draws heavily on ideas and content from Steve Blank, Cindy Alvarez and Jason Evanish.
Researching Entrepreneurship using Phenomenological Methods
The document discusses phenomenology as a method for studying entrepreneurship. It begins by defining entrepreneurship as creating new products/services under conditions of uncertainty, rather than just small business ownership. It then discusses common approaches to studying entrepreneurs like traits, behaviors, cognitions and discursive factors, and argues phenomenology can provide insights these miss by focusing on entrepreneurs' lived experiences. The document provides an overview of phenomenology's principles and methods, including purposive sampling, semi-structured interviews to understand experiences, and analyzing data for themes. It provides examples of phenomenological entrepreneurship research questions and studies.
The document discusses Geoffrey Moore's book "Crossing the Chasm". The book focuses on 3 main themes: 1) the technology adoption life cycle, 2) the problem of crossing the chasm between early adopters and the early majority, and 3) solutions for how to cross the chasm. It also discusses the different customer types along the adoption curve and strategies for targeting customers, assembling resources, positioning products, and launching attacks to help cross the chasm from early adopters to the early majority.
This document discusses strategies for marketing high-tech products by crossing the "chasm" between early adopters and the mainstream market. It describes Everett Rogers' diffusion of innovations theory and the technology adoption life cycle, which divides adopters into innovators, early adopters, early majority, late majority and laggards. For high-tech, Geoffrey Moore's model names the categories technology enthusiasts, visionaries, pragmatists, conservatives and skeptics. The document explains how differences between these groups cause cracks and chasms in adoption. It advocates focusing on a beachhead segment using segmentation, differentiation, positioning and distribution to target a compelling customer and cross the chasm to the mainstream.
The document discusses Geoffrey Moore's technology adoption life cycle model and strategies for high-tech companies to cross the "chasm" between early adopters and the mainstream market. It outlines the challenges of disruptive innovation including high risk and low data. The life cycle model includes innovators, early adopters, early majority, late majority, and laggards. To cross the chasm, companies should target an initial "beachhead" segment and provide a "whole product" solution. For B2C markets, companies should focus on acquiring, engaging, converting, and enlisting users to achieve viral growth and reach the "tornado phase". For B2B, targeting flagship customers pre-chasm and compelling use cases post
Eric Ries' presentation on lean startups. From Steve Blank's Customer Development course at Berkeley. Learn more and hear the audio at http://bit.ly/3qsvJ.
This document discusses Lean Startup principles including validated learning, building-measuring-learning quickly through iterations, and innovation accounting. It emphasizes that entrepreneurship is management, startups are experiments, and most successful startups pivot their vision based on customer feedback. The Lean Startup methodology advocates for developing minimum viable products and continuously deploying, measuring and improving through techniques like A/B testing to rapidly learn what customers want.
The document outlines an agenda for a two-day workshop on business models and customer development. Day one covers introducing customer development, developing a value proposition and identifying customer segments. Students work on an initial business model canvas and present it. Day two focuses on customer relationships, revenue streams, partners, resources/costs, and concludes with a customer development manifesto. The agenda emphasizes learning customer development strategies through hands-on exercises and student presentations of their business model canvas and customer discovery plans.
Everything You Knew About Startups is Wrong, And How to Make it Right
- Traditional startup models assume the customer problem and product features are known, but they are actually hypotheses that need to be tested
- Startups should focus on customer development from the beginning through customer discovery, validation, and creation to learn about customers and iterate the product
- The lean startup methodology emphasizes rapid iteration and minimal viable products to get customer feedback quickly rather than lengthy waterfall development processes
Steve Blank discusses how startups can fail less by focusing on customer development and business models rather than execution alone. He outlines the key insights:
1. Most startups fail due to a lack of customers, not product development issues. Customer development is a search strategy to test hypotheses about the problem and solution.
2. A business model is made up of hypotheses that need to be tested, not assumptions. Customer development helps test the hypotheses through interviews, demos, and pivots if needed.
3. Rather than managing processes, founders should run a customer development team to search for a repeatable and scalable business model. Functional organizations by department are less effective than a founder-driven customer development team.
The document provides an agenda and overview for a two-day TiE workshop on best practices and principles for startups. Day 1 focuses on developing business models, including exercises on creating business model canvases (BMCs) and minimum viable products (MVPs). Day 2 involves customer investigation in the field and a retrospective. The workshop teaches entrepreneurs to validate assumptions and learn quickly by talking to customers, developing BMCs and MVPs, and iterating based on customer feedback.
Startup 101: Finding your business model: TIE Bangalore
The document provides an agenda and overview for a two-day TiE workshop on best practices and principles for startups. Day 1 focuses on developing business models, including using a Business Model Canvas template and developing minimum viable products. Participants then conduct customer investigations to validate their assumptions. Day 2 involves a retrospective and presentations from startup teams on their findings from customer interviews. The workshop aims to provide experiential learning for startups on iterative business model development and customer validation.
Marketing for High-Tech Startups presented at UC Berkeley
1. Marketing for high-tech startups has changed in recent years due to shifts in software markets and development philosophies. Products are often developed iteratively now rather than using the black-box model of the past.
2. When developing a marketing strategy, startups must consider the 4Ps of marketing - product, price, place, and promotion. This includes deciding where the company's product fits relative to larger competitors, choosing the appropriate pricing and distribution models, and determining how to effectively promote the product and acquire customers.
3. Effective customer acquisition involves testing various promotion channels like social media, blogs, conferences and evaluating their cost effectiveness. The goal is to drive customers through the lifecycle from initial contact
This document outlines a presentation on product management and achieving product-market fit. The presentation covers key concepts like the customer development process, lean startup theory, and crossing the chasm. It discusses tools and techniques for validating ideas with customers before and after achieving product-market fit. An exercise about strategic choices for Blackberry 10 is included to help attendees practice applying the concepts. The overall goal is to help attendees devise an approach for rapidly achieving product-market fit and avoiding wasting resources.
The document discusses how the rules for startups have changed with the rise of new tech bubbles. It outlines four phases of startup liquidity from 1970-2014 and how approaches differed between building long-term businesses versus short-term flips. The customer development process is introduced as a methodology for startups to search for their business model by testing hypotheses through customer interaction rather than relying only on plans. Metrics are emphasized over accounting, with the goal of continuous learning rather than presuming knowledge of customers or features up front.
The document provides an overview of Customer Development, which is the process startups use to search for a business model. It discusses how startups should test hypotheses about their problem, customer, product, and other business model components by getting out of the building and talking to customers. The Lean LaunchPad process of building a minimum viable product and continuously pivoting based on customer feedback is highlighted. An example is given of a team that conducted customer interviews over 8 weeks and pivoted from an autonomous mowing idea to focus on weeding for organic farmers after determining a bigger problem and opportunity.
This document discusses the concept of product-market fit and how startups can achieve it through lean startup principles. It recommends that startups rapidly test hypotheses with minimum viable products to validate their business model with customers before scaling. The document outlines tools and techniques for customer development and discovery. It contrasts the pre- and post-product market fit stages and uses the example of Foursquare to illustrate how achieving product-market fit shaped its growth challenges.
The document lists the projects and roles the author has performed at American Woodmark over their career. It includes projects in marketing, product development, national accounts, general management, and corporate training and development. Some highlights include leading the repositioning of the Timberlake brand, developing an automated pricing approval system, turning around an unprofitable division, and creating comprehensive sales and marketing training programs. The author has received six President's Awards, the company's highest honor, for projects that achieved outstanding results and improved financial performance.
Entrepreneurship, Research and Innovation - Supelec 2014
This 112 slide presentation introduces key concepts about startups including:
- Startups search for a business model while large companies execute established models.
- Traditional business schools focus on strategies for large companies, while startups require a different approach centered on customer development, agile processes, and pivoting based on validated learning rather than upfront planning.
- The business model canvas is introduced as a tool to conceptualize the key elements of a startup business model, including customer segments, value propositions, channels, and revenue streams.
Trying to connect the dots between Content Marketing and Marketing Automation? Join DemandGen for another exploration of B2B Marketing Automation best practice. This webcast will be looking at the relationship between Content Marketing and Marketing Automation. We’ve put together another panel of smart b2b practitioners. This month’s insights are provided by Doug Kessler of Velocity Partners, author of The B2B Content Marketing Workbook and Bob Apollo, founder of Inflexion-Point, B2B Sales and Marketing Performance Improvement specialists.
We’ll be taking a closer look at the relationship between Marketing Automation and Content Marketing:
- Rules of thought leadership
- Aligning content to the buying cycle
- Best practices: Building an integrated content marketing strategy with Marketing Automation tools
- B2B content marketing examples and successes
- Measuring the results
The document outlines six common ways startups can fail and provides advice on how to succeed instead. It discusses how startups should not try to operate like large companies by following traditional models. Startups need to search for an unknown business model rather than execute a known one. The key is getting out of the building to test hypotheses through customer development, building minimal viable products, and pivoting based on feedback.
Startup camp chalmers innovation 19 september 2014
This document discusses business models and customer development for startups versus established companies. It begins by defining companies as organizations that sell products or services for profit, organized around business models. Startups are defined as temporary organizations designed to search for a repeatable and scalable business model. The document then discusses how companies execute business plans while startups search for their business model through customer development. It advocates that startups focus on searching for the right business model rather than executing a predetermined plan.
Introduction to Customer Development at the Lean Startup Intensive at Web 2.0...
The document discusses customer development and the search for a business model in startups. It emphasizes testing hypotheses with customers to validate problems and solutions. There are three types of markets - existing, resegmented, and new - that require different sales, marketing and business development approaches. The key ideas are to parallel customer development with product development using measurable checkpoints tied to customer milestones rather than just product shipments. The goal is to prove a repeatable and scalable business model before scaling the company.
This document summarizes an entrepreneur's process of validating a business idea for an autonomous weeding robot. Through interviews with 75 customers in 8 weeks, the entrepreneur learned that the biggest problem was weeding in organic crops. A minimum viable product called "CarrotBot" was built to collect machine vision data. Further customer validation revealed that both farmers and weeding service providers would be interested customers. The business model was updated to target mid-large organic farmers, agricultural corporations, and weeding service providers with a solution that reduces labor costs through automation.
The Northfront Entrepreneur Alliance is a entreprenuer networking association in Northern Utah. This presentation was given on 04.06.11 to the group by Rob Kunz- a successfull entrepreneur, investor., and co-founder of BoomStartup. He discusses the Lean Startup Business Model and how to apply it.
Steve Budra has extensive experience leading marketing strategies that have generated significant revenue growth for companies. As highlighted in testimonials, he is praised for his creativity, vision, ability to execute plans, and delivering great results. His background includes tripling revenues for a graphic arts supplier through rebranding and international expansion, and increasing product revenue 400% for a business forms manufacturer through affiliate partnership strategies.
This document provides an overview and syllabus for the course "Customer Development in the High-Tech Enterprise" taught by Steve Blank. The course is divided into two parts over 12 weeks and will cover key concepts in customer development, applying the customer development methodology to case studies of companies, and having student teams conduct a research project analyzing a company using customer development. The syllabus outlines the weekly classes, assigned readings, cases to be discussed, application exercises for students, and the team research project which accounts for 50% of the grade. The course aims to teach students how to reduce product/market risk and bring new products to market through customer development and validation.
The document summarizes Steve Blank's work developing the Lean LaunchPad methodology for teaching entrepreneurship. It shows how his thinking evolved from initially believing entrepreneurship education should focus on execution, to realizing it must begin with searching for a business model. This led to developing customer development and the business model canvas as the core of the Lean LaunchPad class, which trains students to search for viability before executing a plan. The methodology then spread globally to thousands of students through additional classes, online offerings, and trainer programs.
Tonight's event will include pizza and beer from 6:00-6:45pm, followed by introductions and a Lean Startup refresher presentation from 6:45-8:00pm with a question period afterwards. Upcoming meetups on April 18th and May 16th will feature different guest speakers. The document provides details on an event for a Lean Startup group including the agenda, upcoming events and contact information.
The document contrasts the search and execution phases of a startup. In the search phase, startups focus on developing a business model and hypotheses through customer development and agile processes. They use a founder-driven organization and experiential education strategies. In the execution phase, startups shift to operating plans, product management, and functional organizations as they scale, using more traditional education strategies like lectures.
This document discusses customer development and company building. It covers moving from early adopters to mainstream customers by managing sales growth based on market type. It also discusses crossing the chasm between early adopters and mainstream pragmatists. Strategies for crossing the chasm include creating a "whole product", focusing on one or two market segments, and becoming a market leader in a niche. The document also discusses evolving management and developing a mission-centric culture as a company grows.
This document discusses the differences between how startups and large companies operate. It states that startups are temporary organizations that search for a repeatable and scalable business model through customer validation and pivoting if needed, while large companies execute known business models through processes like sales, marketing and engineering plans. The document advocates that startups require different tools than large companies since they are searching for an unknown business model rather than executing a known plan.
This document discusses three types of markets that startups can enter: existing markets, resegmented markets, and new markets. It defines each market type and discusses the risks associated with each. Existing markets involve competing with incumbents for performance-seeking customers. Resegmented markets involve targeting underserved customer niches or a lower price point. New markets serve customer needs that have never been addressed before. The risks vary depending on the market type and how incumbent companies may respond. Overall, understanding the market type is important for developing the right business model and execution strategy.
This document discusses customer development as an important parallel process to product development for startups. It argues that startups often fail because they focus on product development without adequately engaging customers. The document introduces customer development as a process involving customer discovery, customer validation, and customer creation that should be synchronized with and guide product development. It emphasizes the importance of learning from customers over linear execution and achieving customer-centric milestones rather than focusing on the first customer ship date.
Managing the flipped classroom llp educators course jan 2013Stanford University
The document provides an overview of how to structure and teach a Lean LaunchPad flipped classroom. It discusses determining what type of students the class is for, how to structure the class into teams, emphasizing an experiential and immersive approach. Key concepts covered are searching for problems versus executing solutions, using the Business Model Canvas as a scorecard, and making customer discovery the heart of the class. It also provides resources for teaching including recommended co-instructors, a faculty handbook, and the instructor's website.
Customer Development 4: Customer Discovery Part 1Venture Hacks
This document discusses customer development and outlines its key steps and methodology. It begins with an agenda that includes discussing the WebVan case study, testing problems and product concepts with customers, and establishing a customer development team. The rest of the document provides details on the customer development process, which involves testing hypotheses with customers through iterative phases of discovery and validation over several months or years. It emphasizes the importance of listening to customers, testing problems and products, and modifying the process for each individual company's needs.
The document provides an overview of customer development and discovery phases for a high tech startup. It discusses testing hypotheses about customers, problems, products, distribution, pricing, demand creation and competition. The key phases covered are authoring hypotheses, testing the problem hypothesis by talking to customers, presenting the problem, and testing the product hypothesis by getting early feedback and iterating before moving to customer validation.
Customer Assistant: Product Assistant: Marketing Assistant: Sales
Discovery Development & PR & Distribution
! Titles describe learning tasks not execution functions
! CEO + 4 Assistants focused on learning not execution
! Small, focused on getting out of the building
Customer Development in the High-Tech Enterprise Fall 2009
Customer Development Team
! CEO - Oversees entire Customer Development process
! Assistant: Customer Discovery
' Tests customer/problem hypotheses
! Assistant: Product Development
' Tests product hypotheses
! Assistant: Marketing & PR
' Tests demand creation hypotheses
! Assistant: Sales & Distribution
'
This document discusses how to build a startup by focusing on customer development rather than plans or forecasts. It recommends:
1) Viewing the business model as hypotheses to be tested rather than plans to be executed.
2) Using customer development, not product development, as the strategy by testing problems and solutions with customers.
3) Pivoting the business model based on customer feedback through iterative customer discovery and validation processes.
This document provides an agenda and materials for a customer development class focusing on customer validation. The agenda includes reviewing two case studies of HP Kittyhawk and Wildfire, as well as a discussion of customer validation. The materials include slides on the HP Kittyhawk case, an overview of the customer validation phase, and details on getting ready to sell including articulating a value proposition, developing sales collateral, mapping channels and sales, hiring a sales closer, and formalizing advisory boards.
The document discusses six ways startups can fail and provides tips for success. It begins by outlining traditional models that implicitly assume the customer problem and product features are already known. However, the document argues startups should not assume they know these things and should instead search for an unknown business model. It recommends using customer development to test hypotheses about the problem, customer, and solution through interviews and iteration. The document advocates developing minimum viable products and being willing to pivot based on what is learned from customers.
The document discusses different types of startups and lessons learned about building startup ecosystems. It outlines four main types of startups - lifestyle startups that allow owners to pursue a passion, social entrepreneurship startups that solve social problems, small businesses that support families, and scalable startups designed for growth. It also examines the factors that contributed to the success of Silicon Valley's ecosystem, including government investment, university research, a culture that embraces risk, and the necessary infrastructure, culture, tools, and motivations.
The document provides advice for creating a successful startup. It discusses that Mike, an experienced executive, had a great idea for a product but some key mistakes. It outlines 5 lessons: 1) No business plan survives customer contact. 2) Have a clear business model. 3) Consider alternative models. 4) Treat your model as hypotheses to test. 5) Verify your model before building your company to avoid wasting money. It emphasizes the importance of testing assumptions through customer development and pivoting the model until it is proven.
- Startups are focused on searching for a scalable and repeatable business model through continuous customer validation and pivoting if needed. In contrast, large companies execute established business models through planning and accounting.
- Traditional processes like marketing, sales, engineering are inappropriate for startups still searching for a model. Startups require agile development and customer development focused on hypothesis testing.
- Once a startup finds product/market fit and a repeatable sales process, it transitions to a large company focused on growth, processes, and management over leadership. Accounting takes priority over metrics like in large companies versus the search focus of startups.
This document discusses customer creation strategies for startups. It outlines four key activities for customer creation: setting year one objectives, positioning, launch, and demand creation. It notes that customer creation strategies should differ depending on whether the startup is targeting an existing market, resegmenting an existing market, or entering a new market. The document also discusses using influence maps, sales roadmaps, and marketing metrics like the AARRR framework to track customer acquisition and retention.
From a concept to viable business — How do we know if we are building the rig...Marko Taipale
This document discusses building the right product by focusing on problem/solution fit, business model/market fit, hypothesis/experiment fit, and user needs/service fit. It emphasizes the importance of validating your concepts by talking to customers and measuring results rather than assuming you know requirements. The key steps outlined are drawing a business model canvas, stating hypotheses to test, and getting customer feedback through discovery and validation. Pivoting based on learnings is important rather than prematurely scaling execution without verifying the business model. Overall the message is to interface business, design and engineering to create successful businesses by making the business the driver.
Cbi Day Henrik - Introduction - Users and Radical InnovationHenrik Berglund
The document discusses the relationship between invention, innovation, and customers. It argues that while invention creates something new, innovation requires widespread adoption, which necessitates understanding customers. However, simply listening to customers may not lead to radical innovations if customers cannot envision solutions to problems they face. The document suggests that the wise approach is not to just listen to customers, but to understand the problems they experience and their goals, which can provide insight even if customers cannot envision specific solutions. It advocates approaches like design thinking and customer development to properly leverage customer input for innovation.
Review of Israel Kirzner's work on entrepreneurship, and of related work by entrepreneurship researchers.
Paper now forthcoming in Entrepreneurship Theory and Practice
http://henrikberglund.com/A%20Tale%20of%20Two%20Kirzners.pdf
This document discusses the differences between startups and companies, clones and innovators, and metrics. It defines startups as temporary organizations that search for a repeatable and scalable business model under uncertainty, whereas companies execute established business models. It recommends that startups clone existing ideas 80-99% and only innovate 1-20% by picking a clear competitive dimension for users to experience. The document also stresses the importance of using appropriate metrics and only innovating on essential aspects as a startup.
This document introduces the concept of customer development and summarizes its key phases over the past decade. It begins with describing how traditional product development models made incorrect assumptions about knowing customer problems and product solutions. It then outlines Steve Blank's customer development model, including the phases of customer discovery, customer validation, customer creation, and company building. It emphasizes the importance of getting outside the building to test hypotheses through customer feedback in early phases via continuous discovery and "do-over" iterations until a repeatable and scalable business model is proven.
The 12-step document outlines a process for becoming an entrepreneur. It begins by distinguishing between different types of entrepreneurs and startups, such as lifestyle startups, small businesses, social enterprises, and scalable startups. It then discusses finding an idea of sufficient size by considering idea sources and sizing market opportunities. The document also covers crafting hypotheses about the business model, building a basic website, getting early customers, and testing the problem and solution with customer feedback through iterative development.
Henrik Berglund - Customer Development for startupsHenrik Berglund
Customer Development in start-ups, with Boo.com as an example of what may go wrong, Palm Pilot as an example of a demo prototype (early MVP), and Groupon and YouTube as examples of pivots.
This presentation is based on the Customer Development theory developed by Steve Blank and Bob Dorf (http://www.steveblank.com), and is based on slides developed by Steve Blank and Bob Dorf (http://www.slideshare.net/sblank/).
Workshop at Chalmers Innovation Startup Camp 2013.
This presentation is based on the Customer Development theory developed by Steve Blank and Bob Dorf (http://www.steveblank.com), and is based on slides developed by Steve Blank and Bob Dorf (http://www.slideshare.net/sblank/).
Customer Development - Identifying and Testing Startup HypothesesHenrik Berglund
Presentation for VCs, angels and incubator coaches on how to help startups implement customer development, specifically how to identify and test startup hypotheses.
Draws heavily on ideas and content from Steve Blank, Cindy Alvarez and Jason Evanish.
Researching Entrepreneurship using Phenomenological MethodsHenrik Berglund
The document discusses phenomenology as a method for studying entrepreneurship. It begins by defining entrepreneurship as creating new products/services under conditions of uncertainty, rather than just small business ownership. It then discusses common approaches to studying entrepreneurs like traits, behaviors, cognitions and discursive factors, and argues phenomenology can provide insights these miss by focusing on entrepreneurs' lived experiences. The document provides an overview of phenomenology's principles and methods, including purposive sampling, semi-structured interviews to understand experiences, and analyzing data for themes. It provides examples of phenomenological entrepreneurship research questions and studies.
The document discusses Geoffrey Moore's book "Crossing the Chasm". The book focuses on 3 main themes: 1) the technology adoption life cycle, 2) the problem of crossing the chasm between early adopters and the early majority, and 3) solutions for how to cross the chasm. It also discusses the different customer types along the adoption curve and strategies for targeting customers, assembling resources, positioning products, and launching attacks to help cross the chasm from early adopters to the early majority.
This document discusses strategies for marketing high-tech products by crossing the "chasm" between early adopters and the mainstream market. It describes Everett Rogers' diffusion of innovations theory and the technology adoption life cycle, which divides adopters into innovators, early adopters, early majority, late majority and laggards. For high-tech, Geoffrey Moore's model names the categories technology enthusiasts, visionaries, pragmatists, conservatives and skeptics. The document explains how differences between these groups cause cracks and chasms in adoption. It advocates focusing on a beachhead segment using segmentation, differentiation, positioning and distribution to target a compelling customer and cross the chasm to the mainstream.
Crossing the Chasm - What's New, What's NotGeoffrey Moore
The document discusses Geoffrey Moore's technology adoption life cycle model and strategies for high-tech companies to cross the "chasm" between early adopters and the mainstream market. It outlines the challenges of disruptive innovation including high risk and low data. The life cycle model includes innovators, early adopters, early majority, late majority, and laggards. To cross the chasm, companies should target an initial "beachhead" segment and provide a "whole product" solution. For B2C markets, companies should focus on acquiring, engaging, converting, and enlisting users to achieve viral growth and reach the "tornado phase". For B2B, targeting flagship customers pre-chasm and compelling use cases post
Eric Ries' presentation on lean startups. From Steve Blank's Customer Development course at Berkeley. Learn more and hear the audio at http://bit.ly/3qsvJ.
Eric Ries - The Lean Startup - Google Tech TalkEric Ries
This document discusses Lean Startup principles including validated learning, building-measuring-learning quickly through iterations, and innovation accounting. It emphasizes that entrepreneurship is management, startups are experiments, and most successful startups pivot their vision based on customer feedback. The Lean Startup methodology advocates for developing minimum viable products and continuously deploying, measuring and improving through techniques like A/B testing to rapidly learn what customers want.
The document outlines an agenda for a two-day workshop on business models and customer development. Day one covers introducing customer development, developing a value proposition and identifying customer segments. Students work on an initial business model canvas and present it. Day two focuses on customer relationships, revenue streams, partners, resources/costs, and concludes with a customer development manifesto. The agenda emphasizes learning customer development strategies through hands-on exercises and student presentations of their business model canvas and customer discovery plans.
Everything You Knew About Startups is Wrong, And How to Make it RightStanford University
- Traditional startup models assume the customer problem and product features are known, but they are actually hypotheses that need to be tested
- Startups should focus on customer development from the beginning through customer discovery, validation, and creation to learn about customers and iterate the product
- The lean startup methodology emphasizes rapid iteration and minimal viable products to get customer feedback quickly rather than lengthy waterfall development processes
Steve Blank discusses how startups can fail less by focusing on customer development and business models rather than execution alone. He outlines the key insights:
1. Most startups fail due to a lack of customers, not product development issues. Customer development is a search strategy to test hypotheses about the problem and solution.
2. A business model is made up of hypotheses that need to be tested, not assumptions. Customer development helps test the hypotheses through interviews, demos, and pivots if needed.
3. Rather than managing processes, founders should run a customer development team to search for a repeatable and scalable business model. Functional organizations by department are less effective than a founder-driven customer development team.
The document provides an agenda and overview for a two-day TiE workshop on best practices and principles for startups. Day 1 focuses on developing business models, including exercises on creating business model canvases (BMCs) and minimum viable products (MVPs). Day 2 involves customer investigation in the field and a retrospective. The workshop teaches entrepreneurs to validate assumptions and learn quickly by talking to customers, developing BMCs and MVPs, and iterating based on customer feedback.
Startup 101: Finding your business model: TIE BangaloreManish G Pillewar
The document provides an agenda and overview for a two-day TiE workshop on best practices and principles for startups. Day 1 focuses on developing business models, including using a Business Model Canvas template and developing minimum viable products. Participants then conduct customer investigations to validate their assumptions. Day 2 involves a retrospective and presentations from startup teams on their findings from customer interviews. The workshop aims to provide experiential learning for startups on iterative business model development and customer validation.
Marketing for High-Tech Startups presented at UC BerkeleyR. Paul Singh
1. Marketing for high-tech startups has changed in recent years due to shifts in software markets and development philosophies. Products are often developed iteratively now rather than using the black-box model of the past.
2. When developing a marketing strategy, startups must consider the 4Ps of marketing - product, price, place, and promotion. This includes deciding where the company's product fits relative to larger competitors, choosing the appropriate pricing and distribution models, and determining how to effectively promote the product and acquire customers.
3. Effective customer acquisition involves testing various promotion channels like social media, blogs, conferences and evaluating their cost effectiveness. The goal is to drive customers through the lifecycle from initial contact
This document outlines a presentation on product management and achieving product-market fit. The presentation covers key concepts like the customer development process, lean startup theory, and crossing the chasm. It discusses tools and techniques for validating ideas with customers before and after achieving product-market fit. An exercise about strategic choices for Blackberry 10 is included to help attendees practice applying the concepts. The overall goal is to help attendees devise an approach for rapidly achieving product-market fit and avoiding wasting resources.
The document discusses how the rules for startups have changed with the rise of new tech bubbles. It outlines four phases of startup liquidity from 1970-2014 and how approaches differed between building long-term businesses versus short-term flips. The customer development process is introduced as a methodology for startups to search for their business model by testing hypotheses through customer interaction rather than relying only on plans. Metrics are emphasized over accounting, with the goal of continuous learning rather than presuming knowledge of customers or features up front.
The document provides an overview of Customer Development, which is the process startups use to search for a business model. It discusses how startups should test hypotheses about their problem, customer, product, and other business model components by getting out of the building and talking to customers. The Lean LaunchPad process of building a minimum viable product and continuously pivoting based on customer feedback is highlighted. An example is given of a team that conducted customer interviews over 8 weeks and pivoted from an autonomous mowing idea to focus on weeding for organic farmers after determining a bigger problem and opportunity.
This document discusses the concept of product-market fit and how startups can achieve it through lean startup principles. It recommends that startups rapidly test hypotheses with minimum viable products to validate their business model with customers before scaling. The document outlines tools and techniques for customer development and discovery. It contrasts the pre- and post-product market fit stages and uses the example of Foursquare to illustrate how achieving product-market fit shaped its growth challenges.
The document lists the projects and roles the author has performed at American Woodmark over their career. It includes projects in marketing, product development, national accounts, general management, and corporate training and development. Some highlights include leading the repositioning of the Timberlake brand, developing an automated pricing approval system, turning around an unprofitable division, and creating comprehensive sales and marketing training programs. The author has received six President's Awards, the company's highest honor, for projects that achieved outstanding results and improved financial performance.
Entrepreneurship, Research and Innovation - Supelec 2014Daniel Jarjoura
This 112 slide presentation introduces key concepts about startups including:
- Startups search for a business model while large companies execute established models.
- Traditional business schools focus on strategies for large companies, while startups require a different approach centered on customer development, agile processes, and pivoting based on validated learning rather than upfront planning.
- The business model canvas is introduced as a tool to conceptualize the key elements of a startup business model, including customer segments, value propositions, channels, and revenue streams.
Content marketing For Marketing Automation DemandGen
Trying to connect the dots between Content Marketing and Marketing Automation? Join DemandGen for another exploration of B2B Marketing Automation best practice. This webcast will be looking at the relationship between Content Marketing and Marketing Automation. We’ve put together another panel of smart b2b practitioners. This month’s insights are provided by Doug Kessler of Velocity Partners, author of The B2B Content Marketing Workbook and Bob Apollo, founder of Inflexion-Point, B2B Sales and Marketing Performance Improvement specialists.
We’ll be taking a closer look at the relationship between Marketing Automation and Content Marketing:
- Rules of thought leadership
- Aligning content to the buying cycle
- Best practices: Building an integrated content marketing strategy with Marketing Automation tools
- B2B content marketing examples and successes
- Measuring the results
The document outlines six common ways startups can fail and provides advice on how to succeed instead. It discusses how startups should not try to operate like large companies by following traditional models. Startups need to search for an unknown business model rather than execute a known one. The key is getting out of the building to test hypotheses through customer development, building minimal viable products, and pivoting based on feedback.
Startup camp chalmers innovation 19 september 2014sahlinas
This document discusses business models and customer development for startups versus established companies. It begins by defining companies as organizations that sell products or services for profit, organized around business models. Startups are defined as temporary organizations designed to search for a repeatable and scalable business model. The document then discusses how companies execute business plans while startups search for their business model through customer development. It advocates that startups focus on searching for the right business model rather than executing a predetermined plan.
Introduction to Customer Development at the Lean Startup Intensive at Web 2.0...Eric Ries
The document discusses customer development and the search for a business model in startups. It emphasizes testing hypotheses with customers to validate problems and solutions. There are three types of markets - existing, resegmented, and new - that require different sales, marketing and business development approaches. The key ideas are to parallel customer development with product development using measurable checkpoints tied to customer milestones rather than just product shipments. The goal is to prove a repeatable and scalable business model before scaling the company.
This document summarizes an entrepreneur's process of validating a business idea for an autonomous weeding robot. Through interviews with 75 customers in 8 weeks, the entrepreneur learned that the biggest problem was weeding in organic crops. A minimum viable product called "CarrotBot" was built to collect machine vision data. Further customer validation revealed that both farmers and weeding service providers would be interested customers. The business model was updated to target mid-large organic farmers, agricultural corporations, and weeding service providers with a solution that reduces labor costs through automation.
The Northfront Entrepreneur Alliance is a entreprenuer networking association in Northern Utah. This presentation was given on 04.06.11 to the group by Rob Kunz- a successfull entrepreneur, investor., and co-founder of BoomStartup. He discusses the Lean Startup Business Model and how to apply it.
Steve Budra has extensive experience leading marketing strategies that have generated significant revenue growth for companies. As highlighted in testimonials, he is praised for his creativity, vision, ability to execute plans, and delivering great results. His background includes tripling revenues for a graphic arts supplier through rebranding and international expansion, and increasing product revenue 400% for a business forms manufacturer through affiliate partnership strategies.
Similar to Henrik Berglund, Venture Cup, feb 2013 (20)
1. Business Models/Customer Development
Henrik Berglund
Chalmers University of Technology
Center for Business Innovation
henber@chalmers.se
www.henrikberglund.com
@khberglund
2013-02-15 1
2. Presentation based on
by Steve Blank and Bob Dorf
More info: www.steveblank.com
Buy the book: http://www.amazon.com/gp/product/0984999302/
27. Traditional Development Process
Has Two Implicit Assumptions
Customer Problem: known
Concept Product Dev. Alpha/Beta Launch/
Test 1st Ship
Product Features: known
Works well for incremental development projects
targeting existing customers.
28. Tradition – Hire Marketing
Concept Product Dev. Alpha/Beta Launch/
Test 1st Ship
- Create Marcom - Hire PR Agency - Create Demand
Marketing Materials - Early Buzz - Launch Event
- Create Positioning - “Branding”
29. Tradition – Hire Sales
Concept Product Dev. Alpha/Beta Launch/
Test 1st Ship
- Create Marcom - Hire PR Agency - Create Demand
Marketing Materials - Early Buzz - Launch Event
- Create Positioning - “Branding”
- Hire Sales VP - Build Sales
Sales - Hire 1st Sales Staff Organization
30. Tradition – Hire Business Development
Concept Product Dev. Alpha/Beta Launch/
Test 1st Ship
- Create Marcom - Hire PR Agency - Create Demand
Marketing Materials - Early Buzz - Launch Event
- Create Positioning - “Branding”
- Hire Sales VP - Build Sales
Sales - Hire 1st Sales Staff Organization
Business - Hire First Bus Dev - Do deals for FCS
Development
32. What’s wrong with this picture?
Concept Product Dev. Alpha/Beta Launch/
Test 1st Ship
• Both Customer Problems and Product Features
are hypotheses
• Emphasis on execution rather than learning and
discovery
• No relevant milestones for marketing and sales
• Often leads to premature scaling and a heavy
spending hit if product launch fails
You do not know if you are wrong until you
are out of money/business
33. Concept Product Dev. Alpha/Beta Launch/
Test 1st Ship
- Create Marcom - Hire PR Agency - Create Demand
Marketing Materials - Early Buzz - Launch Event
- Create Positioning - “Branding”
- Hire Sales VP - Build Sales
Sales - Hire 1st Sales Staff Organization
Business - Hire First Bus Dev - Do deals for FCS
Development
35. Product and Customer Development
Product Development
Concept Product Dev. Alpha/Beta Launch/
Test 1st Ship
+
Customer Development
Customer Customer Customer Company
Discovery Validation Creation Building
37. Search Execution
Strategy Business Model
Operating Plan +
Hypotheses
Financial Model
Process Customer & Product Management
& Waterfall Development
Agile Development
43. Founders run a
Customer Development Team
No sales, marketing and business
development
44. Search Execution
Strategy Business Model
Operating Plan +
Hypotheses
Financial Model
Customer Development, Product Management
Process
Agile Development Agile or Waterfall Development
Customer Functional Organization
Organization
Development Team, by Department
Founder-driven
46. Business Model
Key activities Value proposition Customer
relationships
Key partners
Customer
segments
Cost Key Channels Revenue
structure resources streams
http://www.businessmodelalchemist.com/
47. Business Model
Key activities Value proposition Customer
relationships
Key partners
Customer
segments
Cost Key Channels Revenue
structure resources streams
A framework for making your assumptions explicit
49. Customer Segments
Who is the customer?
Multi-sided market?
Different from user?
http://www.businessmodelalchemist.com/2012/08/achieve-product-market-fit-with-our-brand-
new-value-proposition-designer.html
50. Customer Segments
- jobs to be done
What functional jobs is your customer
trying get done? (e.g. perform or
complete a specific task, solve a specific
problem…)
What social jobs is your customer trying
to get done? (e.g. trying to look good,
gain power or status…)
What emotional jobs is your customer
“What jobs are the customers you are
trying get done? (e.g. esthetics, feel good,
targeting trying to get done”
security…)
51. Customer Segments
- customer pains
What does your customer find too costly?
(e.g. takes a lot of time, costs, effort)
What makes your customer feel bad?
(e.g. frustrations, annoyances)
How are current solutions under-
performing for your customer?
(e.g. lack of features, performance,
malfunction) “What are the costs, negative emotions, bad
situations etc. that your customer risks
What negative social consequences does experiencing before, during, and after getting
your customer encounter or fear? the job done.”
(e.g. loss of face, power, trust, or status)
52. Customer Segments
- customer gains
Which savings would make your customer
happy? (e.g. in terms of time, money and
effort)
What would make your customer’s job or
life easier? (e.g. flatter learning curve,
more services, lower cost of ownership)
What positive social consequences does
your customer desire? (e.g. makes them
look good, increase in power, status)
“What are the benefits your customer
expects, desires or would be surprised by.”
What are customers looking for? (e.g.
good design, guarantees, features)
What do customers dream about? (e.g.
big achievements, big reliefs)
55. Value Propositions
Can your product/service:
• Produce savings?
• Make your customers feel
better?
• Put an end to difficulties?
• Wipe out negative social
consequences?
56. Value Propositions
Can your product/service:
• Outperform current
solutions?
• Produce outcomes that go
beyond their expectations?
• Make your customer’s job
or life easier?
• Create positive social
consequences?
60. How Do You Want Your Product to Get to
Your Customer?
Yourself
Through someone else
Retail
Wholesale
Bundled with other goods or services
60
63. How Does Your Customer Want to Buy
Your Product from your Channel?
• Same day
• Delivered and installed
• Downloaded
• Bundled with other
products
• As a service
• …
63
71. Key activities Value proposition Customer
relationships
Key partners
Customer
Visualization of the segments
business model
framwork
Cost Key Channels Revenue
structure resources streams
83. The goal is not to remain a startup
Large
Startup Transition
Company
The goal of a startup is to become a large company!
Failure = failure to transition.
88. …they focus on executing the plan…
Concept Product Dev. Alpha/Beta Launch/
Test 1st Ship
• Both Customer Problems and Product Features
are hypotheses
• Emphasis on execution rather than learning and
discovery
• No relevant milestones for marketing and sales
• Often leads to premature scaling and a heavy
spending hit if product launch fails
You do not know if you are wrong until you
are out of money/business
90. … and end up going bust.
“We have been too visionary. We
wanted everything to be perfect, and
we have not had control of costs"
Ernst Malmsten
(BBC News, May 18 2000)
93. Customer Development: Key Ideas
• Parallel process to Product Development (agile)
• Measurable checkpoints not tied to FCS but to customer
insights
• Emphasis on iterative learning and discovery before execution
• Must be done by small team including CEO/project leader
94. Customer Development Heuristics
• There are no facts inside, so get out of the building!
• Earlyvangelists make your company, and are smarter than you!
• Develop a minimum viable product to maximize fast learning.
95. Customer Development: Four Stages
search
execution
• Customer Discovery
Articulate and Test your Business Model Hypotheses
• Customer Validation
Sell your MVP and Validate your MB & Sales Roadmap
• Customer Creation
Scale via relentless execution and fill the sales pipeline
• Company Building
(Re)build company’s organization & management
96. Customer Discovery
• Articulate and test
your BM hypotheses
(value prop/customers key)
• No selling, just listening
• Must be done by founder
103. Test Customer Problem Hypotheses
”Do you have this ”Tell me about it, how
problem?” do you solve it today?”
1. 1.
2. 2.
3. 3.
104. Test Customer Problem Hypotheses
”Do you have this ”Tell me about it, how ”Does something like this
problem?” do you solve it today?” solve your problem?”
1. 1. 1.
2. 2. 2.
3. 3. 3.
Listen carefully to what they say at each step!
Focus on learning - Don’t try to sell them on your idea!
In the process you find out about other BM parts as well:
workflow, benefits (to users & others), preferred channels, critical
influencers, respected peers etc…
You want to become a domain expert!
105. Finding people
Introductions (ask everyone you know)
• Provide the exact text that they can copy and paste into
a tweet or email (They’re doing you a favor! Make it as
easy as possible for them)
• Tell them exactly how you are going to communicate
with their contacts (They’re risking a bit of social capital
for you. Be very clear that you won’t spam or annoy
people)
• Tell them your goals (What do you think you’ll get/learn
if they make this intro for you? People want to know
that they’re contributing to a bigger picture!)
106. Finding people
AdWords, Facebook Ads, Promoted Tweets
Summarize your idea and get it in front of people who have
expressed an interest in it by having searched for your
keywords and clicked your ad – get conversations (and/or
test hypotheses using landing pages).
http://www.cindyalvarez.com/best-practices/customer-
development-interviews-how-to-finding-people
107. Finding people
Twitter Search
Look for people who have already discussed a similar
product, problem, or solution and address a tweet directly
to them:
“@username Would love yr feedback on
[product/problem/solution] – shd only take 2mins [URL]
thanks!”
108. Finding people
Google Alerts
Set up Google Alerts for your product/problem/solution –
when it finds relevant blog posts or comments, email and
ask for feedback:
“I read your [post/comment] about
[product/problem/solution]. I’m currently working on a
related idea and I think your opinion would be very
valuable to me – could you take 2 minutes and check
out [URL]? Thank you – I’d be happy to return the favor
any time.”
110. Web
Much faster to build =>
get quantitative feedback sooner.
Use a low-fi landing page as substitute for –
and introduction to – conversations.
Key to drive traffic through
AdWords/Facebook Ads/Promoted Tweets
etc.
Build (design test), measure (run test) and
analyze (evaluate test)!
113. Reality check!
CustDev and ProdDev teams meet and discuss
the lessons learned from the field.
”Here is what we thought about customers and
their problems, here is what we found out”
BM hypotheses, product specs or both are jointly
revised.
114. Test Solution Hypothesis
1) ”We believe you have this important problem”
– listen (check).
2) Demo how your product solves the problem. Focusing
on a few key features.
Include workflow story: ”life before our product” and
”life after our product” – listen!
3) ”What would this solution need to have for you to
purchase it?” Listen, ask follow up questions.
116. Dropbox
• 1st solution test: a three minute video made in the
founder’s apartment before a complete code was
written.
– Generated valuable feedback from visionary customers.
• 2nd solution test: another video of the product that was
posted on a social network.
– Waiting list jumped from 5 000 to 75 000.
• Dropbox’s original intent was to build and ship their
product in eight weeks.
• Instead, they gathered feedback and launched a public
version 18 months later.
118. Test Product Hypotheses
After demoing, ask about other things:
Positioning – how do they describe the product?
Product category (new, existing, resegmented)
Competitors
Features needed for first version
Preferred revenue model
Pricing
Additional service needs
Marketing – how do they find this type of product?
Purchasing process
Who has a budget?
etc.
119. Web
Build out a high-fidelity web page with “functioning”
back-end, based on lessons learned.
“Mechanical Turk”-solution.
Ask for money: first “pre-order” then charging.
Continue to test, measure and analyze!
121. Reality check!
CustDev and ProdDev teams meet and discuss
the lessons learned.
”Here is what we thought about product
features and here is what we found out”
BM hypotheses, product specs or both are again
jointly revised.
122. Customer Discovery: Exit Criteria
What are your customers top problems?
How much will they pay to solve them?
Does your product concept solve them?
Do customers agree?
How much will they pay for it?
Can you draw a day-in-the-life of a customer?
Before & after your product
Can you draw the org charts of users, buyers
and channels?
123. Customer Validation
• Develop and sell MVP to passionate earlyvangelists
• Validate a repeatable sales roadmap
• Verify the business model
124. Minimal Viable Product
Based on your insights from Customer Discovery, sell
the smallest feature set customers are willing to pay
for!
• Purpose 1: Reduce wasted engineering hours
(and wasted code)
• Purpose 2: Get something into the hands of
earlyvangelists as soon as possible => maximize
learning!
125. The Apple I, Apple’s first product, was sold as an assembled circuit board
and lacked basic features such as a keyboard, monitor and case.
126. The owner of this unit added a keyboard and a wooden case.
http://en.wikipedia.org/wiki/Apple_Inc.
128. Minimal Viable Product
The MVP is not the goal = Requires commitment
to iteration!
• “A complex system that works is invariably
found to have evolved from a simple system
that worked.”
• “A complex system designed from scratch
never works and cannot be made to work.
You have to start over, beginning with a
working simple system.”
129. Types of earlyvangelists
Not
1. Has a problem
helpful
2. Understands he or she has a problem
3. Actively searching for a solution
4. Cobbled together an interim solution
5. Committed and can quickly fund Jackpot!
a solution
130. Customer Validation: Exit Criteria
Do you have a proven sales roadmap?
Organization chart? Influence map?
No staffing until roadmap is proven!
Do you have a set of orders ($’s) of the
product validating the roadmap?
Is the business model scalable?
LTV > CAC, Cash
132. If no – Pivot!
• The heart of Customer Development
• Change without crisis
(and without firing executives)
“The idea that successful startups change directions but
stay grounded in what they've learned”
137. Pivot
Adapt the Business Model
until you can prove it
works
139. Customer Creation
• Grow customers from few to many
• Comes after proof of sales
• Inject $’s for scale
• This is where you “cross the chasm”
• “Growth Hacking”
140. Company Building
• (Re)build company’s organization & management
• Dev.-centric Mission-centric Process-centric
141. Summary – Customer Development
• Customer Discovery
Articulate and Test your Business Model Hypotheses
• Customer Validation
Sell your MVP and Validate your BM & Sales Roadmap
• Customer Creation
Scale via relentless execution and fill the sales pipeline
• Company Building
(Re)build company’s organization & management
142. Don’t do a Boo!
Concept Product Dev. Alpha/Beta Launch/
Test 1st Ship
“We have been too visionary. We
wanted everything to be perfect, and
we have not had control of costs"
Ernst Malmsten
(BBC News, May 18 2000)
143. Tack!
Henrik Berglund
Chalmers University of Technology
Center for Business Innovation
henber@chalmers.se
www.henrikberglund.com
@khberglund
2013-02-15 143
144. Presentation based on
by Steve Blank and Bob Dorf
More info: www.steveblank.com
Buy the book: http://www.amazon.com/gp/product/0984999302/
Most Value Propositions compete with others for the same Customer Segment. I like thinking of this as an “open slot” that will be filled by the company with the best fit.
The user problem you’retryingtosolve. How the userencountersyour solution.Howyour solution willwork (from the user’sperspective). How the userwill benefit.
thepoint, a now largely inactive site primarily for activists and philanthropists who wanted to encourage like-minded people to invest and support their causes. http://www.thepoint.com/