PadhaikoAll subjects

Problem Identification and Opportunity Discovery

IT-Based Innovation and Entrepreneurship (ENCT 436)

Open in the Padhaiko app

2.1 Problem identification as the foundation of innovation

Every sustainable technology venture begins not with a piece of software, but with a real, consequential problem. Innovation fails most often not because engineers cannot build the product, but because they build something nobody urgently needs.

Definition

Problem Identification

Problem identification is the structured process of discovering, framing, and verifying an authentic friction, inefficiency, unmet desire, or failure experienced by a specific group of people or organizations, before committing resources to engineering a solution.

Why Problem Identification Precedes Solution Design

  1. Prevents Premature Engineering ("Solution in Search of a Problem"): Anchors software features to measurable user pain rather than founder assumptions.
  2. Clarifies Value Proposition: A sharply defined problem immediately defines what success looks like for the customer (time saved, error reduced, cost lowered, or revenue gained).
  3. Identifies Willingness to Pay: Urgent, frequent, and expensive problems ("painkillers") convert buyers far more reliably than mild conveniences ("vitamins").
  4. Guides Differentiation: Understanding why existing alternatives fail reveals where a new IT product can deliver a improvement.
AspectVitamin ProductPainkiller Product
Problem UrgencyLow; users tolerate the status quoHigh; problem causes immediate financial, operational, or emotional loss
Customer AwarenessNeeds heavy education and persuasionCustomers actively seek or build workarounds already
Adoption & ChurnSlow adoption; high churn when budgets tightenRapid adoption; sticky retention once integrated into workflow
IT ExampleGamified personal habit trackerAutomated VAT/tax reconciliation software for SMEs facing audit penalties

2.2 Problem identification techniques

Entrepreneurs use systematic analytical and field techniques to uncover root problems rather than relying on casual intuition.

Core Problem Identification Techniques
TechniqueMechanismBest Use Case in IT Ventures
5 Whys AnalysisAsk "Why?" iteratively (typically five times) to move past symptoms to the root causeDiagnosing why users abandon an onboarding flow or why SME billing takes hours
Fishbone (Ishikawa) DiagramCategorizes causes into People, Process, Technology, Policy, Environment, and DataMapping multi-factor bottlenecks in hospital queues or supply chains
Journey MappingTraces every step a user takes end-to-end, marking delays, handoffs, and emotional dropsPinpointing friction in online university admissions or e-commerce checkout
Jobs-to-be-Done (JTBD)Focuses on the functional, social, and emotional "job" a customer hires a product to doUnderstanding why SMEs still use spreadsheets/WhatsApp instead of legacy ERPs
Bug / Friction JournalingRecording daily annoyances, manual copy-pasting, and broken workflows over 1–2 weeksDiscovering B2B workflow automation SaaS opportunities
Secondary Data & Trend MiningAnalyzing industry reports, support forums, app-store 1-star reviews, and regulatory updatesSpotting recurring complaints against incumbent software

2.3 Customer needs and pain points

Definition

Customer Needs and Pain Points

Categories of Customer Pain Points

  1. Financial Pain Points: Current tools are overpriced, carry hidden fees, or cause revenue leakage.
  2. Productivity / Time Pain Points: Excessive manual data entry, slow approvals, or repetitive coordination.
  3. Process / Integration Pain Points: Disconnected systems (e.g., inventory in Excel, billing in desktop software, orders on social media) requiring manual syncing.
  4. Support / Trust Pain Points: Poor reliability, opaque pricing, lack of local language support, or security/compliance fears.

2.4 Identifying unmet and emerging customer needs

Customer needs are not static; they evolve as technology, demographics, and regulations shift.

Techniques to Spot Unmet and Emerging Needs

  1. Lead-User Analysis: Studying advanced users who already hack together scripts, macros, or spreadsheets to solve needs that mainstream users will face next year.
  2. Workaround Detection: Anywhere users export CSVs, copy-paste between apps, or maintain shadow WhatsApp groups indicates an unmet software integration need.
  3. Non-Consumption Analysis: Examining people who want an outcome (e.g., accounting, tutoring, credit) but are priced out or intimidated by complex incumbent software.

2.5 Problem validation and problem-solution fit

Having an idea about a problem is only a hypothesis. Problem validation proves with empirical evidence that target customers genuinely experience the problem, recognize it as urgent, and actively invest effort or money to solve it.

Definition

Problem-Solution Fit

Problem-Solution Fit is achieved when validated evidence confirms that:

  1. A clearly defined customer segment has a high-priority problem worth solving, and
  2. A proposed solution concept directly addresses the root cause of that problem in a way customers understand and are willing to adopt or pay for—even before the full product is built.

Signs of Validated vs. Unvalidated Problems

AspectUnvalidated AssumptionValidated Problem
Evidence SourceFounder opinion or polite friends saying "cool idea"Past behavior: users already spend time, staff, or money on workarounds
Interview FeedbackHypothetical agreement ("I would probably use that")Specific recent stories ("Last Tuesday we lost NPR 15,000 because...")
CommitmentZero commitment beyond verbal praisePre-orders, Letters of Intent (LOIs), pilot sign-ups, or paid deposits

2.6 Customer observation, interviews and surveys

Because customers often say one thing in abstract questionnaires and do another in daily life, founders combine qualitative (observation, interviews) and quantitative (surveys, landing-page tests) discovery methods.

Customer Discovery Methods Compared
MethodPurposeStrengthsPitfalls to Avoid
Customer Observation (Ethnography / Shadowing)Watch users perform the task in their real environmentReveals unstated needs, workarounds, and physical/digital frictionObserver effect (users acting artificially formal)
Problem Interviews1-on-1 semi-structured conversations focused on past behaviorDeep root-cause understanding; uncovers unexpected pain pointsPitching your solution too early or asking leading future-tense questions
Structured SurveysQuantify frequency, demographics, and priorities across a larger sampleFast quantitative validation once themes are knownPoorly worded questions, low response rate, or biased sample

2.7 Market gaps and technology-based opportunities

Definition

Market Gap and TAM / SAM / SOM

A market gap is an underserved customer segment, price tier, geographic region, or workflow capability where existing competitors leave significant value unrealized. Opportunity size is quantified at three nested levels:

Bottom-Up vs. Top-Down Market Sizing

Bottom-up sizing is preferred by investors and examiners because every assumption can be audited.


2.8 AI for Entrepreneurship

Modern startups leverage Artificial Intelligence (AI) both as a force multiplier for the founder (accelerating discovery and execution) and as a core product capability.

How AI Accelerates Opportunity Discovery and Venture Building
Entrepreneurial StageAI ApplicationCaution / Human Oversight Needed
Market & Competitor ResearchSummarizing industry trends, clustering app-store reviews, scanning patent/competitor landscapesVerify citations and numbers; AI can hallucinate market statistics
Customer Discovery SynthesisTranscribing interviews, tagging recurring pain points, extracting sentiment and JTBD themesDo not replace real human interviews with synthetic AI personas
Rapid Prototyping & MVPGenerating UI mockups, boilerplate APIs, landing pages, and automated test suitesReview security, edge cases, and architecture scalability
Workflow Automation & OperationsCustomer support triage, personalized onboarding emails, localized content translationMonitor quality, data privacy, and bias
AI-Native Product FeaturesDocument OCR, predictive demand forecasting, smart recommendations, voice/NLP assistantsEnsure reliable accuracy, latency, and unit-economics (API token cost vs. price)

2.9 Technology-based entrepreneurial opportunities

Technology shifts continually open new entrepreneurial windows across software and cyber-physical domains:

  1. Vertical SaaS for Undigitized Industries: Tailored cloud workflows (clinics, schools, logistics, agri-cooperatives, hospitality) replacing paper ledgers and fragmented spreadsheets.
  2. Digital Marketplaces and Platforms: Two-sided networks matching supply and demand with trust, escrow, and routing (e.g., freelancers, local artisans, freight).
  3. API-First Infrastructure & Fintech: Payment orchestration, KYC verification, e-invoicing, and developer tooling built on open banking and national digital IDs.
  4. Data Analytics & Applied AI: Turning messy operational logs, satellite imagery, or local-language text/speech into actionable predictions.
  5. IoT, Edge & Cloud-Connected Hardware: Smart energy metering, cold-chain monitoring, precision agriculture sensors paired with subscription analytics.

2.10 Case studies of technology-driven startups

Analyzing real technology startups illustrates how problem identification, validation, and technology timing converge.

Illustrative Technology-Driven Startup Case Studies
Startup / CaseInitial Problem IdentifiedTechnological Opportunity LeveragedCore Lesson for Entrepreneurs
Stripe (Global Fintech)Integrating online credit card payments took developers weeks of bank paperwork and fragile scriptsDeveloper-first REST APIs ("7 lines of code") abstracting legacy banking railsSolve an acute developer/operational pain point with radical simplicity
Airbnb (Global Platform)Travelers faced sold-out/expensive hotels during conferences while locals had spare roomsPeer-to-peer web marketplace + trust reviews + online paymentsObservation of real local scarcity + concierge MVP validation before scaling
eSewa / Fonepay (Nepal Fintech)Paying utility bills and transferring small amounts required long physical queues and cash handlingRising mobile penetration + banking interoperability + QR standardsAdapting proven digital infrastructure to local trust and regulatory realities
Pathao / InDrive (Regional Mobility)Urban traffic congestion and opaque, unstandardized taxi/bike bargainingSmartphone GPS, real-time matching algorithms, and mobile walletsCapturing high-frequency daily pain points builds rapid network density

Worked Examples

Example 1

1 (8 marks)

An IT startup plans a cloud-based inventory and VAT-billing SaaS for retail pharmacies. Research shows there are registered pharmacies nationwide, of which operate in urban/semi-urban zones with reliable broadband and smartphones. The startup plans to charge an annual subscription of per pharmacy and realistically targets capturing of the reachable urban/semi-urban segment within two years. Calculate TAM, SAM, and SOM using the bottom-up method, and verify .

Computing Total Addressable Market (TAM): All registered pharmacies nationwide at :

Computing Serviceable Available Market (SAM):

Computing Serviceable Obtainable Market (SOM): Capturing of SAM ( paying pharmacies) within two years:

Clearly , confirming .

Answer:
  • TAM:
  • SAM:
  • SOM: ( pharmacies)
Example 2

2 (6 marks)

During problem validation for a clinic appointment platform, a founding team interviewed clinic managers. Of those, reported losing significant patient bookings due to missed phone calls, and of those signed a paid pilot deposit of . Meanwhile, two candidate problems are scored on a scale for Frequency (, weight ) and Severity (, weight ):

Compute the interview validation rate, pilot conversion rate among affected clinics, and weighted pain score gap between Problem A and Problem B.

Problem Validation and Pilot Conversion Rates:

  • Problem Prevalence in Interviews: confirm the pain point.
  • Pilot Commitment Rate (among affected clinics): paid an upfront deposit, demonstrating strong problem-solution fit.

Weighted Pain Scores:

Answer:

of interviewed clinics confirmed the problem and of affected clinics paid a pilot deposit. Problem A scores vs. Problem B's (a gap of points), confirming Problem A as a high-urgency "painkiller" opportunity.

Example 3

3 (6 marks)

Explain how to design a customer discovery plan (combining observation, Mom-Test interviews, and a follow-up survey) for a student team exploring an AI-powered exam-grading assistant for engineering colleges.

Customer Observation (Shadowing): Sit beside 3–5 faculty members while they actually grade mid-term answer scripts and enter marks into spreadsheets. Record where time is lost (deciphering handwriting, tallying sub-parts, uploading CSVs to the college portal) without offering suggestions.

Mom-Test Problem Interviews: Conduct 15–20 one-on-one interviews asking strictly about past behavior: "Walk me through the last exam you graded—which step took the longest?" and "What tools or teaching assistants do you currently use?" Avoid pitching the AI tool until the end, and seek concrete commitments (such as sample anonymized scripts for a trial).

Quantitative Survey & Synthesis: Once recurring themes emerge, send a short 5-minute survey to 100+ instructors across departments to measure grading volume, error frequency, and institutional budget rules. Use AI tools only to transcribe and cluster interview notes—never to fabricate user responses.

Answer:

A sound discovery plan starts with silent observation of real grading workflows, followed by Mom-Test interviews anchored in past behavior and current workarounds, and concludes with a targeted survey to quantify segment size and urgency before writing production AI code.


Exercises

Practice Exercises — Problem Identification and Opportunity Discovery

Question 1

Why is problem identification considered the foundation of technological innovation? Differentiate between a vitamin and a painkiller product with one IT example each, and describe how the 5 Whys and Jobs-to-be-Done (JTBD) techniques uncover root problems.

Problem Identification as Foundation: Without an authentic, urgent problem, engineering effort produces features customers ignore. Identifying the root problem clarifies the value proposition, reveals willingness to pay, and prevents premature scaling.

Vitamin vs. Painkiller: A vitamin offers a mild convenience (e.g., an aesthetic desktop weather widget), whereas a painkiller removes an acute operational or financial loss (e.g., automated cloud backup and ransomware recovery for clinics).

5 Whys and JTBD:

  • 5 Whys peels back surface symptoms by asking "Why?" repeatedly until reaching the controllable system cause.
  • JTBD analyzes the functional, social, and emotional progress a user seeks in a specific context rather than focusing on product demographics.
Answer:

Problem identification anchors engineering to real customer value and willingness to pay. Painkillers solve urgent, costly problems with high retention, whereas vitamins address mild wants. 5 Whys drills down to root causes, while JTBD reveals the underlying progress customers hire a solution to achieve.

Question 2

A Nepalese agritech startup builds an IoT + AI cold-storage monitoring SaaS priced at per facility per year. There are agricultural storage and dairy-chilling centers nationwide, of which have grid/solar power and cellular connectivity needed for telemetry. The startup projects capturing of the reachable market in three years. Calculate TAM, SAM, and SOM.

TAM (Total Addressable Market):

SAM (Serviceable Available Market): Restricted to the facilities with power and cellular coverage:

SOM (Serviceable Obtainable Market): Targeting of SAM ( facilities):

Answer:
  • TAM:
  • SAM:
  • SOM: ( facilities)
Question 3

Compare customer observation, problem interviews, and surveys in validating problem-solution fit. List three common mistakes engineers make during customer interviews and how to avoid them.

Comparing Discovery Methods:

  • Observation captures unspoken behaviors and workarounds in natural settings.
  • Problem Interviews probe root causes, frequencies, and past expenditures in depth.
  • Surveys quantify how widespread those findings are across a large sample.

Three Interview Mistakes and Fixes:

  1. Pitching the product early keep interviews focused on the customer's workflow and frustrations.
  2. Asking future hypotheticals ("Would you pay for...?") ask about past actions ("How much did you spend solving this last quarter?").
  3. Accepting polite compliments test commitment with deposits, LOIs, or follow-up introductions.
Answer:

Observation uncovers latent workarounds, interviews uncover root causes, and surveys quantify prevalence. Avoid pitching too early, asking hypothetical questions, or mistaking compliments for validation; instead ask about past behavior and seek concrete commitments.

Question 4

An accounting firm employs staff at to manually enter paper invoices per month, taking per invoice. An AI-OCR startup offers an automated invoice extraction SaaS for that cuts manual review time by . Calculate: (a) current monthly labor hours, (b) hours saved per month by the AI tool, and (c) net monthly financial savings for the accounting firm.

Current Monthly Labor Hours:

Hours Saved with AI-OCR ( reduction):

Net Monthly Financial Savings: Gross labor cost saved . Subtracting the SaaS fee:

Answer:

(a) , (b) , and (c) .

Question 5

Explain how AI can be used responsibly during entrepreneurial opportunity discovery, and summarize key lessons from case studies of technology-driven startups regarding timing, market gaps, and validation.

AI in Opportunity Discovery: AI accelerates competitor scanning, transcribes and clusters customer interviews, summarizes app-store complaints to reveal market gaps, and speeds up clickable/code prototyping. Founders must still verify facts manually and never substitute real customer conversations with synthetic AI responses.

Lessons from Tech Startup Case Studies: Successful ventures (such as Stripe, Airbnb, or eSewa/Pathao) pair an acute, high-frequency customer friction with an enabling technology shift (APIs, GPS smartphones, interoperable digital payments) and validate demand leanly before scaling.

Answer:

AI serves as a discovery and prototyping co-pilot—clustering feedback, scanning market gaps, and building rapid MVPs—while founders provide real-world validation and fact-checking. Startup case studies show that enduring ventures align real market gaps with timely enabling technologies and validate adoption early.

← Entrepreneurship and Entrepreneurial MindsetTechnological Innovation and Entrepreneurship →