A product is the carrier of value that customers pay for directly. The app, the website, the feature — they all carry value, but the product is the value itself.
Products are all around us. You already have a notional sense of what a product is. But that sense varies — and that variation causes confusion and miscommunication. The actual job is to have a clear, shared definition so you and your team build and manage the right things.
This lesson clarifies what a product is, how it differs from features, and how value flows through complex products with many moving parts. You will learn to see products not just as collections of features but as platforms that deliver value worth paying for.
The product is the carrier of value, not the features
Let’s start with a simple but crucial point: a product is the carrier of value that customers pay for directly. The value can be paid in money or attention, but it must be real and tangible to the customer.
Take Instagram as an example. Instagram is the product. Users pay Instagram via their attention — by scrolling the image feed, using filters, or searching hashtags. The feed, filters, and search are features inside Instagram.
Yet, inside Instagram’s teams, each of these features is often called a "product." There is a product manager for the image feed, another for filters, another for search. Why? Because Instagram grew so complex that its subsystems became valuable enough to need dedicated ownership.
This dual use of "product" creates confusion. For users, Instagram is the product; filters and image feed are features. For the company, these features are treated as independent products because each delivers distinct value and requires focused management.
The key is this: the overall product’s value is the sum of the value delivered by its subsystems — plus the value created by how those subsystems are assembled together. Think of it like a factory assembly line: the output of one subsystem feeds into the next, culminating in the final product that users pay for.
Why features become products internally
In the early days of Instagram, one product manager could handle the entire app. But as the product scaled, subsystems became complex and valuable enough to require dedicated PMs.
This is a common pattern in modern tech companies. Features grow into mini-products internally, each with their own roadmap, metrics, and teams. Yet externally, users see just one product with many features.
Understanding this distinction is critical for your role as a PM. You must know which level you own and how your subsystem contributes to the overall product value.
The product as value delivered, not the delivery mechanism
It is essential not to mix up the product with its delivery mechanism.
The product is the value itself — the benefit the customer receives. The delivery mechanism could be an app, a website, hardware, or even a human expert.
Consider an independent consultant. The product is their expertise — that value you pay for. The consultant delivers that value through verbal advice or written documents. Similarly, a doctor’s product is medical advice, delivered through consultation and prescriptions.
The delivery channels are just carriers of value. Your job is to focus on the value, not the form it takes.
Kotler’s three layers of product value
Marketing legend Philip Kotler defined three layers of product that help us understand how value is packaged and delivered:
| Layer | What it means | Washing Machine example | Instagram example |
|---|---|---|---|
| Core product | The fundamental benefit the user wants | Convenience — clean clothes without effort | Social validation via visual sharing |
| Actual product | The physical/digital thing delivering value | The machine — drums, heater, controls | The app — feed, filters, camera, stories |
| Augmented product | Additional features enhancing the experience | Warranty, installation, customer support | Creator tools, analytics, help center |
Your job as a PM is to understand these layers and decide where to invest effort depending on the stage and strategy of your product.
Extending the classical product definition: engagement as value
The classical definition of product focuses on features and benefits. But modern products are platforms for ongoing customer engagement.
If your engagement machine is well built, customers keep coming back. Engagement becomes a form of value in itself.
Take the iPhone. As a PM responsible for the home button, you might build features that keep users interacting with the device, increasing their satisfaction and loyalty.
Now consider a non-tech product — an office chair. The core value is a comfortable, functional seat. But imagine adding a feature: an indicator that reminds users to stand and move periodically to stay healthy. That feature turns the chair into a platform for active engagement, not just passive utility.
This engagement lens helps you see products as dynamic systems that deliver ongoing value beyond the initial transaction.
The trap of confusing internal and external product definitions
Many PMs confuse the internal product (a subsystem managed by a dedicated PM) with the external product (the overall value delivered to users).
This confusion leads to prioritizing internal metrics and roadmaps over user outcomes. It also causes misalignment when teams talk past each other — one team calls something a product, another calls it a feature.
The actual job is to keep the user’s perspective front and center: what is the product the user pays for? Features and subsystems exist to deliver that product’s value.
The assembly line analogy for product subsystems
Visualize the product’s subsystems as an assembly line in a factory. Each feature produces output that feeds into the next.
For example, Instagram’s image feed depends on the search feature to surface relevant content. The filters feature enhances the images shown in the feed.
For the upstream feature (image feed), the downstream feature (search) is a product it "pays for" internally because it relies on its value.
This perspective clarifies why internal teams treat features as products — because they deliver independent value to other parts of the system.
Why this matters for you as a PM
Understanding the difference between product and feature, and how value flows through subsystems, shapes your scope and priorities.
If you own a subsystem product, your focus is on maximizing its value contribution to the overall product.
If you see your work only as feature delivery, you risk becoming a ticket-pusher rather than a value creator.
The cleanest way to think about it: you manage the product that your users pay for — directly or indirectly. The features and subsystems are means to that end.
Summary: What a product really is
- A product is the carrier of value customers pay for — in money, time, or attention.
- Features are parts of a product that deliver value, but the product is the whole experience.
- Internally, features can become products if they deliver independent value and need dedicated ownership.
- The product’s value is the sum of its subsystems’ value plus how they integrate.
- Kotler’s three layers help you think about value: core benefit, actual product, and augmented product.
- Modern products are platforms for ongoing engagement, not just collections of features.
- Always keep the user’s perspective: what product are they paying for?
Test yourself: Product or feature?
You are a PM at a Series A Indian SaaS startup building a customer engagement platform. Your team is debating whether the new 'smart notifications' module should be called a feature or a product. The notifications depend on the analytics subsystem and feed into the user dashboard. The CEO wants to market 'smart notifications' as a standalone product to attract investors.
The call: Is 'smart notifications' a product or a feature? How do you explain this to your team and CEO?
Your reasoning:
Where to go next
- If you want to deepen your understanding of product thinking: Product Thinking Fundamentals
- If you want to master user research to validate product value: User Research Methods
- If you want to learn how to prioritize features that deliver core value: Prioritization Frameworks
- If you want to explore product-market fit concepts: Product-Market Fit
- If you want to understand the PM role in large, complex products: Managing Product Portfolios