I like this framing of product opportunites from Jason Fried around “questions and answers” instead of “features and benefits.”

When making products, you can think of them as a collection of features or answers.

Some people may say “you mean features or benefits?” No, I mean answers. Answers are counterpoints to questions people have in their heads. Answers fill holes, answers snap into sockets. Benefits don’t have such places in people’s minds.

For example, you could make a feature that shows you which tasks are overdue. Or, you can build something that answers the question “What’s late?”

Emphasis mine.