Term 6 · Module 1 of 8

Foundations of Software Product Management in Startup and SPM Framework

Software Product Management for Startups

Practise this module in Claude, ChatGPT or Gemini

Set it up free
Mind map

Product Definition and Software vs Physical Products

What is a product? (Business perspective)

Every product, whether a pen, a TV, or WhatsApp, shares four business elements:

  1. Parties – a supplier (person or legal entity) and a customer/consumer.
  2. Value – the offering is useful; that is, it provides some benefit (even if no money changes hands).
  3. Defined rights – what the customer may do with the product: own, use, rent, sell (physical product) vs. use under license (software, e.g., Microsoft Office). The transfer of rights is more fundamental than payment.
  4. Commercial interests – the supplier’s motivation (money, data, promotion, etc.).

Physical Products vs Software Products

Attribute Physical Product Software Product
Tangibility Tangible (you can touch it) Intangible (can't touch the software itself)
Marginal cost High – each unit requires raw material, manufacturing, labour, logistics Near zero – serving one more user costs almost nothing (just a download)
Iteration speed Slow – retooling the assembly line needed for any change Fast – upgrades can be shipped overnight
Distribution Requires warehouse, shipping, physical retail No logistics or shelf life – delivered via app stores or cloud
Feedback loop Slow – manufacturers rely on surveys, complaints, or warranty claims Near real-time (especially cloud) – usage data available instantly
Risk of irreversibility High – committed cost cannot be recovered easily Low – can fix, upgrade, or revise after release

Types of Software Products

Not every app is a “software product.” The defining criterion: primary value must come from the software itself.

  • Embedded softwaresoftware designed specifically to make a physical device work (e.g., iOS for Apple devices, firmware in a washing machine). It runs only under specific hardware conditions.
  • Software productthe software itself is the core value; you can use it independently (e.g., WhatsApp, Google Maps).
  • Software-intensive productsoftware is the primary driver, but not the only component of a larger system.
  • Non-software product delivered via softwaree.g., a banking app. Without a linked bank account, the app has no value. The primary value is the banking service, not the software. Such a product is not a software product in the strict sense.

Key takeaways

  • A product always involves parties, value, defined rights, and commercial interests.
  • Physical products: tangible, high marginal cost, slow iteration, physical distribution, delayed feedback.
  • Software products: intangible, near-zero marginal cost, fast iteration, digital distribution, real-time feedback.
  • Software products are defined by software being the primary value; embedded software, software-intensive products, and apps with non-software primary value are related but distinct categories.

Product Family, Platform, and Product Line

Product Family

A product family is a set of diverse but connected products united under a single strong brand to enable cross-selling and build trust. The products are held together for marketing reasons – they may share no common technology.

Example Products in the family
Google Search, Maps, Photos, Cloud, Meet, Drive
Microsoft Office 365 Word, Excel, PowerPoint, Outlook
  • Each product in the family has distinct functionality.
  • They are often shipped together as a suite.
  • Brand power drives adoption of the entire family.

Product Platform

A product platform is a foundational set of shared technologies, components, and services that enable the development of multiple related products (or applications) – not a single product.

Two main types (illustrated by Amazon):

  1. Innovation platform – a technological foundation that developers use to build their own products. Example: Amazon Web Services (AWS) – startups build applications on AWS infrastructure.
  2. Transaction platform – an intermediary or online marketplace that enables buying, selling, or sharing of goods/services. Example: Amazon marketplace – buyers and sellers transact.
  • A platform is not a pointed solution; it is a foundation for many solutions.
  • Distinguishing feature: the platform enables others to create value.

Product Line

A product line is a set of product variants that all share a common product platform (architecture, code base, or infrastructure) but are adapted for different markets, geographies, or use cases.

Example Platform Product Lines
Amazon Single code base (underlying platform) amazon.in, amazon.de, amazon.fr – same look and feel but different features per country
Android Open-source Android OS Variants by different phone brands (Samsung One UI, Xiaomi MIUI)
Automobiles Same engine, braking, chassis Sedan, hatchback, estate
  • The product line is a manifestation of the platform.
  • Relationship: Product platform → (multiple) product lines.

How the three relate:

Key takeaways

  • Product family: different products, same brand (marketing-driven).
  • Product platform: shared foundational technology/services that enable other products (e.g., AWS, Android).
  • Product line: variants of a product built on a common platform (e.g., country-specific Amazon sites).
  • These are distinct: a family can exist without a platform; a platform can have multiple lines; a line always depends on a platform.

Software Product Management Definition and Evolution

Software product management (SPM) is the discipline governing a software product — including embedded software, software-intensive products, and associated services — over its entire life cycle. That means managing every phase from concept (understanding customer needs) through design, development, growth, maturity, and eventual retirement. The goal is not just to produce software but to deliver customer value and business value that makes the product viable.

Definition and Scope

  • SPM covers the full gamut of business around the product: strategy, pricing, positioning, development, marketing, and lifecycle decisions.
  • It applies to pure software products (e.g., WhatsApp), embedded software in physical goods, and software-intensive systems (e.g., a car’s infotainment system).
  • The core output is a product that balances customer satisfaction with sustainable profit.

Evolution of Product Management

The role and focus of product management have shifted dramatically over a century, moving from physical goods to intelligent systems.

Era Key Focus Representative Company Core Concepts
Product era (early 1900s) Manufacturing at scale, efficiency, standardization Ford (“any color as long as it’s black”) Production, engineering, quality
Marketing era (1930–31) Brand management, customer segmentation, positioning Procter & Gamble 4Ps (product, price, place, promotion); product manager as mini-CEO
Software era (late 1960s–1990s) Develop features, deliver user experience, iterate rapidly IBM, Microsoft (MS-DOS, Windows) SDLC, agile, lean startup; shrink-wrapped software
Platform era (2000s–2010s) Multi-sided ecosystems, network effects, scale Amazon, Uber Product–market fit, ecosystem partners, business value at scale
Intelligent era (present) AI, digital-physical integration, systems thinking Tesla, da Vinci 5 Phygital products, cyber-physical systems, autonomous decision-making

Key concept – Phygital and cyber-physical systems Phygital products are physical goods enhanced by software to remove friction (e.g., a smart air conditioner controlled via a phone app). Cyber-physical systems go further — software controls safety, regulation, and autonomous decisions (e.g., a self-driving car).

Key takeaways

  • SPM manages a product from concept to retirement, balancing customer and business value.
  • Product management originated in physical manufacturing (product era), then added marketing, then software, then platforms, and now intelligence.
  • Each new era added a new dimension: scale → branding → iterative UX → ecosystems → systems thinking.
  • Hardware and software are converging — modern product managers must handle phygital and cyber-physical products.

Desirability–Feasibility–Viability Framework

This framework (adapted from IDEO’s design thinking) identifies three essential pillars for any product’s success. A product that succeeds must sit at the intersection of all three.

Pillar Question Skill Required
Desirability Do customers actually need or want this product? Design / empathy
Feasibility Can we build it with current technology and capabilities? Engineering
Viability Can we make a profit — are the unit economics sustainable? Business

Intersections and failure modes

A product can fail if any one pillar is missing:

  • Desirability + Feasibility, no viability → Unsustainable. Customers want it and you can build it, but the economics don’t work (e.g., early Dunzo, Zepto had unit economics problems).
  • Desirability + Viability, no feasibility → Pipe dream. Demand and money exist, but technology isn’t ready (e.g., telemedicine in pre-COVID India where remote areas lacked data connectivity).
  • Feasibility + Viability, no desirability → Useless innovation. You can build it profitably, but nobody wants it. ~40% of startups fail here (per Crunchbase insights; e.g., early VR EdTech tools that customers didn’t adopt at the price point).

Success example: UPI and digital wallets

  • DesirabilityMassive demand for simple digital payments.
  • FeasibilityCore banking and financial backend technologies existed.
  • ViabilityBillions of transactions enabled the business to scale profitably.

Key takeaways

  • A product must be desirable, feasible, and viable simultaneously.
  • Missing any one dimension leads to a specific failure pattern: unsustainable, pipe dream, or useless innovation.
  • Validate desirability early — it is the most common missing pillar.
  • The framework is a practical lens for evaluating any new product idea (e.g., a hypothetical “smart hydration bottle”).

Startup Attributes and Types of Startups

A startup is not a small version of a mature company. Intuitively, think of a caterpillar and a butterfly — the caterpillar is not a “small butterfly”; it is a fundamentally different stage of life. Similarly, a startup operates under conditions that make it a distinct organizational form.

Defining a Startup: The Experiment Lens

Serial entrepreneur Steve Blank defined a startup as “an experiment in search of a business model.” A business model is a hypothesis about how the organization will create, deliver, and capture value. Until validated, the venture is temporary.

Key implications:

  • The product is not final — the team does not yet know who the real customers are, how they will use the product, or whether it will meet their needs.
  • The approach is iterative experimentation: build, measure, learn, pivot or persevere.
  • A startup is a temporary organization designed to discover a repeatable, scalable business model.

Core Attributes of a Startup

Attribute Description
Extreme uncertainty Unclear markets, customers, funding, team availability, and technology viability
Temporary structure Not meant to last as-is; success leads to transformation into a mature company
Experimentation Decisions are hypotheses to be tested; failure is data, not final
Resource constraints Limited money, people, and time (especially in bootstrapped phases)
High dependency on ecosystem Must rely on partners for storage, compute, market access, etc.

Types of Startups (in Product Management Context)

Three major types exist, each with distinct trade-offs for product managers.

1. Bootstrapped Startup

  • FundingFounders self-fund; no external investment.
  • FocusFrugal innovation — lean, low-cost, iterative development.
  • AdvantagesFull flexibility — choose markets, technology, and release timings independently.
  • DisadvantagesSevere resource constraints; heavy reliance on ecosystem partners (e.g., cloud storage, compute vendors); dependency can delay or derail.
  • ExampleZoho — famously refused funding to retain control.

2. Funded Startup

  • FundingExternal investors (angel, VC) provide capital in exchange for equity.
  • FocusRapid scale and monetization — investors expect high returns within 3–7 years.
  • AdvantagesAmple resources; ability to hire aggressively, spend on marketing, and develop faster.
  • DisadvantagesTime constraint is the sword — not patient capital; pressure to ship and monetize quickly; limited freedom to pivot because investors control strategic direction.
  • ExamplesFlipkart, Paytm — began small, received funding, grew into platforms.

3. Corporate Venture

  • FundingA single corporate parent provides capital.
  • FocusStrategic alignment — the venture operates within (or adjacent to) the parent’s business.
  • AdvantagesAccess to both capital and the parent’s market, distribution, and expertise (“riding on giant shoulders”).
  • DisadvantagesConstraints of alignment — priorities and timelines are dictated by the parent; the venture cannot explore “white spaces” that conflict with the parent’s roadmap.
  • ExampleJio (Reliance) — massive initial investment in infrastructure and distribution, made possible by the parent corporation.

Comparison Table

Dimension Bootstrapped Funded Corporate Venture
Source of funds Founders External investors Parent corporation
Resource availability Low High High
Time pressure Low (self-paced) High (investor exit timeline) Moderate (parent’s strategic cycle)
Flexibility Maximum Limited (investor control) Limited (parent alignment)
Example Zoho Flipkart, Paytm Jio

Experimentation in Action: Instagram’s Pivot

Instagram is used as a case study:

  • Original idea: a location‑sharing app that let users share photos from places (restaurants, parks) and monetize via sponsors.
  • After launch, only the photo‑sharing feature gained traction.
  • The team removed all other features — streamlined the app — and relaunched as a pure photo‑sharing platform.
  • Business model shifted from location sponsors to the creator economy (ads, influencer marketing).

How Ideas Connect

Key Takeaways

  • A startup is not a small version of a mature business; it is a temporary, experimentation‑driven organization searching for a repeatable business model.
  • Core attributes: extreme uncertainty, experimentation, temporary structure, resource constraints, and ecosystem dependency.
  • Three types: bootstrapped (frugal, flexible), funded (resource‑rich but time‑pressed, investor‑controlled), and corporate venture (strategic alignment, parent‑dependent).
  • Product managers must adapt their approach based on the type: e.g., pivot cautiously in funded startups, embrace partnership dependency in bootstrapped ventures.
  • Real‑world pivots (e.g., Instagram) show that experimentation often means removing features, not just adding them.

Discovery Phase

The Discovery Phase is the first stage of a startup’s product evolution. Its purpose is to answer a single high-stakes question: Does this product need to exist? Founders who skip this phase risk building something nobody wants — ~40% of startup products are never needed (Crunchbase Insights). The phase systematically uncovers a real customer problem, validates that enough people face it, and checks whether existing solutions are inadequate.

Step 1: Spot the Customer Problem

A customer problem is not a business problem; it is a difficulty or inefficiency a person experiences when completing a task. It is uncovered by keen observation of current practices — analysing the time, effort, cost, and risk involved in the way people do things now.

Airbnb example: The founders couldn’t pay rent and rented out air mattresses to conference attendees. They observed that short-term travellers struggled to find affordable, convenient accommodation — a problem of temporary demand-supply mismatch.

Step 2: Observe / Survey a Large Sample

Once a potential problem is spotted, the startup must gather customer insights from a large sample (not just the first few users). The goal is to identify a pattern: does the problem repeat across a significant population? Who faces it? Under what conditions?

Airbnb example: They talked to hundreds of travellers attending conferences and events in San Francisco. The pattern emerged: during conferences, peak vacation times, and events, there was a consistent lack of affordable, nearby accommodation.

Step 3: Study the Alternatives

Before building a solution, the startup must understand what customers currently do to cope with the problem. This step determines whether the problem truly needs a new solution or could be solved with a simple tweak (e.g., better information). The analysis should examine cost, convenience, risk, time, and effort of each existing alternative.

Airbnb example:

  • Hotels: expensive, often unavailable at short notice
  • Staying far away: inconvenient and unsafe
  • Friends/family: not everyone has them nearby

Conclusion: no scalable alternative existed; the problem was not about awareness but a genuine supply-demand mismatch.

  1. 1Spot the customer problem
  2. 2Observe / survey large sample
  3. 3Identify patterns
  4. 4Study the alternatives
  5. 5Conclude: Is the problem real & unsolved?

Why This Matters for Pricing

Studying alternatives directly informs pricing. The value of the solution is bounded by what customers currently pay in time, money, and hassle. Airbnb’s $80 per night price was not arbitrary — it reflected the cost and inconvenience of hotel rooms and distant rentals.

Practical Application

Apply the same three questions to any startup (e.g., Niramai, Zoho, or your own idea):

  1. What is the pressing unmet need?
  2. Who has this problem, and how does it manifest across segments?
  3. What current alternatives exist, and at what cost, convenience, risk, time, and effort?

Key takeaways

  • The Discovery Phase confirms that a real customer problem exists before any solution is built.
  • Step 1: Spot the problem via observation of time, effort, cost, and risk.
  • Step 2: Validate the pattern by surveying a large sample (100s–1,000+).
  • Step 3: Study alternatives to see if the problem is truly unsolved or just poorly matched.
  • Alternative analysis directly feeds into pricing strategy.
  • Skipping discovery leads to a ~40% chance of building something no one needs.

Product Evolution (Validation Phase)

From Discovery to Validation: Shifting Focus

The discovery phase (Steps 1–3) established whether a real customer problem exists — it emphasised desirability (“do they need it?”). The validation phase (Steps 4–6) checks whether your solution actually works for real users. Now feasibility (“can we build it?”) becomes equally important.

The DFV framework (desirability, feasibility, viability) visualises this shift:

  • Discovery: desirability circle is largest — the focus is on understanding the problem, customer segments, and alternatives.
  • Validation: both desirability and feasibility circles are large — the solution must continue addressing a real problem and be buildable within constraints.

The goal of validation: build something that some people actually use and find valuable — not just express approval.


Step 4: Build the Core Product

What to build and what not to build is critical. Create a minimum version of the product that addresses the needs of a carefully selected set of early adopters — not all potential customers.

Key principle Why it matters
Minimise time, cost, effort Speed and learning, not perfection
Choose pilot customers who really need the product Friends/family may say “yes” but never use it — pick those with a felt need
Build just enough to test A working experiment, not an automated, scalable system

Step 5: Validate the Core Product

The MVP is now tested with real users. Validation addresses desirability + feasibility and focuses on durability and repeatable use — not mass adoption.

  • Durability: Do users find the solution valuable enough to return?
  • Repeatability: Do they come back and use it again?
  • Comparison with alternatives: Can users compare the new offering with existing options and give meaningful feedback?

Airbnb validation:

  • Would strangers stay in someone else’s home? (Behavioural change for guests)
  • Would hosts list their spaces? (Behavioural change for hosts)
  • Real people booked, stayed, and paid. Hosts rented space. This proved the concept — not just verbal enthusiasm.
  • Validation insight: Usage and feedback are the proof-point, not just payment.

Step 6: Sharpen the Core Product (Validated Learning)

Validated learning is data-driven, not just qualitative. Use metrics to fine-tune the product within available means (time, cost, effort). Ask: what works? What doesn’t? Improve the former, remove the latter.

Airbnb sharpening:

  • Improved listing quality — added photos of interiors, utilities, features.
  • Collected reviews to build trust.
  • Made booking simpler.
  • Result: the core value proposition gets stronger for existing users (both hosts and guests), even if not yet ready for mass scale.

The output of these three steps is a problem-solution fit.


Problem-Solution Fit

Validation culminates in problem-solution fit — the point where you have:

  1. A clear, unambiguous target customer — you know their attributes, problem, patterns, and alternatives.
  2. Clarity of the problem — exactly what are you solving?
  3. An MVP that works for those customers.
  4. Users who find it valuable — demonstrated by usage, repeat behaviour, feedback, and (ideally) payment.

Key difference from product-market fit: Problem-solution fit is about validating the solution for a small set of early users; product-market fit (covered later) is about scaling to the mass market.


  1. 1DiscoveryDesirability focus
  2. 2Build Core ProductStep 4
  3. 3Validate Core ProductStep 5
  4. 4Sharpen Core ProductStep 6
  5. 5Problem-Solution Fit

Key takeaways

  • Validation shifts focus from desirability alone to desirability + feasibility.
  • Build a minimal product (MVP) for a carefully selected set of real users — aim for speed and learning.
  • True validation = behavioural change, repeat usage, and measurable feedback, not just praise.
  • Sharpening uses data-driven learning to improve what works and remove what doesn’t.
  • Validation ends with problem-solution fit: a clear target customer, a clear problem, a working MVP, and evidence of value.

Product Thinking

Product thinking is a customer-first, value-centric, continuous approach to building products that are scalable, sustainable, responsible, and profitable or impactful. It contrasts with project thinking, which is limited by budget, time, and defined goals. A product is a long-term, evolving solution that solves real-world problems for a population scale — not just a single transaction.

Product thinking = value + iteration + impact + profitability — all with a long-term lens.

The Five Dimensions of Product Thinking

Every global product must be evaluated along these five interrelated pillars:

Dimension Core Question What It Means Real-World Example
Value Does it solve a real problem in a simple, relatable way? Customer–centric: solves pain, drives adoption & retention. Benefit must be clear at first use. WhatsApp replaced complex sign‑ups (Skype) with a phone‑number‑only model, delivering instant value.
Scalability Can it serve millions/billions without breakdown? Robust architecture, performance, ecosystem integration. Growth of adoption without failure. UPI scaled from a few banks to handling billions of transactions/month across payment gateways, devices, and banking systems.
Sustainability Can it endure environmentally, socially, and economically? Environmental (e.g., energy use), social (across demographics), and economic (value for business and ecosystem partners). Microsoft Office sustains by improving user productivity, co‑existing across OS, and enabling collaboration (Teams) with reasonable energy consumption.
Responsibility Is it ethical, trustworthy, safe, and privacy‑respecting? No dark patterns, data privacy, transparency, non‑addictive design, informed defaults. Trust is a strategic asset. Aadhaar (India’s digital identity) is simple yet profoundly responsible — it has no dark patterns, is trustworthy, and protects privacy.
Profitability / Impact Can it generate revenue (commercial) or social value (societal platform)? Sustained value per user and collectively. Without profitability/impact, the product vanishes. WhatsApp is commercial; Aadhaar is a societal platform. Both must demonstrate sustained value to survive.

Value: The Core Driver

  • Solve a real problemidentify what customers currently use (alternatives), at what cost/convenience/risk.
  • Drive adoption & retentionthe first use must deliver benefit immediately. WhatsApp’s phone‑number‑only sign‑up made first‑use value instant, leading to high retention.

Scalability: Thinking Beyond the First User

  • Architecture must handle rapid growth without performance loss.
  • Ecosystem thinking — the product must interface seamlessly with other systems (payment gateways, banking, devices). UPI succeeded because NPCI built a simple, robust, interoperable system.

Sustainability: Three Layers

  1. Environmental — minimize negative impact (e.g., avoid fossil fuels).
  2. Social — work across demographics and sustain social cohesion.
  3. Economic — create value for both the business and its ecosystem partners (suppliers, developers, etc.).

Responsibility: The Modern Imperative

Modern digital products are deeply embedded in life; responsibility covers:

  • Ethical designno dark patterns (manipulative defaults, addictive loops).
  • Data privacy & trusttransparent processing, secure handling, informed consent.
  • Safetyprotect users and non‑users (e.g., content moderation).

Profitability / Impact: The Survival Condition

  • Commercial platforms must generate revenue (profits) to survive.
  • Societal platforms must deliver measurable social impact (e.g., Aadhaar’s inclusion).
  • Without either, the product will disappear (e.g., many short‑lived apps that were not profitable).

Trade-Offs and Interconnections

  1. 1Value
  2. 2Scalability
  3. 3Sustainability
  4. 4Responsibility
  5. 5Profitability / Impact
Then it starts again from step 1.
  • Trade-offs are inevitable — e.g., maximizing profit might tempt dark patterns, undermining responsibility.
  • Trust and sustainability make the product a long‑term strategic advantage; short‑term gains at their expense lead to eventual failure.

Key takeaways

  • Product thinking is multidimensional: value, scalability, sustainability, responsibility, profitability/impact.
  • Customer value drives adoption/retention; first‑use benefit is critical.
  • Scalability requires robust architecture and ecosystem integration.
  • Sustainability spans environmental, social, and economic dimensions.
  • Responsibility (ethics, privacy, trust) is a modern strategic necessity.
  • Profitability or societal impact is required for survival; all five dimensions must be balanced.

Job-To-Be-Done (JTBD) Framework

Jobs to Be Done (JTBD) is a framework for understanding why customers “hire” a product. The core insight: people do not simply buy products; they hire them to make progress in a specific context. The progress includes functional, emotional, and social dimensions — not just the stated need.

Need vs. Value

Customer need = a problem, pain, or job the user wants done. Value = the perceived benefit minus the total cost (money, time, effort, risk). A product may solve the need but still fail if it does not deliver enough relative value compared to alternatives.

Value=Benefits−Costs(where costs include money, time, effort, risk)\text{Value} = \text{Benefits} - \text{Costs} \quad (\text{where costs include money, time, effort, risk})

Many products fail not because they don't solve the need, but because they don't deliver enough value.

Example – Doctor’s Certificate A doctor wants to hang her MD certificate.

  • Functional needDisplay the certificate (regulatory / practical).
  • Emotional needPride, sense of achievement after a decade of study.
  • Social needBuild trust and confidence in new patients (social credibility).

A simple drilling machine solves the functional need (hang the photo). But a framing service or a digital display that enhances the emotional and social value would deliver more value.

Example – Uber vs. Traditional Taxi Both solve the need “get from A to B.” But Uber added:

  • Convenienceapp-based booking, tracking, expected arrival time.
  • Reliabilityreal-time data, driver rating before the ride.
  • Safetyperceived security through tracking.

Uber did not invent a new need; it delivered higher value by addressing emotional and social jobs (reliability, safety, convenience) on top of the functional job.

The JTBD Framework (Clayton Christensen)

When customers “hire” a product, they look for progress across three types of jobs:

Job Type Description Example (UPI payment)
Functional The practical task to be done Transfer ₹46 to an auto driver
Emotional How the user wants to feel Relieved, not anxious about non‑payment
Social How the user wants to be perceived Not embarrassed by inability to pay after dinner

The framework forces teams to look beyond the stated need and uncover the full set of jobs. This enables designing a value proposition that outperforms current alternatives.

Conducting JTBD Interviews – Process

A step-by-step interview approach uses a recent payment scenario (e.g., a small UPI-like payment). The logic flow is:

  1. 1Identify a recent, specific event
  2. 2Probe the trigger & context
  3. 3Alternatives considered & why chosen
  4. 4Frustrations & trade‑offs
  5. 5Satisfaction with outcome?
  6. 6Summarize the JTBD statement

Sample interview questions (from the UPI example):

  1. Trigger event: “Tell me about the last time you paid a small amount (₹46 for a rickshaw).”
  2. Context: “What caused that payment? Did the driver lack change?”
  3. Options considered: “Did you think of cash, card, cheque? Which ones and why?”
  4. Frustrations: “What frustrated you most about each option?”
    • Cash: needing exact change, not having small notes.
    • Card: remembering PIN, terminal not available, risk of sharing details.
  5. What nearly stopped you? “Did any of these issues almost make you avoid the transaction?”
  6. Trade‑offs made: “What did you sacrifice? (e.g., small change, privacy, time)”
  7. Satisfaction: “Were you relieved when the payment went through? How?”
  8. Importance: “How important is it to have a certain, easy payment method?”
  9. Perfect solution: “What would a perfect solution look like? (e.g., no details, no change, always works)”

After interviewing several people, look for patterns – common frustrations, recurring contexts, and unsatisfied emotional/social jobs.

Synthesised JTBD statement (payment example):

“When I need to pay, I want to pay simply and easily and in a certain way so I can feel relieved that I'm not at risk of non‑payment.” Functional job: pay without losing extra money / change. Emotional job: avoid anxiety about being unable to pay. Social job: avoid embarrassment.

Worked Example – UPI Payment Alternatives

Alternative Cost (time, effort, risk) Benefit Gap (unsatisfied job)
Cash Finding change; carrying exact amount Universal acceptance Effort of finding change; risk of not having enough
Card Remember PIN; swipe machine needed; data risk Secure for large amounts Not always accepted on street; anxiety about PIN failure
Cheque Slow; not accepted for small amounts Record‑keeping High effort; not used in daily small payments
UPI (ideal) Almost zero friction No change; no details shared; always works –

Key Takeaways

  • Need ≠ Value. Value = benefits – costs; a product can solve a need but still fail if it doesn't deliver enough value compared to alternatives.
  • Jobs to Be Done includes functional, emotional, and social dimensions. Always probe beyond the stated need.
  • Interview method: start with a recent, specific event; ask about triggers, alternatives, frustrations, trade-offs, and the perfect solution.
  • Pattern recognition across multiple interviews reveals the true JTBD statement.
  • Value proposition is built by making progress on jobs better than the alternatives in all three dimensions.
  • Practice on any product (WhatsApp, Instagram, Perplexity) by mapping the functional, emotional, and social jobs.
Revise before your examAll 8 exam tips from this module in one list
  1. The marginal cost difference is the most frequently tested distinction. Physical: high marginal cost → careful inventory management. Software: near-zero marginal cost → business models like freemium or volume scaling become viable.
  2. the biggest killer** The most common cause of startup failure (≈40%) is lack of desirability — building something feasible and viable that nobody actually needs. Always validate desirability first.
  3. The “caterpillar vs. butterfly” analogy is a classic exam question — remember that a startup is structurally different, not just smaller.
  4. The Instagram story illustrates that experimentation is not only about adding features; removing features and simplifying can be the winning move. It also shows how the business model itself can pivot.
  5. The 40% failure rate statistic (Crunchbase) is a high-yield reminder: the Discovery Phase is not optional. Questions often ask why startups fail — lack of problem validation is a top cause.
  6. Validation is not when users say “great idea”. Validation is when they change their behaviour because of your product.
  7. Trust and sustainability are strategic advantages — even if regulators don’t ban an irresponsible product, users will eventually abandon it.
  8. The JTBD interview process is a direct application of the customer discovery phase. The goal is to validate the importance of the job and identify where current alternatives fall short. This feeds the value proposition canvas (covered later).

Test yourself on this module

Questions from these notes, one at a time, with feedback. Your weak topics are saved.

Set it up free Takes about a minute. Free plans work.