The LSAR Framework
A 4-phase product decision system that replaces founder assumptions with behavioral evidence — before capital is committed to any product.
LSAR is not a design methodology.
It is not a consulting framework.
It is not a checklist.
It is the structured process of replacing founder assumptions with behavioral evidence — and converting that evidence into one clear, executable product direction.
Why LSAR exists
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. Without exception.
LSAR exists to ensure the decision made before execution is the right one — grounded in real behavior, not assumption, opinion, or gut feeling. The framework does not start with the product idea and work outward. It starts with real human behavior and works toward the product.
The decision comes first. Execution follows the decision. Always.
See LSAR applied to a real product decision — read the case study.
L — Listen
Listen is the research phase of LSAR. Its only job is to find real behavior — not what people say they will do, but what they actually do.
Research in the Listen phase can be field-based or desk-based depending on user accessibility. Field research means going to the real environment — observing users in the actual situations where the product will be used. Desk research means structured secondary research when direct observation is not possible.
Both methods follow one non-negotiable rule: no bias. No “I already know the answer” mode. No predetermined conclusions. The researcher enters the Listen phase with zero assumptions and lets behavior speak.
What does NOT qualify as listening
“My friends said they would use it.” “The market research report says demand exists.” “I’ve seen this succeed before.” These are not behavioral evidence. They are opinions, recollections, and stated preferences — none of which predict real purchase behavior.
Opinion is not behavior. Stated preference is not demand. LSAR only works with real behavioral evidence.
- Real user profile — who they actually are, not who the founder assumes
- Real problem — what actually frustrates them in real situations
- Real behavior — what they currently do and how they do it
- Real context — when, where, and why this happens
- Jobs to be done — what they are truly trying to achieve
S — Structure
Structure is where raw behavioral evidence from the Listen phase is converted into a clear product foundation. This is not the founder’s vision being refined. It is the customer’s voice and behavior being translated into structured product directions.
Everything that gets structured in this phase comes directly from behavioral evidence — not from what the founder originally wanted to build, not from what competitors are doing, and not from internal team opinions.
What gets structured
Problem statement — the real problem defined precisely from observed behavior. Not a broad category. One specific, evidenced problem that real people experience in real situations.
Target audience — who exactly the product is for, based on observed behavior. Who buys it. Who uses it. What their situation is. These are often different people with different goals.
Pricing direction — what the market will actually bear, based on behavioral signals — not guesswork or competitor benchmarking.
Feature priorities — what actually matters to the user, ranked by evidence — not by what the founder finds technically interesting.
Market positioning — where this product sits relative to what already exists, based on the gaps behavioral research revealed.
If this phase is wrong — everything downstream is wrong. The Structure phase is the foundation. A weak foundation produces a product that solves the wrong problem for the wrong person at the wrong price.
- Validated problem statement — precise, evidenced, real
- Target audience definition — buyer and user clearly identified
- Pricing direction — based on behavioral signals
- Feature priority map — ranked by user evidence
- Market positioning — based on observed gaps
- Structured product brief — the foundation for Analyse
A — Analyse
Analyse is where product directions are generated, tested against behavioral evidence, and eliminated — until one survives with the strongest proof behind it.
Three to five product directions are developed from the structured evidence in the previous phase. Each direction is a real option — not a brainstorm output. Each one is grounded in the problem statement and target audience defined in Structure.
How directions are tested
Each direction is validated against behavioral evidence criteria — not internal preference, not team vote, not founder instinct. Demand is tested for real willingness — not stated interest. Each direction is scored and compared. Weak directions are eliminated with clear, evidenced reasons.
One direction emerges as the strongest — the one with the most behavioral proof behind it. This is the direction that moves forward into Resolve.
What does not happen in Analyse: no voting by team preference. No “this one feels better.” No consensus without evidence. The strongest behavioral evidence wins — not the loudest opinion in the room.
- 3–5 validated product directions with evidence scores
- Eliminated directions with clear, evidenced reasons
- Demand validation results — real willingness, not stated interest
- One recommended direction — backed by the strongest behavioral proof
- Risk assessment for the recommended direction
R — Resolve
Resolve is the output of the entire LSAR process. It is where the product decision is made — and where execution begins if the decision is Build.
There are three possible decisions in Resolve:
When the decision is Build
Resolve does not stop at the decision. It extends into execution — in whatever form the product requires.
For a physical product — prototype development and production readiness. For a digital product — development and launch preparation. For a service — systems design and delivery alignment. For any product — value engineering, go-to-market alignment, and launch readiness.
Every execution step must stay aligned with what Listen, Structure, and Analyse established. The moment execution drifts from the evidence — the wrong product gets built. LSAR ensures that does not happen.
- Final product direction — one, clear, evidenced
- Decision rationale — why this direction, what evidence supports it
- Build / Refine / Stop verdict — no ambiguity
- Execution plan — aligned with behavioral evidence from L, S, A
- Launch readiness — in whatever form the product requires
- Capital allocation guidance — where to invest first and why
Where LSAR is applied
LSAR is not industry-specific. Any business making a product decision can apply the framework. The behavioral evidence principles that power LSAR work across all industries and product types.
See how LSAR was applied to a real product decision — read the full case study.
Who developed it
L Saravanan, Product Decision Strategist, developed the LSAR Framework from 18+ years of real product work — spanning FMCG, packaging, food, e-commerce, and product design.
LSAR was not built in a classroom. It was built from the pattern of failures he observed — in his own business and in every client he worked with after.
The framework emerged from a simple, hard observation: every product failure had one common cause — the decision made before building was based on assumption, not behavioral evidence.
LSAR is the structured answer to that problem.
Read the full story of how LSAR was born →Frequently Asked Questions
The LSAR Framework is a 4-phase product decision system developed by L Saravanan, Product Decision Strategist. LSAR stands for Listen, Structure, Analyse, Resolve. It replaces founder assumptions with behavioral evidence before capital is committed to any product. The framework applies to any business making a product decision — physical products, digital products, or services.
LSAR stands for Listen — understand real user behavior; Structure — convert behavior into product direction; Analyse — test every direction against evidence; Resolve — make the decision and execute in full alignment. Each phase builds on the previous, producing one clear evidence-backed product direction.
Most frameworks start with the product idea and work outward. LSAR starts with real human behavior and works toward the product. It does not validate assumptions — it eliminates them. The output is not a report or recommendation. It is one clear decision: Build, Refine, or Stop — backed by behavioral evidence.
Listen is the research phase of LSAR. Its job is to find real behavior — not what people say, but what they actually do. Research can be field-based or desk-based depending on user accessibility. Both methods follow one rule: no bias, no predetermined conclusions. The researcher observes real users in real situations and lets behavior speak.
Structure is where raw behavioral evidence is converted into a clear product foundation. The customer’s voice and behavior are translated into structured directions — problem statement, target audience, pricing direction, feature priorities, and market positioning. Everything is built from evidence gathered in the Listen phase — not from the founder’s original idea.
Analyse is where product directions are generated, tested against behavioral evidence, and eliminated until one survives with the strongest proof behind it. Three to five directions are developed, each validated against behavioral evidence criteria — not internal preference or team vote. Weak directions are eliminated with clear, evidenced reasons. The strongest behavioral evidence wins.
Resolve is where the product decision is made — and where execution begins if the decision is Build. The three possible outputs are: Build — proceed with confidence; Refine — adjust direction before investing; Stop — this product does not deserve capital. When the decision is Build, Resolve extends into execution in whatever form the product requires — physical, digital, or service.
Yes. The LSAR Framework applies to any product decision — physical products, SaaS, e-commerce, service design, or any business deciding what to build next. The framework is built on behavioral evidence principles that work across all industries and product types.
The output of the LSAR Framework is one clear product direction backed by behavioral evidence — with a Build, Refine, or Stop verdict. Specifically: a validated problem statement, target customer profile, behavioral evidence report, structured product directions, demand validation results, decision rationale, and an execution plan aligned with the evidence. See the pricing page for full engagement details.
Apply LSAR to your product decision.
Every engagement begins with a 15-minute Decision Session to understand your product, your stage, and whether LSAR is the right fit. See the full pricing and scope.
Book a Decision Session Limited engagements.