#product-review.md
Version: 1.0.0
Target Models
- Sarvam-105B
- Sarvam-30B
- Sarvam Family
- Future Sarvam Models
#Purpose
This document defines the Product Review methodology.
Product review evaluates whether a feature delivers meaningful value to users and the business.
A technically correct implementation can still be a poor product.
The objective is to verify that every feature solves the correct problem, creates measurable value, aligns with business goals, and provides an excellent user experience.
Engineering builds software.
Product thinking builds successful software.
#Core Philosophy
Understand User
↓
Understand Business
↓
Validate Problem
↓
Evaluate Solution
↓
Measure Value
↓
Review Experience
↓
Approve
Every feature must justify its existence.
#Primary Objective
Every product review should answer one question.
"If this feature launches tomorrow, will users genuinely benefit from it?"
If the answer is uncertain,
the product requires improvement.
#Product Principles
Every feature should maximize
User Value
↓
Business Value
↓
Simplicity
↓
Clarity
↓
Trust
↓
Adoption
↓
Retention
↓
Long-Term Growth
Technology is the implementation.
Value is the objective.
#Product Review Workflow
Understand Users
↓
Understand Business Goals
↓
Understand Feature
↓
Review User Journey
↓
Review UX
↓
Review Metrics
↓
Review Risks
↓
Approve
#Stage 1 — Problem Validation
Verify
What problem exists?
Who experiences it?
How often does it occur?
How painful is it?
How is it solved today?
Never build solutions for imaginary problems.
#Stage 2 — User Review
Understand
Primary Users
Secondary Users
User Goals
User Motivation
User Behavior
User Expectations
Every feature should solve a user problem.
Not an engineering problem.
#Stage 3 — Business Review
Verify
Business Objective
Revenue Impact
Retention Impact
Growth Impact
Operational Impact
Strategic Alignment
Every feature should support business goals.
#Stage 4 — Value Review
Evaluate
Time Saved
Money Saved
Risk Reduced
Convenience Improved
Productivity Increased
Decision Quality Improved
The value proposition should be obvious.
#Stage 5 — User Journey Review
Review
Discovery
Onboarding
Navigation
Primary Task
Success State
Exit Flow
Retention Flow
Every step should feel intentional.
#Stage 6 — Feature Review
Inspect
Purpose
Scope
Complexity
Dependencies
Limitations
Edge Cases
Success Criteria
Features should solve one problem well.
#Stage 7 — Simplicity Review
Ask
Can this be simpler?
↓
Can steps be removed?
↓
Can decisions be reduced?
↓
Can friction be minimized?
↓
Can users succeed faster?
Simple products win.
#Stage 8 — UX Review
Evaluate
Clarity
Navigation
Feedback
Loading
Errors
Empty States
Recovery
User Confidence
Users should never feel lost.
#Stage 9 — Trust Review
Review
Professional Design
Clear Language
Reliable Behavior
Predictable Actions
Transparent Feedback
Privacy
Security
Trust is earned through consistency.
#Stage 10 — Engagement Review
Inspect
First Impression
Curiosity
Motivation
Progress
Rewards
Completion
Return Visits
Good products encourage continued use.
#Stage 11 — Accessibility Review
Verify
Inclusive Design
Keyboard Support
Readable Content
Touch Targets
Responsive Layout
Accessible products reach more users.
#Stage 12 — Performance Perception
Evaluate
Loading Speed
Responsiveness
Animations
Transitions
Optimistic UI
Skeleton States
Fast experiences increase user satisfaction.
#Stage 13 — Product Metrics
Review
Activation Rate
Feature Adoption
Retention
Session Length
Task Completion
Conversion
Drop-off Points
Error Rate
Products improve through measurement.
#Stage 14 — Competitive Review
Ask
How does this compare to similar products?
↓
Is it easier?
↓
Is it faster?
↓
Is it more useful?
↓
Why would users switch?
Every feature should have a competitive advantage.
#Stage 15 — Growth Review
Evaluate
Virality
Sharing
Referrals
Expansion
Collaboration
Network Effects
Organic Growth
Good products help acquire new users.
#Stage 16 — Scalability Review
Review
Future Features
Larger User Base
Localization
Enterprise Needs
Platform Expansion
API Support
Products should evolve naturally.
#Stage 17 — Risk Review
Identify
User Confusion
Adoption Risk
Business Risk
Technical Risk
Operational Risk
Security Risk
Legal Risk
Every significant risk should have mitigation.
#Stage 18 — Success Criteria
Verify
User Problem Solved
Business Goal Achieved
Positive UX
Acceptable Performance
Reliable Operation
Clear Metrics
Success should be measurable.
#Product Quality Attributes
Review
Useful
Usable
Desirable
Findable
Accessible
Credible
Reliable
Scalable
Profitable
Sustainable
#Product Questions
Before approval ask
Does this solve a real user problem?
↓
Would users use this repeatedly?
↓
Would users recommend it?
↓
Does it create measurable value?
↓
Does it support business objectives?
↓
Would removing this feature make the product worse?
↓
Would users pay for this capability?
#Severity Levels
Critical
Wrong problem
No user value
Business conflict
Major
Poor UX
High friction
Low adoption potential
Medium
Workflow improvements
Messaging improvements
Navigation issues
Minor
Micro UX
Copywriting
Visual polish
Suggestion
Future improvements
Additional insights
Growth opportunities
#Product Checklist
✓ Real user problem identified
✓ Business objective supported
✓ Clear value proposition
✓ Simple workflow
✓ Excellent UX
✓ Trustworthy experience
✓ Performance acceptable
✓ Success metrics defined
✓ Scalable solution
✓ Competitive advantage identified
✓ Risks reviewed
✓ Long-term product vision supported
#Anti-Patterns
Avoid
Building without validation
Feature bloat
Technology-first thinking
Ignoring user feedback
Overcomplicated workflows
Hidden value
Weak onboarding
Poor success metrics
Shipping features without purpose
Confusing business goals with user needs
#Definition of Done
Product review is complete when
- The feature solves a validated user problem.
- The value proposition is immediately clear.
- The user journey is intuitive and efficient.
- Business objectives are supported.
- Success metrics are defined.
- Risks have been evaluated.
- The feature improves the overall product.
- Users can discover, understand, and successfully use it.
- The implementation supports future growth.
- The product delivers meaningful, measurable value to both users and the business.
A successful product is not defined by the number of features it contains.
It is defined by how effectively it solves important problems for the people who use it.