Defining the Problem Before Solving It
When Aravind Eye Care looked at avoidable blindness in India, the obvious answer could have been “build more hospitals.” The sharper question was different: how do we make quality eye care accessible to people who may never reach a traditional hospital? That shift - from a vague solution to a precise problem - is where real problem-solving begins.
- Do not solve the first sentence you hear. It is often a symptom, not the problem.
- A strong problem statement names the gap, owner, scope, constraint, and success measure.
- The best structure is: clarify objective - diagnose symptoms - frame the gap - bound the scope - define success.
- Bad problem definition creates elegant analysis for the wrong question.
- Use “current state vs desired state” to convert noise into a solvable problem.
- Before building issue trees, lock the problem statement; otherwise every branch will be unstable.
Big Picture: A Problem Is a Gap, Not a Complaint
Defining the problem is the first move in structured problem-solving: you convert a messy business concern into a focused question that can be answered with analysis.
The danger is subtle: most business problems arrive disguised as opinions. “Our app is bad,” “pricing is wrong,” “customers are unhappy,” or “we need more salespeople” may all be true - but none is yet a problem statement. They are starting signals.
The Core Idea: Slow Down at the Start to Move Faster Later
A well-defined problem is like a sharp camera lens. The facts may be the same, but the frame decides what becomes visible.
Compare these two statements:
- Weak: “The company should improve customer retention.”
- Strong: “Repeat purchases among first-time app users are below target in metro markets, and we need to identify the main drivers within the onboarding, pricing, and post-purchase experience.”
The second version tells the team what to analyse and what not to analyse. That is the whole point.
The Five-Step Process to Define the Problem
Use this when a case, project brief, or business discussion begins with ambiguity.
Once this is clear, you can move to building mutually exclusive issue trees without mixing causes, symptoms, and solutions in the same branch.
The Problem Statement Formula
When under pressure, write the problem in this structure:
For [owner], [current state] is below/above [desired state] in [scope], because of unknown drivers, under [constraints], and success means [metric/outcome].
Example:
“For the food-delivery business, repeat orders from new users in Tier-1 cities are below the target in the first 30 days, and we need to identify whether acquisition quality, pricing, delivery experience, or assortment is the main driver, while keeping discounts within budget.”
This is not yet the solution. It is the launchpad for the solution.
Good vs Bad Problem Definitions
Use this table to upgrade a weak statement quickly.
Notice the discipline: a good problem definition does not pretend to know the cause too early. It names the suspected areas and keeps them testable.
Definitions You Should Be Able to Say in One Breath
- Problem: A meaningful gap between the current state and a desired state, under constraints that make action necessary.
- Problem statement: A concise definition of the gap, owner, scope, constraints, and success measure.
- Symptom: Visible evidence of pain; it is not automatically the cause.
- Root cause: The underlying condition that, if changed, prevents the problem from recurring.
- Hypothesis: A testable best-guess explanation or answer that guides analysis.
Aravind Eye Care: Defining the Problem Before Scaling the Solution
Aravind Eye Care shows how reframing the problem from “more hospitals” to “accessible, high-quality eye care at scale” can change the entire operating model.
Situation: In India, many people needing eye care face barriers of access, affordability, awareness, and travel. A narrow problem statement would have been: “We need more eye doctors” or “We need more hospital capacity.”
The move: Aravind Eye Care framed the challenge more sharply: how can quality eye care reach large underserved populations reliably and affordably? That problem definition pushed the organisation toward an operating model built around patient flow, process discipline, outreach, specialised roles, and cost control.
Why it worked: The primary driver was not one magic tactic. It was the problem frame itself - access at scale, not just hospital expansion. Supporting drivers included standardised clinical processes, high utilisation of specialist time, outreach that brought patients into the system, and a culture of disciplined execution.
Lesson: If Aravind had defined the problem only as a supply shortage, the solution would have centred on adding more doctors and buildings. By defining the problem as access to quality care at scale, the organisation designed a system, not just an expansion plan.
How AI Changes Defining the Problem Before Solving It
AI does not remove the need to define the problem. It makes weak problem definition more dangerous, because a tool can produce polished analysis for a badly framed question.
- AI can surface hidden problem frames. You can ask ChatGPT or Claude to generate multiple ways to frame the same business issue - customer problem, economics problem, process problem, risk problem, or organisation problem.
- AI can pressure-test scope. A model can list what is inside and outside a problem statement, helping you catch vague boundaries before analysis begins.
- AI can convert messy notes into candidate problem statements. This is useful after reading an annual report, customer reviews, or interview transcript - but you must choose the final frame yourself.
Load a company annual report, case prompt, or article into NotebookLM. Ask: “Generate three possible problem statements, each with objective, scope, constraints, and success measure. Then list what analysis each frame would require.” Use the output as a thinking partner, not as the final answer.
Interview Relevance
“Our client’s revenue has declined for two quarters. How would you approach the problem?”
A strong candidate does not immediately say “I will analyse price and volume.” First, define the problem.
Use the phrase: “Before I solve, I’d like to make sure I’m solving the right problem.” It signals maturity without sounding slow.
Common Mistake
Jumping from symptom to solution. Candidates hear “sales are down” and instantly recommend discounts, marketing, or sales training. It costs them because they look action-oriented but not structured. Fix: first convert the symptom into a gap with owner, scope, constraint, and success measure.