What is a product

A product is something created to solve a problem or fulfill a need for a specific group of people. It can be physical, digital, or a combination - a smartphone, a software application, a subscription service, or an experience. What makes something a product isn't its form but its purpose: delivering value to users in exchange for something (money, attention, data, or engagement). Understanding what a product truly is shapes how product managers think about their work.

Why this definition matters

The question "what is a product?" seems basic, but how you answer it fundamentally shapes your approach to product management. If you think of your product as the code your engineers write, you'll focus on features and specifications. If you think of it as the problem you solve for users, you'll focus on outcomes and experiences. The second framing almost always leads to better products.

This definition matters because it determines where you look for success metrics, how you prioritize features, and how you communicate with stakeholders. A feature-centric view leads to counting what you build. A value-centric view leads to measuring what you enable.

Products as solutions to problems

At its core, a product exists because someone has a problem worth solving. The problem might be:

Functional - "I need to get from point A to point B" (transportation products)

Emotional - "I want to feel connected to friends" (social products)

Social - "I want others to see me as successful" (luxury products)

Aspirational - "I want to become a better version of myself" (education products)

Most products address multiple problem types simultaneously. A fitness app might solve functional problems (tracking workouts), emotional problems (feeling accomplished), and aspirational problems (becoming healthier). Understanding the full problem space helps product managers build more resonant solutions.

The layers of a product

Products operate on multiple levels simultaneously:

Core benefit. The fundamental need being addressed. For a drill, the core benefit isn't the drill itself - it's the hole. For a project management tool, it's not the software - it's coordinated work.

Actual product. The tangible or intangible thing delivered. Features, design, quality, branding - the specific implementation of the solution.

Augmented product. Everything surrounding the actual product that adds value. Support, community, integrations, documentation, the ecosystem of complementary offerings.

Strong products excel at all three layers. A mediocre core product with excellent support and ecosystem can outperform a superior core product delivered poorly. Product managers must think beyond the product itself to the entire experience of using it.

Digital products

In software and technology, products have distinctive characteristics:

Marginal cost approaches zero. Once built, serving additional users costs little. This enables business models impossible with physical goods.

Products evolve continuously. Unlike physical products that ship once, digital products update constantly. The product users have today differs from what they'll have next month.

Usage generates data. Digital products can observe how users interact with them, enabling optimization and personalization at scale.

Network effects are possible. Some digital products become more valuable as more people use them, creating powerful competitive dynamics.

Distribution is instant. Updates, new features, and fixes reach users immediately, anywhere in the world.

These characteristics make digital product management a distinct discipline, requiring approaches different from traditional product development.

Product vs. feature vs. solution

Clarity about terminology helps:

A product is a complete offering that stands alone in delivering value. Users can buy, use, and derive benefit from it independently.

A feature is a capability within a product. Features don't stand alone - they contribute to the product's value but aren't independently valuable.

A solution is broader than a product. It might encompass multiple products, services, and activities that together address a customer's need.

Sometimes the boundaries blur. A feature might become a product (Slack started as a feature within a gaming company). A product might become a feature of a larger platform (many standalone apps became features within operating systems). These evolutions reflect changing market dynamics and user expectations.

What makes a product good

A good product isn't just one that works - it's one that creates value efficiently. Good products share characteristics:

They solve a real problem. Not an imagined problem or a problem only interesting to the builders. Real problems that real users will pay to solve.

They solve it well. Better than alternatives, whether those alternatives are competitors, workarounds, or doing nothing.

They're usable. Users can actually get the value without excessive friction, learning curves, or frustration.

They're viable. The economics work. The product can sustain itself and the organization building it.

They're feasible. The team can actually build and maintain it with available resources and capabilities.

Great products often feel inevitable in retrospect - obvious solutions to obvious problems. But that obviousness is usually the result of deep understanding of users and relentless refinement of solutions.

The product as experience

Modern product thinking extends beyond the functional to embrace the entire user experience. The product isn't just what users do with your software - it's how they feel while doing it, how they describe it to others, how it fits into their lives.

This perspective shifts attention from features to journeys:

Every touchpoint shapes the user's relationship with the product. Product managers who think this broadly build more successful products than those who focus narrowly on functionality.

Products and markets

A product doesn't exist in isolation - it exists in relationship to a market. The same functionality might be a product in one context and irrelevant in another. Understanding the market means understanding:

Who are the users? What do they need, value, and struggle with?

Who are the buyers? In B2B contexts, users and buyers often differ. Both must find value.

Who are the competitors? What alternatives exist, including non-consumption?

What's the context? When, where, and how will users engage with the product?

Product-market fit - that magical state where a product meets a strong market need - remains the central challenge of product development. Tools like Klero help product managers understand their market more deeply by systematically capturing and analyzing user feedback, ensuring products evolve in response to real user needs rather than internal assumptions.

The ongoing question

"What is our product?" isn't a question you answer once. As markets shift, users evolve, and technology changes, the answer changes too. Products that started solving one problem often succeed by pivoting to solve a different one. The discipline of continually asking what your product truly is - what problem it solves, for whom, and why they care - keeps product development grounded in user value rather than internal momentum.