Did you decide?
Or did you assume?
Most product failures are not execution failures. They are decision failures — made before a single rupee moved. LSAR is the system that fixes the decision before execution begins.
This is not theory.
This is a documented result.
Same factory. Same materials. Same water. One product decision — made before a single rupee moved into production — produced a 75% profit increase.
The iball case study is the most direct proof of what LSAR makes possible. Not a better product. A product that changes how people behave around it.
Read the full case study →75%
profit increase
iball · One product decision
The LSAR Framework
A 4-phase product decision system that replaces founder assumptions with behavioral evidence — before any build decision is made.
LSAR is not a design methodology. Not a consulting framework. Not a checklist. It is the structured process of replacing what you think is true with what is actually true — and converting that into one clear, executable product direction.
Most products fail not because of poor execution. They fail because the wrong decision was made before execution began. Good execution on a wrong decision still fails. Every time.
The decision comes first. Execution follows. Always.
The gap every other framework misses.
Four phases. One purpose.
Each phase has a specific job. Each phase produces specific outputs. Each phase is a prerequisite for the next.
Observe real users in real situations.
Not what they say. What they actually do.
Field research or desk research — no bias. Real behavior. Real context. Real frustrations. Zero predetermined conclusions. The researcher enters with zero assumptions and lets behavior speak.
- What they actually do, why they do it, what context surrounds the decision
- Opinion is not behavior. Stated preference is not demand.
- LSAR only works with real behavioral evidence
Outputs from Listen
- Real user profile — who they actually are
- Real problem — what actually frustrates them
- Real behavior — what they currently do
- Real context — when, where, and why
- Jobs to be done — what they are truly trying to achieve
Convert behavior into product direction.
The customer’s voice — not the founder’s vision.
Everything comes from behavioral evidence — not from what the founder originally wanted to build, not from competitors, not from internal team opinions.
- If this phase is wrong — everything downstream is wrong
- A weak foundation produces a product that solves the wrong problem
- For the wrong person. At the wrong price.
Outputs from Structure
- Validated problem statement — precise, evidenced
- Target audience — buyer and user identified
- Pricing direction — from behavioral signals
- Feature priority map — ranked by evidence
- Market positioning — from observed gaps
- Structured product brief
Test every direction against evidence.
One survives. The rest are eliminated.
3–5 product directions generated. Each evaluated against behavioral evidence criteria — not team preference, not founder instinct. Weak directions eliminated with documented reasons.
- No voting by preference. No “this one feels better.”
- No consensus without evidence
- The strongest behavioral evidence wins
Outputs from Analyse
- 3–5 validated directions with evidence scores
- Eliminated directions with documented reasons
- Demand validation — real willingness, not stated interest
- One recommended direction
- Risk assessment
One verdict: Build, Refine, or Stop.
When Build — execution begins in whatever form the product requires. Every step stays aligned with Listen, Structure, and Analyse. The decision comes first. Execution follows. Always.
- The moment execution drifts from evidence — the wrong product gets built
- Good execution on a wrong decision still fails. Every time.
- LSAR ensures the decision and execution stay aligned
Outputs from Resolve
- Final product direction — one, clear, evidenced
- Build / Refine / Stop verdict
- Decision rationale document
- Execution plan aligned with evidence
- Launch readiness in whatever form required
- Build guidance — where to deploy first and why
Every engagement ends with one of three decisions.
No ambiguity. No “it depends.” One clear verdict — backed by behavioral evidence.
LSAR is not industry-specific.
Any business making a product decision can apply the framework. The behavioral evidence principles work across all industries and product types.
L Saravanan — Product Decision Strategist
He started as a product designer. CIPET. MSc in Engineering — Product Design, Coventry University. Then ran a PET bottle manufacturing business with his own money — 50+ customers, real decisions, real consequences.
After 2022 he observed 40+ founders across 45+ products in 7 industries make the same mistake. Not a similar mistake. The exact same one. The decision to build was made before the evidence existed.
He built LSAR to close that gap. Not from theory. From decisions that had a rupee value and a deadline.
Full story →Questions About the Framework
What is the LSAR Framework?
The LSAR Framework is a 4-phase product decision system — Listen, Structure, Analyse, Resolve. It replaces founder assumptions with behavioral evidence before any build decision is made. It is not a design methodology, a consulting framework, or a checklist. It is the structured process of making the right product decision before building begins.
What does LSAR stand for?
LSAR stands for Listen, Structure, Analyse, Resolve — the four phases of the product decision system developed by L Saravanan, India’s Product Decision Strategist. Each letter represents one phase with a specific job, specific outputs, and a specific prerequisite role in the sequence.
How is LSAR different from Design Thinking?
Design Thinking, popularised by Stanford’s d.school, asks: how do you build something people want? LSAR asks: should you build it at all? Design Thinking begins after the decision to build has already been made. LSAR makes the decision first — before a single rupee moves. Both have value, but LSAR operates before Design Thinking begins.
How is LSAR different from Lean Startup?
Lean Startup is a post-build feedback system — build, measure, learn. It requires you to build something first before learning whether it is right. LSAR is a pre-build decision system — it determines what to build, and whether to build it, before any build commitment is made. For physical products where pivoting means scrapping a mould, Lean Startup is too expensive to apply. LSAR works before that cost is committed.
What is the Listen phase of LSAR?
The Listen phase observes real users in real situations — not surveys, not focus groups. What do they actually do? Why do they do it? What context surrounds the decision? Research can be field-based (ethnographic observation) or desk-based depending on user accessibility. Both methods follow one rule: zero bias, zero predetermined conclusions. Opinion is not behavior. Stated preference is not demand.
What is the Resolve phase — Build, Refine, or Stop?
Resolve delivers one of three verdicts. Build — behavioral evidence is strong, the product direction is clear, proceed with documented confidence. Refine — direction needs adjustment before committing; do not build what you have, build what the evidence points to. Stop — evidence does not support proceeding; what has not yet been spent is protected. A Stop verdict is not failure. It is the system working correctly.
Can LSAR be applied to digital products and SaaS?
Yes. The LSAR Framework applies to any product decision — SaaS features, D2C launches, physical products, FMCG, food, agricultural equipment, service design, or e-commerce. The behavioral evidence principles work identically across all industries and product types. The question is always the same: who is the real buyer, what is their real goal, and does the product decision reflect that?
Who developed the LSAR Framework?
L Saravanan, India’s Product Decision Strategist. He developed LSAR from 18+ years of operating experience — CIPET manufacturing training, MSc in Product Design from Coventry University, a PET bottle manufacturing business with 50+ customers, and post-2022 observation of 40+ founders across 45+ products in 7 industries. The framework emerged from one repeated observation: the decision to build was made before the evidence existed.
15 minutes. No commitment. The right next step becomes clear from there.