If you ask ten product people what a product is, you’ll probably get twelve answers, and at least three small arguments. Some say it’s a thing you sell. Others claim it’s a service. A few will use nice buzzwords along the lines of “value delivery.” We’ve spent years dissecting that question, and spoiler alert: a product isn’t a feature, a backlog item, or a shiny app. And you might not like the answer, but it depends.
Just like a body, it has anatomy: a spark that gives it life, DNA that defines who it is, a skeleton that holds it up, and nerves, muscles, and lungs that keep it moving and breathing. A product isn’t a project. It’s an organism that grows, adapts, and, if we’re not careful, decays.
So, what makes something a product instead of “just stuff we built”?
The Heart of It: Intent and Boundaries
You can consider a product a catalyst for change with positive intent. That begins with the intent in mind. It’s something created on purpose: to solve a problem, fill a gap, or make life a bit better for someone. That intent is what separates a product from a raw resource. Sand on a beach isn’t a product; sand turned into glass for something is.
But intent alone isn’t enough; you also need boundaries. Think of boundaries as drawing your product’s “box.” Where does it start, and where does it stop? A fingerprint scanner can be the product for a security company, but just a component inside an airport’s passenger-flow service. Context decides everything. Those edges define ownership, budget, and accountability, and ultimately keep you sane.
Once you’ve drawn your box, you’ve got some perspective. What should be inside it, what should be outside, and what should be excluded. From the inside, your product might look like architecture, APIs, and dashboards; from the outside, it’s simply “how fast I get through security” or “how easy it is to pay.” Both views are valid, but customers only care about their own. That’s why a product should always be defined through the lens of the people using it, not the people building it.
The Body: Systems Working Together
A single organ can’t survive without the rest. The same goes for products. They have:
A Skeleton: Structure and Strength The architecture, the workflows, the decisions that make it stand up under stress. No skeleton, no posture. Build it flexible enough to evolve but strong enough to support growth.
A Nervous System: Sensing and Learning Feedback, analytics, customer signals, elements that are your product’s nerves. Ignore them, and you go numb. Listen well, and you adapt before problems become diseases.
A Circulatory System: Value Flow Marketing, distribution, onboarding, how value moves from you to your users and back again. A great product keeps blood (and feedback) pumping constantly.
A Digestive System: Input and Nutrition Healthy products feed on good data, a clear strategy, and sustainable funding. Garbage in, garbage out. Feed them junk metrics and you’ll get bloat and fatigue.
A Respiratory System: Communication and Support Products breathe through conversation: support tickets, release notes, changelogs, and transparency. When communication stops, trust suffocates. And that trust is essential to delivering value.
Products can even reproduce through extensions, new markets, or spin-offs. But reproduction only works if the DNA is healthy and consistent. Cloning chaos multiplies chaos. Scale small dysfunctions and they become big dysfunctions.
The trick is to see all of this as a connected ecosystem, not as isolated departments. Engineering without marketing is like lungs without a heart. Design without feedback is eyesight without nerves. When the systems collaborate, the product feels alive to users, even if they can’t explain why.
More Than a Thing
So, what’s a product? Its purpose is made tangible inside defined boundaries, sustained by interconnected systems that together create value for users and for the organization. That’s why, in The Anatomy of a Product, we don’t describe backlog refinement or metrics as the main event. Those are just vital signs. What matters is the organism’s overall health: does it learn, adapt, and deliver meaning? Next time your stakeholders come to you with a feature to build, ask them how it feeds the ecosystem (or doesn’t) and how it supports the overall survival and vitality of the product.
Because in the end, a great product isn’t built. It’s grown.
What Is a Product, Really?
If you ask ten product people what a product is, you’ll probably get twelve answers, and at least three small arguments. Some say it’s a thing you sell. Others claim it’s a service. A few will use nice buzzwords along the lines of “value delivery.” We’ve spent years dissecting that question, and spoiler alert: a product isn’t a feature, a backlog item, or a shiny app.
And you might not like the answer, but it depends.
Just like a body, it has anatomy: a spark that gives it life, DNA that defines who it is, a skeleton that holds it up, and nerves, muscles, and lungs that keep it moving and breathing. A product isn’t a project. It’s an organism that grows, adapts, and, if we’re not careful, decays.
So, what makes something a product instead of “just stuff we built”?
The Heart of It: Intent and Boundaries
You can consider a product a catalyst for change with positive intent. That begins with the intent in mind. It’s something created on purpose: to solve a problem, fill a gap, or make life a bit better for someone. That intent is what separates a product from a raw resource. Sand on a beach isn’t a product; sand turned into glass for something is.
But intent alone isn’t enough; you also need boundaries. Think of boundaries as drawing your product’s “box.” Where does it start, and where does it stop? A fingerprint scanner can be the product for a security company, but just a component inside an airport’s passenger-flow service. Context decides everything. Those edges define ownership, budget, and accountability, and ultimately keep you sane.
Once you’ve drawn your box, you’ve got some perspective. What should be inside it, what should be outside, and what should be excluded. From the inside, your product might look like architecture, APIs, and dashboards; from the outside, it’s simply “how fast I get through security” or “how easy it is to pay.” Both views are valid, but customers only care about their own. That’s why a product should always be defined through the lens of the people using it, not the people building it.
The Body: Systems Working Together
A single organ can’t survive without the rest. The same goes for products. They have:
The architecture, the workflows, the decisions that make it stand up under stress. No skeleton, no posture. Build it flexible enough to evolve but strong enough to support growth.
Feedback, analytics, customer signals, elements that are your product’s nerves. Ignore them, and you go numb. Listen well, and you adapt before problems become diseases.
Marketing, distribution, onboarding, how value moves from you to your users and back again. A great product keeps blood (and feedback) pumping constantly.
Healthy products feed on good data, a clear strategy, and sustainable funding. Garbage in, garbage out. Feed them junk metrics and you’ll get bloat and fatigue.
Products breathe through conversation: support tickets, release notes, changelogs, and transparency. When communication stops, trust suffocates. And that trust is essential to delivering value.
Products can even reproduce through extensions, new markets, or spin-offs. But reproduction only works if the DNA is healthy and consistent. Cloning chaos multiplies chaos. Scale small dysfunctions and they become big dysfunctions.
The trick is to see all of this as a connected ecosystem, not as isolated departments. Engineering without marketing is like lungs without a heart. Design without feedback is eyesight without nerves. When the systems collaborate, the product feels alive to users, even if they can’t explain why.
More Than a Thing
So, what’s a product? Its purpose is made tangible inside defined boundaries, sustained by interconnected systems that together create value for users and for the organization. That’s why, in The Anatomy of a Product, we don’t describe backlog refinement or metrics as the main event. Those are just vital signs. What matters is the organism’s overall health: does it learn, adapt, and deliver meaning? Next time your stakeholders come to you with a feature to build, ask them how it feeds the ecosystem (or doesn’t) and how it supports the overall survival and vitality of the product.
Because in the end, a great product isn’t built. It’s grown.
2 replies to “What Is a Product, Really?”
Biplab Subedi
One of the finest articles, I’ve come across. Thank you, Sander!
SanderDur
Much appreciated!:)