-
Customer Discovery
-
NOT-TO-DOs
- Understand the needs and wants of ALL customers
- Make a list of ALL the features customers want before they buy your product
- Hand Product Development a features list of the sum of all customer requests
- Hand Product Development a detailed marketing requirements document
- Run focus groups and test customers' reactions to your product to see if they will buy
- Instead, you are going to develop your product for the few, not the many.
- You are going to start building your product even before you know whether you have any customers for it
-
Earlyvangelists
- Has a problem
- Is aware of having a problem
- Has been actively looking for a solution
- Has put together a cobbled up solution
- Has or can acquire a budget
- Phase 0: Get buy-in from all stakeholders
-
Phase 1: State hypotheses
-
Product hypothesis
- Product features
- Product benefits
- Intellectual property
- Dependency analysis
- Product delivery schedule
- Total cost of ownership/adoption
-
Customer & problem hypothesis
-
Types of customers
- End-users
- Influencers
- Technical buyer
- Recommenders
- Saboteurs
- Economic buyer
- Decision maker
- Customer problems
- A-day-in-a-life of your customer
- Organizational map and customer influence map
- ROI justification
-
Minimum feature set
- A very small group of early visionary customers will guide your follow-on features
- Less is more, to ship earlier
- What is the smallest, least complicated problem that the customer will pay us to solve?
- Distribution & pricing hypothesis
-
Demand-creation hypothesis
-
Creating customer demand
- The further away from a direct sales force your channel is, the more expensive your demand-creation activities are
- You need to understand HOW your customers hear about new companies and products
- Trade shows?
- Magazines?
- Analysts
-
Influencers
- Analysts?
- Press?
- Visionaries?
-
Market type hypotheses
-
Type of Startup Markets
- 1. Customers
- Existing
- New
- Existing
- Existing
- 2. Customer needs
- Performance
- Simplicity and convenience
- Cost
- Perceived need
- 3. Performance
- Better/faster
- Low in "traditional" attributes; improved by new customer metrics
- Good enough at the low end
- Good enough for new niche
- 4. Competition
- Existing incumbents
- Non-consumption, other startups
- Existing incumbents
- Existing incumbents
- 5. Risks
- Existing incumbents
- Market adoption
- Existing incumbents
- Niche strategy fails
-
Existing market
- Ask
- Is there an established and well-defined market with large numbers of customers?
- Does your product have a better "something" that existing competitors?
- Brief
- Who are the competitors and who is driving this market?
- What is the market share of each competitor?
- What is the total marketing an sales dollars the market share leaders will be spending to compete with you?
- Do you understand the cost of entry against incumbent competitors?
- Since you are going to compete on performance, what performance attributes have customers TOLD YOU are important?
- Wat percentage of this market do you want to capture in years 1 throuth 3?
- How do the competitors define the market?
- Are there existing standards? If so, whose agenda is driving the standards?
- Do you want to embrace these standards, extend them or replace them?
-
Resegmented market
- Ask
- Is there an established and well-defined market with large numbers of customers and your offering is lower cost than the incumbents?
- Is there an establshed and well-defined market with large numbers of customers and your product can be uniquely differentiated from the existing incumbents?
- Brief
- What existing markets are your customers coming from?
- What are the unique characteristics of those customers?
- What compeling needs of those customers are unmet by existing suppliers?
- What compelling features of your product will get customers of existing companies to abandon their current supplier?
- Why couldn't existing vendors offer the same thing?
- How long will it take you to educate potential customers and to grow a market of sufficient size? (What size is that?)
- How will you educate the market?
- How will you create demand?
- Given that no customers yet exist in your new segment, what are realistic forecasts for year 1-3?
-
New market
- Ask
- Is there no established and well-defined market?
- Are there no existing competitors?
- Brief
- What are the adjacent markets, closest to the new one you're creating?
- What markets will potential customers come from?
- What compelling need will make customers use/buy your product?
- What compelling feature will make them use/buy your product?
- How long will it take you to educate potential customers to grow a market of sufficient size? (What size is that?)
- How will you educate the market?
- How will you create demand?
- Given that no customers yet exist what are realistic forecasts for years 1-3?
- How much financing will it take to soldier on while you educate and grow the market?
- What will stop a well-heeled competitor from taking the market from you once you've developed it?
-
Competitive hypothesis
-
Existing market
- The basis of competition is all about some atribute(s) of your product.
-
State of market
- Fragmented: all players have 30% or less of the market
- Monopolized: a player has 80% or more of the market
-
Ask
- How have the existing competitors defined the basis of competition? (features? service?)
- Why do you believe your company and product are different?
- What makes you think that customers will care about your new, unique "killer" feature? performance? channel? price?
- If this were a grocery store, which products would be shelved next to yours?
- Who are you closest competitors today? in features? performance? channel? price?
- Where do customers go today to get the equivalent of what you offer?
- What do you like most about each of your competitor's product? What do customers like most?
- If you could change one thing in your competitor's product, what would it be?
- Who uses the competing product today, by title/function? How do they use it?
- Describe the workflow/design flow for an end-user
- What percentage of their time do end-users spend with your competitor's product?
- How mission critical is it?
- For lack of your product, what do people do today without it? Do they simple not do something or do they do it badly?
-
Phase 2: Test problem hypotheses
-
Friendly first contacts
-
Make a list of 50 potential customers you can test your ideas on
- Get referrals
- Prepare a "reference story"
- Paragraph 1: describe your company
- Paragraph 2: describe what you're doing
- Paragraph 3: what's in it for them
- The goal is to get 5-10 visits lined up
-
Start an innovators list
- Advisory board candidates
- Industry influencers
-
Network your way up the "food chain of expertise" in your space
- "Who's the smartest person you know in this space?"
-
"Problem" presentation
-
Present problem(s)
- What do they think the problems are?
- Are we missing any problems?
- How would they rank-order the problems?
-
Existing solutions
- How do they deal with the problem today?
- How do they think others address it?
- Who else shares these problems in the company?
-
Our solutions
- Describe the "big" solution (not specific features)
- Do they understand what the words mean?
- Is the solution evident enough?
-
In-depth customer understanding
-
How does the workflow/design flow happens?
- How to customers actually spend their day?
- How do they spend money?
- How do they get the job done?
-
Will they pay for your solution?
- What would make customers change the current way of doing things? Price? Features?
-
If you had a product like this... ?
- What percentage of your time could be spent using this product?
- How mission-critical is it?
- Would it solve the pain you mentioned earlier?
- What would be the barrirs to adopting a product like this?
-
How do they learn about new products?
- What analysts do they follow?
- Who they they trust in the press?
- What magazines do they read?
- What orgranizations they belong to?
- Do they get their news from Twitter?
-
Spot talent
- Can these customers be helpful in the future?
- Could they help the next round of conversations?
- Could they contribute in an Advisory position?
- Could they become a paying customer?
- Could they give you referrals?
-
Market knowledge
-
Meet with
- Potential customers
- Peers in adjacent markets
- Key industry influencers and recommenders
- Gather quantitative data
- Attend industry conferences and trade shows
-
Ask
- What the industry trends?
- What are key unresolved customer needs?
- Who are the key players in this market?
- What should I read?
- Who should I know?
- What should I ask?
- What customers should I call on?
-
Phase 3: Test product concept
-
First reality check
-
Reality check your customer hypothesis
- Gather all customer data
- Build a workflow map of typical customer
- Diagram who works with whom
- Compare to original customer hypotheses
-
Product Dev/Customer Dev sync meeting
- Adjust assumptions
- Adjust specs
-
Reality check the "problem" assumptions
- What problems do customers SAY they have?
- How painful were these problems?
- Where on the "problem scale" were the customers you interviewed?
- How are they solving these problems today?
-
Draw the customer workflow with and without your product!
- Was the difference dramatic?
- Did customers say they would pay for that difference?
- What did you learn about customers' problems?
- What were the biggest surprises?
- What were the biggest disappointments?
-
Given all this, how close were out assumptions? spec?
- Do we talk to a different set of customers?
- Are we building the wrong product?
- Should we continue building it and hope for a miracle?
- Do we change the product?
-
If product addresses part of the problem
- Review the feature list
- Prioritize the features in terms of importance to the customer
- Can we match each feature to an explicit customer problem?
- Which features did customers not care about?
- Can any features be deleted or deferred?
-
Review and get agreement on the delivery schedule
- All features beyond the first version are up for grabs
- Features spec'd in release 1.0 are subject to change/deletion to get the product out as early as possible
-
Review your other Phase 1 hypotheses
- Which market type are you in?
- Why are you different?
- What will be your basis for competing?
- Do your pricig and delivery channel assumptions hold up?
- What did you learn about influencers?
-
Prepare product presentation
-
Goal
- Test revised product assumptions
- Validate your product features
- Cover the five (no more!) key product features
- Describe the customer's live "before" and "after" your product
- A day-in-a-life with and without your product
- LEAVE OUT ALL THE MARKETING, POSITIONING AND FLUFF
- Present the product roadmap
-
More customer visits
- This time, you do want to present to the people/roles who will be involved in the purchasing decision.
- Create introductory email, reference story and sales script
- Restate the problem your product is designed to solve
- Describe why it is important to address this problem
-
Get agreement on the value of solving this problem
- If you don't get agreement, go back to Phase 2
- Describe your product
- Demo as many of its key features as you can
- Draw customer workflow with/without your product
- Describe who else in the customer organization your product may affect
- Shut up and listen
-
Second reality check
-
Reality check your customer hypothesis
- Gather all customer data
- Build a workflow map of typical customer
- Diagram who works with whom
- Compare to original customer hypotheses
-
Product Dev/Customer Dev sync meeting
- Adjust assumptions
- Adjust specs
-
Reality check the "problem" assumptions
- What problems do customers SAY they have?
- How painful were these problems?
- Where on the "problem scale" were the customers you interviewed?
- How are they solving these problems today?
-
Draw the customer workflow with and without your product!
- Was the difference dramatic?
- Did customers say they would pay for that difference?
- What did you learn about customers' problems?
- What were the biggest surprises?
- What were the biggest disappointments?
-
Given all this, how close were out assumptions? spec?
- Do we talk to a different set of customers?
- Are we building the wrong product?
- Should we continue building it and hope for a miracle?
- Do we change the product?
-
If product addresses part of the problem
- Review the feature list
- Prioritize the features in terms of importance to the customer
- Can we match each feature to an explicit customer problem?
- Which features did customers not care about?
- Can any features be deleted or deferred?
-
Review and get agreement on the delivery schedule
- All features beyond the first version are up for grabs
- Features spec'd in release 1.0 are subject to change/deletion to get the product out as early as possible
-
Review your other Phase 1 hypotheses
- Which market type are you in?
- Why are you different?
- What will be your basis for competing?
- Do your pricig and delivery channel assumptions hold up?
- What did you learn about influencers?
- First advisors
- Phase 4: Verify
- Customer Validation
- Customer Creation
- Company Building