The debate between shareholder primacy and stakeholder theory concerns the legal obligations of corporate directors. Introduction A corporation is never just a machine for making money. It is a legal institution, a social system, and a vehicle for allocating power, risk, and responsibility. That is why one of the most important debates in corporate governance continues to divide scholars, executives, regulators, and investors: should corporations exist primarily to maximize shareholder value, or should they balance the interests of all the people and institutions affected by their actions? This debate is commonly framed as shareholder primacy vs. stakeholder theory. Shareholder primacy says the corporation's central obligation is to its owners, the shareholders. Stakeholder theory says the corporation owes duties to a wider circle of affected parties, including employees, customers, suppliers, creditors, communities, and sometimes society at large. This is not a purely academ...
This post explains market validation and customer discovery as a single sequence: find the problem, test whether anyone will pay to solve it, and confirm the answer with evidence rather than opinion. It covers the customer-discovery interview, the problem-solution fit test, and the minimum viable product. The post tests the method against Airbnb’s early growth in San Francisco and M-KOPA’s pay-as-you-go solar rollout in Kenya.
By Kateule Sydney — Researcher and Writer | Last Verified: 2026-09-28 | Published by Kat-Syd Resources Hub
Market validation runs in sequence: problem, solution, evidence.
Table of Contents
Market Validation Tests Whether Anyone Will Pay
Definition
Market validation is the process of confirming, with evidence gathered from real potential customers, that a market exists for a proposed product or service at a price the customer will pay. Steve Blank defined the discipline in The Four Steps to the Epiphany, published in 2005, as the search for a repeatable and scalable business model before the business commits serious capital to execution.
The three components of market validation are these:
- Problem validation — evidence that the problem the product solves is real, urgent, and felt by a specific group of people.
- Solution validation — evidence that the proposed solution is preferred over the alternatives the customer already uses.
- Willingness to pay — evidence that the customer will exchange money for the solution at the price the firm needs to charge.
The order matters. A founder who validates the solution before the problem is testing a product nobody needs. A founder who validates willingness to pay before the solution is testing a price for a product the customer has not yet seen.
A complete market-validation exercise moves through four stages:
- Hypothesis — state the assumption about who has the problem and why.
- Interview — speak to at least twenty potential customers in the target segment.
- Test — offer a landing page, a pre-order, or a paid pilot to measure actual interest.
- Decision — proceed, pivot, or stop, on the basis of what the evidence showed.
Market validation is a search, not a sales pitch. A founder who treats it as a sales pitch will get agreement from every customer and learn nothing.
Customer Discovery Interviews Replace Assumptions With Evidence
Definition
Customer discovery is the interview process through which a founder tests assumptions about the customer’s problem, current behaviour, and buying criteria. Steve Blank and Bob Dorf set out the method in The Startup Owner’s Manual, published in 2012, as the first phase of the customer-development model.
The three components of a customer-discovery interview are these:
- Past behaviour — what the customer has already done about the problem, and how much it has cost them.
- Current workaround — the tool, service, or manual process the customer uses today in place of a purpose-built solution.
- Buying criteria — the conditions under which the customer would change from the workaround to a new product.
The most common mistake in customer discovery is asking the customer what they want. Customers describe ideal products they will never buy. Key point: the interview must ask about what the customer has already done, not what they would do, because past behaviour is evidence and future intention is not.
A customer-discovery interview runs in three phases:
- Warm-up — establish the customer’s context and role without leading the answer.
- Problem probe — ask what the customer does today, what it costs, and what frustrates them about it.
- Commitment test — ask for a small commitment, such as a follow-up meeting or an introduction, to test real interest.
The interview is a research instrument. A founder who talks for more than twenty percent of the interview has stopped researching and started pitching.
Case Study
Airbnb and M-KOPA illustrate market validation from opposite ends of the income scale. Airbnb validated a solution to an unserved demand for short-term accommodation in cities hosting sold-out events. M-KOPA validated a solution to an unserved demand for off-grid electricity in rural Kenya, where the existing workaround was kerosene.
Airbnb founders Brian Chesky and Joe Gebbia launched the first listing in 2007 during a design conference in San Francisco when every hotel room in the city was booked. The initial test was three air mattresses in their apartment. They validated the demand with a single event, then repeated the test in New York, where they went door to door to help hosts photograph their listings. Airbnb reported 4 million guests in 2015, 150 million in 2018, and over 2 billion cumulative guest arrivals by 2024 in its annual reports. M-KOPA launched in Kenya in 2012 with a pay-as-you-go solar home system financed by mobile-money repayments of roughly fifty United States cents per day. The customer-discovery insight was that rural households spent a comparable amount daily on kerosene, so the product replaced an existing expense rather than adding a new one. M-KOPA reported over one million customers across Kenya, Uganda, Nigeria, and Ghana by 2018 and over four million by 2023 according to its annual impact reports. [VERIFY: confirm the current M-KOPA customer figure and year against the most recent annual impact report before publication.]
Airbnb and M-KOPA prove the same point from different segments. Airbnb succeeded because the first test was small enough to run in a weekend and specific enough to measure. M-KOPA succeeded because the customer-discovery interview identified the workaround — kerosene — and priced the solution against it rather than against nothing. Market validation is not a market study. It is a series of small, cheap tests, each one designed to produce evidence that a larger commitment either is or is not justified.
The Minimum Viable Product Tests the Solution, Not the Idea
Definition
A minimum viable product is the smallest version of a product that allows a team to collect the maximum amount of validated learning about customers with the least effort. Eric Ries defined the term in The Lean Startup, published in 2011, as the central instrument of the build-measure-learn feedback loop.
The two components of a minimum viable product are these:
- Minimum — the smallest feature set that lets a customer complete the core action the product is designed for.
- Viable — complete enough that the customer would use it more than once, and would pay for it.
Most minimum viable products are neither minimum nor viable. They are either too complete, which wastes money on features customers have not asked for, or too incomplete, which produces a false negative when the customer rejects a product that was never functional.
The five principles I recommend for building a minimum viable product are these:
- State the learning goal — the specific question the test is designed to answer.
- Ship the smallest version — one core action, completed end to end.
- Recruit real users — customers from the target segment, not friends or colleagues.
- Measure behaviour — usage, retention, or payment, not opinions gathered after the fact.
- Set the pass or fail line before launch — the threshold above which the team proceeds.
A minimum viable product is a test, not a product. Its purpose is to answer a question, and a test that cannot be failed is not a test.
Validated Learning Turns Discovery Into a Measurable Process
Definition
Validated learning is the process of demonstrating, with data from real customer behaviour, that a team has discovered something true about its market. Eric Ries introduced the term in The Lean Startup as the unit of progress in early-stage ventures, in place of the traditional measures of product shipped or features built.
Progress in validated learning is measured in knowledge, not in activity. A team that has built twelve features has learned nothing unless the features produced data that changed a decision. A team that has run three tests and killed two of them has learned more than a team that has launched a single product and hoped for the best.
The three-element framework I recommend for tracking validated learning is this:
- Learning log — a written record of each assumption tested, the evidence produced, and the decision taken.
- Decision cadence — a fixed interval, usually two to four weeks, at which the team reviews the log and updates the plan.
- Kill criteria — a stated condition under which the team stops the project rather than continuing to test.
I recommend that validated learning be recorded in the same document as the business plan itself, so that every claim in the plan is traceable to evidence the team has gathered. A plan that cites customer interviews, pilot data, or payment records is a plan that has earned its numbers. A plan that cites only market reports and intuition has not yet begun the validation process.
Conclusion
The case evidence establishes that market validation and customer discovery are a single process designed to reduce uncertainty before capital is spent. Airbnb and M-KOPA both began with small tests against a defined problem, and both scaled only after the evidence confirmed the underlying demand.
Market validation matters because a business plan is a claim about future revenue, and every claim about the future must be supported by evidence from the present. The process is supposed to produce four outputs: a validated problem statement, a validated solution description, a price the customer has agreed to pay, and a log of the tests that produced each of those conclusions. It applies whenever a founder or team proposes to build something new, whether at start-up, within a corporate innovation unit, or at the launch of a new product line. The people responsible are the founder and the product lead, with the support of a research or data function where one exists. The method is to state the assumption, interview twenty customers in the target segment, build the smallest product that tests the assumption, measure real behaviour, and record the outcome in writing before deciding to proceed, pivot, or stop. The advantage of this discipline is that it catches the fatal error early, at a cost the founder can afford, and it produces the evidence base for the financial projections in the plan. The limitation is that validation takes time a founder may not have, interviews produce biased answers if the founder leads the conversation, and a test that succeeds in a small sample may still fail when the product scales to the full market.
The recommendations I would give any founder or product lead conducting market validation and customer discovery are these:
- Interview twenty customers before building anything — a sample smaller than twenty produces anecdotes, not evidence.
- Ask about past behaviour, not future intent — what the customer has already done is evidence; what they say they would do is not.
- Set the pass or fail line before the test begins — a test without a threshold is a demonstration.
- Charge real money as early as possible — a pre-order or a paid pilot is the strongest form of validation available.
- Keep a written learning log — every assumption, every test, every decision, in one document that feeds the business plan.
Market validation is not a phase that ends when the product launches, and the founders who treat it as a permanent discipline are the ones who survive the first two years.
References
- Blank, S. — The Four Steps to the Epiphany — K&S Ranch, 2005
- Blank, S. & Dorf, B. — The Startup Owner’s Manual — K&S Ranch, 2012
- Ries, E. — The Lean Startup — Crown Business, 2011
- Airbnb — Company Milestones and Guest Arrivals Data — Airbnb Newsroom
- M-KOPA — Annual Impact Reports and Customer Data — M-KOPA Solar
Read Also on Kat-Syd Resources Hub
Entrepreneurship and Innovation Part I — Ideation and Opportunity Recognition — how opportunity recognition precedes market validation in the wider process.
Developing the Business Plan — Entrepreneurship and Innovation Part II — where validated learning feeds the market section of the plan.
Functional Management — The Pillars — how marketing, operations, finance, and human resources support the product once it is validated.
Written by Kateule Sydney — Researcher and Writer
© 2026 Kat-Syd Resources Hub. All rights reserved.
Kat-Syd Resources Hub — Educational case studies and analytical reference