A product is the carrier of value that customers pay for directly. Inside the company, features become products because the complexity demands it — but for users, the product is the value they get.
Products are all around us, and most people have a notional sense of what a product is. But that definition varies widely. The actual job is to use a consistent definition so you and your team are on the same page.
A product is the carrier of value that customers pay for directly. That payment might be money, time, or attention. The product is not the app, the website, or the hardware alone — it is the value those things deliver.
Getting this wrong leads to confusion about what you build, who owns it, and how to prioritize. This lesson will give you clarity.
The product is the value the user pays for — not the features
Consider Instagram. Instagram as a whole is a product. It offers a social feed, filters, hashtag search, stories, and more. These are features inside Instagram.
Users pay Instagram with their attention as they scroll and engage with the feed and filters. That attention is the currency. Instagram is the product; the features are the vehicles for delivering that value.
But inside Instagram, the industry parlance is different. The image feed is often called a product, the filters are called a product, and so on. Each has its own product manager.
Why? Because as products grow, their complexity explodes. Early on, Instagram had one product manager who wore many hats. But as the subsystems grew in scale and value, some of those subsystems became independently valuable and required dedicated owners.
Each subsystem is called a product internally — but for the user, it remains a feature of Instagram.
This distinction is critical. Internally, a feature becomes a product because it demands its own strategy, metrics, and roadmap. Externally, users see the whole experience as one product.
The value of a product is the sum of its parts — plus how they fit together
How do these two perspectives connect?
The value of a product is the sum total of value delivered by its subsystems — plus the value created by how they are assembled.
In Instagram’s case, users pay Instagram directly via their attention to the feed, filters, and stories. Those features are carriers of core value internally and thus treated as individual products.
You can visualize this like a factory assembly line: the output of one feature feeds into another, creating a seamless final product.
For the upstream feature, the downstream feature is a product because of the value it provides, which the upstream feature "pays" for internally. But from the user’s point of view, the product is what provides value directly.
Product is not the app, the hardware, or the interface — it is the value delivered
It is essential to keep this clear.
Product is the core value you pay for. This value may be delivered via an app, a hardware device, or a complex suite of both.
For example, an independent consultant’s product is the expertise you pay for. The deliverable might be a document or verbal advice, but the value is the expertise.
A doctor’s product is the medical advice you pay for, delivered through verbal instructions and prescriptions.
If you confuse the delivery mechanism with the product, you risk optimizing the wrong thing.
Kotler’s three layers of product apply in practice
From a marketing vantage point, Philip Kotler defined products in three layers:
| Level | What it is | Washing machine example | Instagram example |
|---|---|---|---|
| Core product | The benefit the user actually buys | Convenience — clean clothes without effort | Social validation via visual sharing |
| Actual product | The physical/digital thing delivering the core | Drums, heater, motor, controls | The app — feed, filters, camera, stories |
| Augmented product | Additional features supporting the experience | Warranty, installation, customer service | Creator tools, analytics, help center |
Good PMs understand all three layers. Great PMs know which layer to invest in at each stage of product maturity.
Modern product thinking extends beyond features to engagement platforms
The classical definition of product as a bundle of features is incomplete.
A product is also a platform for customer engagement that delivers value worth paying for repeatedly.
If your engagement machine is well built, customers keep coming back.
This is straightforward for software and hardware products. For example, as the iPhone home button product manager, you build features that keep users engaged with the device.
But consider a non-tech product: an office chair. The core value is functional, comfortable seating.
Viewed through a modern lens, the chair can also become an engagement product if it includes features like an indicator reminding users to stand up and move for health.
The exact implementation depends on many factors, but this illustrates how product management is evolving to include engagement as a core responsibility.
Embedded media: Talvinder explaining product concepts in a PLPM session
Test yourself: Identify core, actual, and augmented layers in a product you use
Choose a product you use daily — be it Swiggy, Google Pay, or a physical product like a chair.
Write down:
- Core product: What is the fundamental benefit you pay for?
- Actual product: What are the specific features or components delivering that benefit?
- Augmented product: What additional services or features support the core and actual product?
If this is difficult, pick a simpler product — a local tea stall, for example. What is the core value? What delivers that value? What is the augmented experience?
This exercise forces you to separate value from delivery and support.
The actual job is to think about product as value, not just features
Confusing features with products leads to fragmented ownership, misaligned priorities, and wasted effort.
The trap is to obsess over shipping features without understanding how they fit into the user’s experience of value.
Your actual job as a PM is to own the value the customer pays for — not the code, the screens, or the specs alone.
You must understand your product’s core value proposition and how your features and subsystems contribute to it.
Indian product examples reflect this pattern
Indian companies like Razorpay and Meesho have complex product ecosystems.
For instance, Razorpay’s payments product includes APIs, dashboards, fraud detection, and settlement features. Internally, each is treated as a product with its own PM.
But Razorpay’s customer pays for seamless payment acceptance and settlement — the core product.
Meesho’s social commerce platform has features like product search, reselling workflows, and social sharing. Each is a product internally but a feature externally.
Understanding this distinction is critical to managing priorities and measuring success.
Where to go next
- If you want to understand what product management actually is: What Is Product Management
- If you want to learn how to think about product strategy: Product Thinking
- If you want to build skills in user research: User Research Methods
- If you want to practice prioritization decisions: Prioritization Frameworks