What Is a Product?

Imagine Spotify.

Spotify is the product.

“Download songs for offline listening” is a feature inside the product.

That distinction matters because PM conversations get messy when every feature request gets treated like a product problem.

A useful way to think about a product:

Something people repeatedly use because it helps them make progress.

Spotify helps you listen to music.

Uber helps you get somewhere.

Slack helps a team communicate.

The technology matters, but the value comes first.

A project is a piece of work with a defined end.

For example:

Migrate the company website by September.

A product keeps being used and improved after launch.

Spotify does not “finish” after one release. People keep using it, the team keeps learning, and the product keeps changing.

A feature is one part of a product.

For Spotify:

• product: Spotify
• feature: collaborative playlists
• feature: offline listening
• feature: Discover Weekly

A feature can be well built and still add very little value to the product.

Suppose Spotify launches a new sharing feature.

It ships on time.

There are no major bugs.

Almost nobody uses it.

Was the project delivered successfully?

Probably.

Was the product decision successful?

Probably not.

Different question.

A PM should not only ask:

Did we build what we planned?

Also ask:

Did this make the product more useful for the user or more valuable for the business?

That question changes what “success” means.

A feature is something you build.

A product is the ongoing system of value around it.

Your job is not to maximize how much gets built.

It is to help the product become more useful.