From Idea Hypothesis to PMF

A Practical Framework: Problem -> Solution -> Commercialization#

Starting a business is really less about grand technology or flashy demos, and more about figuring out "why this problem needs to be solved right now."
Some days, a single comment like "I don't think I really need that" from a customer interview shakes your confidence. Other days, a short piece of feedback completely redirects your week.
The core is simple: precisely define the problem, build a solution that gets adopted, design a structure that sells, and keep validating PMF in an ongoing cycle. I've put together the questions and checklists that fill in the gaps along the way.

1) Idea Hypothesis: The Size of the Problem Matters More Than the Solution#

People experience inconveniences. But not every inconvenience gets promoted to a "problem that needs solving right now." When this boundary gets blurry, the team ends up piling on fancy features only to face customer indifference. That's why the starting point is always problem definition. Who, when, in what context, how often, and how badly are they hurting? And what substitutes are they currently using, where does their dissatisfaction with those substitutes begin -- you absolutely have to pin this down with numbers and examples.

• How often and how severely does the customer experience this problem?
• What's the cost of not solving it (time/money/emotion)?
• What are the existing alternatives, and what's unsatisfying about them?

If you succeed in seeing the problem "as it truly is," the solution naturally becomes simple.
Conversely, if you define the problem vaguely, the solution becomes complicated.

2) Solution Design: It's Not About Technology -- It's About Reasons for Adoption#

A solution doesn't need to look impressive. It just needs a crystal-clear "reason why I should use this right now." Focus on the segments customers care about most, and define the benefits clearly in the language of cost, time, quality, and risk. Adoption friction is highest at the first touchpoint. You need to clear those invisible stumbling blocks -- onboarding time, data migration, trust barriers -- before the first use can happen.

The spectrum of solutions is wide:

• Fix: Solving everyday problems with personal knowledge/know-how
• Improvement: Analyzing bottlenecks in existing systems and exploring alternatives
• Innovation: Fundamental enhancement of technology/systems
• Invention: Creating entirely new systems (combining internal and external knowledge)
• Discovery: Creative solutions that never existed before

It helps to reframe the question: "If they use this, what will the customer do less of, and by how much?" or "At what moment would they want to use this right now?"

3) Commercialization: A Structure That Sells Beats a Good Product#

If you only start thinking about sales after development is done, channels, revenue models, partners, and operational capabilities show up too late. Commercialization should be designed from the moment you understand the size and structure of the problem. Our solution is always "one of many alternatives." So from a business perspective, this alternative needs to be compelling enough, with a structure where revenue flows naturally.

• Idea Hypothesis: Whose problem are we solving, and with what? (observation-based)
• Solution Proposal: In what form does it get adopted? (reason for adoption)
• Commercialization Method: Concrete design of channels, pricing, partners, and operations (business model)

It's important to design the selling structure from the very beginning.
It needs to be discovered where customers are, paid for at a comfortable price and flow, and closed with an experience that brings them back.

4) Three Risk Axes: Desirability, Feasibility, Viability#

A product must manage three risks simultaneously:

• Desirability: Have you precisely identified the customer? Is the problem important and urgent? Is there motivation to switch from alternatives?
• Feasibility: Do you have the required technology/operational capabilities? Can you deliver the promised value reproducibly? Can you hit target cost, quality, and lead time?
• Viability: Is the market large enough and growing? Do the price point and unit economics line up? Can you see a balance of CAC, LTV, and payback period?

If one axis collapses, the product won't last even if the other two hold up.

5) Value Chain: The Reality of Entry and Delivery#

A value chain is the connection of activities, functions, and processes needed to deliver value to the customer. Some markets have great infrastructure and easy entry (e.g., app development, deployment, and payment ecosystems). Early on, aggressively leverage existing platforms and partners to cut costs and time, then later build your own value chain to improve delivery speed and quality.

• What are the partners, tools, and processes at each stage of production, distribution, sales, and support?
• What external infrastructure will you borrow to reduce initial costs and lead time?
• What's our unique connection to reach customers faster and easier?

6) Balancing Price, Value, and Cost: The Conditions for Satisfaction#

Customer satisfaction can be explained with a simple inequality:

• Cost < Price < Value
• (Benefits - Price) < Value

Cost isn't just what shows up on the books. Development time, complexity, risk, onboarding and support -- these "recurring invisible costs" are what really determine true cost. On the flip side, customer value has four layers:

• Feature: Required technical characteristics
• Function: Capabilities/attributes provided
• Advantage: Real changes created by those capabilities
• Benefit: The emotional/experiential value that makes someone think "why I absolutely need to buy this"

This is why a product brochure should be a narrative of benefits, not a list of features.

7) Value Proposition: What's Different, and Why Should I Buy Now?#

Core value (differentiation) emerges in contrast with the competition. But customers don't feel differences abstractly. At the first touchpoint, they feel physical value (visible features, immediate satisfaction), and as usage accumulates, they build emotional value (reasons for repurchase and recommendation).

• Core value: Fundamental difference and reason for choosing over competitors
• Physical value: Characteristics and immediate satisfaction revealed at first impression
• Emotional value: The reason you want to use it again and recommend it

A good value proposition works even "in a single sentence": "For people who [do X], it finishes [Y task] [Z times] faster in [situation A]."

8) Business Hypothesis Foundation: Looking at Emotional, Functional, and Social Dimensions#

Even the same feature can have different emotional, functional, and social meanings. So try reinterpreting features/characteristics/benefits across all three dimensions:

• Emotional: How does solving the problem change the customer's mood and anxiety?
• Functional: What differentiating feature will they find most useful?
• Social: What satisfaction does it provide in terms of reputation, relationships, and belonging?

The principle is simple: define the benefits first, then design the features and functions that make those benefits possible.

9) PMF Definition and Structure: The Moment Everything Clicks#

PMF is "the state where enough customers buy, use, and recommend the product, sustaining growth and profitability."
Structurally, on one side there's the Product (Value Proposition -> Feature Set -> UX), and on the other side there's the Market (Underserved Needs -> Target Customer). The moment these two mesh together is PMF. Ultimately, it's about positioning "a good product in a good market that satisfies that market."

10) PMF Validation Hypothesis: Running on Four Tracks#

1. Product Value Proposition

   • What are the customer's pains and the gains they'll receive?
   • Who is the target segment/persona? As narrow as possible.

2. Top Features (Priority)

   • First, strip out the features that "don't need to be in V1."
   • Pick the 5 "must-use" features, and write out the adoption reason and scenario for each.

3. Acquisition (Channels)

   • Where do customers discover us? (Search, community, app store, referrals)
   • How does the team sell? (Self-serve, inside sales, partners, bundles)

4. Revenue Model

   • How will we make money?
   • Pricing can be flexible, but validate the willingness-to-pay (WTP) range early.

Market responses vary. Some products get quick reactions through immediate utility, while some services grow in value as networks, content, and data accumulate. Other models jump once they hit certain milestones (securing supply, entering an ecosystem). What matters is being aware of which trajectory your model is on, and designing metrics and experiments that match that trajectory.

Minimum validation criteria:

• Does the core feature excellently solve one important problem?
• Does it distinctively solve a long-standing problem customers couldn't solve on their own?
• MVP validates core value; MSP validates "willingness to pay"

11) Field Research: Value Proposition Card Testing#

A single deck of cards can tell you more than you'd expect. Create feature/characteristic/benefit cards in playing-card size with emojis and short phrases. About 9 cards is ideal -- ask the customer to "pick the cards they'd choose first" and listen to their reasons. What you gain here isn't feature feedback -- it's language and priorities.

Tips for running it:

• Recall recent experiences: "When was the most recent time you were in this situation?"
• Journey mapping: Awareness -> Exploration -> First Use -> Repeat -> Recommendation
• Record barriers: Trust, onboarding time, data migration, price sensitivity

Through the process of shuffling cards, your product's messaging gets refined.
You'll figure out what needs to be on the front and what should stay as the back-side explanation.

12) Practical Checklist: Items You Can Use Right Away#

Problem:

• Can you pin down the specific segment, context, frequency, and loss with numbers?
• Are the bottlenecks and dissatisfaction with existing alternatives confirmed through interviews/logs?

Solution:

• Are your "3 reasons for adoption" clear in a single sentence?
• Do you have an MVP scenario that validates only 1-2 core values?

Go-To-Market:

• Have you defined the channel and message for meeting your first customer?
• Are your pricing hypothesis, payment flow, and support process ready?

Metrics:

• Initial hypothesis values for Retention/Activation/Conversion/CAC/LTV
• Minimum measurable event definition (e.g., Time-To-First core action)

Learning Loop:

• Weekly hypothesis-experiment-learning-decision cycle
• Interview/experiment record template and sharing rhythm

Wrap-up: The entire process is a loop, not a straight line!
Problem clarity -> Adopted solution -> Selling structure -> PMF validation

This isn't a course you pass through once -- it's a learning loop you keep running. What matters is making one more lap each week, and making "what's different, and why should I buy now?" a little clearer with each lap. You can start light. A few value proposition cards are enough. But that one promise from the card you picked -- see it through to the end with genuine commitment. That promise becomes the backbone of your product.

Always bear in mind that your own resolution to succeed is more important than any one thing.

-- Abraham Lincoln