05. Problem Definition

Chapter 5 of 24 · 15 min

KEY INSIGHT

A well-defined problem has three components: a specific user, a specific struggle, and a measurable better outcome. Vague problems create vague products. The problem statement template that works: "_[User type]_ struggles with _[specific struggle]_ because _[root cause]_. Currently they _[workaround or status quo]_ which results in _[negative consequence]_." This structure forces specificity. "Nigerian businesses need AI" is not a problem statement. "Lagos salon owners lose customers because they can't respond to WhatsApp booking inquiries within 5 minutes, currently they ignore messages until evening which costs an estimated 30% of potential bookings" is a problem statement. Validate your problem by asking whether people would pay to solve it today. Not "would you use this?" but "would you pay ₦5,000 right now if I solved this for you?" Refusal to pay doesn't always mean the problem isn't real—it might mean you haven't found the right monetization model—but refusal to even consider payment usually means the problem isn't painful enough. ```python def problem_statement_score(problem_elements): """ Score problem definition clarity and viability. Returns numeric score and improvement areas. """ score = 0 feedback = [] # Check specificity of user if problem_elements.get('user_specificity') == 'high': score += 25 elif problem_elements.get('user_specificity') == 'medium': score += 15 feedback.append("User type could be more specific") else: feedback.append("Define a specific user segment") # Check measurability of problem if problem_elements.get('problem_measurable'): score += 25 else: feedback.append("Define how you'd measure problem severity") # Check current workaround existence if problem_elements.get('has_workaround'): score += 25 else: feedback.append("Is there truly no current solution? Check problem validity") # Check willingness evidence if problem_elements.get('payment_evidence'): score += 25 else: feedback.append("Gather evidence of payment willingness") return { 'score': score, 'grade': 'Strong' if score > 75 else 'Needs Work' if score > 50 else 'Weak', 'feedback': feedback } # Example evaluation my_problem = { 'user_specificity': 'high', # "Lagos-based freelance designers" 'problem_measurable': True, # "Average 3 hours daily on client revisions" 'has_workaround': True, # "Manual revision communication via WhatsApp" 'payment_evidence': True # "Currently paying ₦20,000/month to virtual assistant" } print(f"Problem score: {problem_statement_score(my_problem)['score']}/100") ``` Real failure mode: Solving the problem nobody has. Confirmation bias makes operators see their solution everywhere. Return to user research continuously—problems evolve, solutions must evolve with them.

Problem definition separates products that people actually use from technically impressive artifacts nobody wants. The trap is defining problems in terms of technology ("users need an AI chatbot") rather than outcomes ("small business owners need to respond to customer inquiries faster").

EXERCISE

Write three versions of your problem statement using the template above. Get feedback from someone in your target user segment on which version resonates most.