Product is the core value that you pay for, delivered through features, apps, or hardware. Features are the building blocks — not the product itself.
Product is the carrier of value that customers pay for directly. Features are the components that deliver that value — but they are not the product itself. This distinction is critical because most PMs confuse features with products and end up building feature factories rather than meaningful products.
Your actual job is to focus on the core value the product delivers, then decide which features best enable that value — not to chase every shiny idea or stakeholder request.
Product versus features: The core, actual, and augmented product layers
Philip Kotler’s classic framework remains relevant: products have three layers.
| Layer | What it means | Example: Washing machine | Example: Instagram |
|---|---|---|---|
| Core product | The fundamental benefit users pay for | Convenience: clean clothes effortlessly | Social validation through sharing images |
| Actual product | The physical/digital components that deliver the core | Drum, heater, controls | Feed, filters, camera, stories |
| Augmented product | Additional services or features that support the experience | Warranty, installation, customer service | Creator tools, analytics, help center |
Many PMs obsess about the actual product layer — the features and UI — without stepping back to ask what core value they are enabling or how the augmented layer can increase engagement or retention.
In India, this distinction matters especially. Take a chair as a product: the core value is comfortable seating. But an augmented feature like a fitness reminder indicator can deepen engagement and differentiate your product.
The trap of feature factory thinking
Many companies, including in India, fall into the trap of becoming feature factories — churning out features to please stakeholders or match competitors, without a clear connection to user value. This leads to bloated products, technical debt, and confused users.
The pattern is consistent: features without clear user benefit cause churn and cost. Features that don’t solve the core problem dilute your product’s identity.
What I tell PMs is: every feature must tie back to the user’s core job-to-be-done or the business’s strategic outcomes. If you cannot make that connection, say no.
How to evaluate a feature idea
When a feature idea lands on your desk, apply these questions:
- What user problem does this feature solve?
- How does this feature improve the core value or user experience?
- What metrics will show if the feature succeeds?
- What is the cost of building and maintaining this feature?
- Does this feature align with our product vision and strategy?
If the answers are vague or the feature is a “nice-to-have” with no clear benefit, deprioritize or reject it.
Indian startups often get feature requests from sales teams chasing large enterprise deals or from founders wanting to impress investors. Your job is to push back and prioritize ruthlessly.
Feature prioritization meeting at a Series A fintech startup in Bangalore
Founder: “Our client wants a dashboard with 50 metrics. We must build it.”
You (PM): “Which metrics do users actually act on? Can we start with the top 5 that impact decisions?”
Sales Head: “They said 50 are important.”
You (PM): “We risk building a confusing product. Let's validate which metrics drive outcomes first.”
CTO: “Agreed. Let's prototype with fewer metrics.”
Balancing sales demands with product focus
Prioritization frameworks for features
To decide what to build next, frameworks help you cut through noise. Here are two that work well:
RICE (Reach, Impact, Confidence, Effort)
- Reach: How many users will this feature affect in a given period?
- Impact: How much will it improve the user experience or business metric?
- Confidence: How sure are you about reach and impact estimates?
- Effort: How much engineering time will it take?
Calculate a score: (Reach × Impact × Confidence) ÷ Effort. Prioritize features with higher scores.
Kano Model
Classify features as:
- Must-haves: Basic expectations. No feature means user dissatisfaction.
- Performance: The more you provide, the happier users get.
- Delighters: Unexpected features that create joy but are not expected.
Focus first on must-haves and performance features aligned to your core value.
In India, where resources are limited, the RICE framework’s emphasis on confidence and effort helps avoid over-investing in features that may not deliver.
The feature lifecycle: from ideas to sunsetting
Features are not forever. Some will fail, others become obsolete.
Good PMs track feature usage and impact continuously. If a feature is unused or causes confusion, consider sunsetting it.
Indian companies like Razorpay regularly review feature adoption and prune aggressively to maintain product clarity.
Field exercise: Evaluate your product’s features
Choose a product you use daily — Swiggy, PhonePe, or a SaaS tool. For each major feature:
- Identify which product layer it belongs to (core, actual, augmented).
- Write down the user problem it solves.
- Assess its impact on user value or business goals.
- Estimate the effort to build and maintain it.
- Decide if it should be prioritized, maintained, improved, or sunsetted.
Spend 15 minutes on this. Reflect on how many features truly deliver core value versus being “nice-to-haves.”
Test yourself: Prioritizing features under pressure
You are a PM at a Series B Indian SaaS startup. The sales team demands a complex reporting feature requested by a top client (₹20 crore ARR). Engineering says it will take 3 months. The product vision focuses on improving onboarding experience, which affects churn critically. The CEO wants you to decide what to do.
The call: How do you respond to the sales request? What factors guide your prioritization and communication?
Your reasoning:
You are a PM at a Series B Indian SaaS startup. The sales team demands a complex reporting feature requested by a top client (₹20 crore ARR). Engineering says it will take 3 months. The product vision focuses on improving onboarding experience, which affects churn critically. The CEO wants you to decide what to do.
Your task: How do you respond to the sales request? What factors guide your prioritization and communication?
your reasoning:
Alumni perspective
Where to go next
- Build a product vision that guides feature decisions: Product Vision and Strategy
- Master user research to uncover real needs behind feature requests: User Research Methods
- Learn to write clear product requirements for features: Product Requirements Document
- Prepare for stakeholder management and negotiation: Stakeholder Management