How to you help stakeholders parse the difference between what’s a feature and what’s a benefit?
Pranav Deshpande
Vanta Senior Product Marketing Manager | Formerly Twilio • May 10
In my opinion, benefits need to describe the outcome of using the feature. The outcome should address a real pain point for the target customer of the feature. The benefit should also be relative to the next best alternative available to the target customer.
When we draft positioning statements for our products at Modern Treasury, we make sure they separately articulate pain points, alternatives, and top benefits for each key product feature. For example, for our Payments product, 'Direct bank connectivity' is a feature and 'Focus on shipping your core product faster instead of figuring out how to integrate with different banks and payment methods' is the associated benefit.
1195 Views
Top Product Marketing Mentors
Mary Sheehan
Adobe Head of Lightroom Product Marketing
Brianne Shally
Nextdoor Ex-Head of Product Marketing
Jeffrey Vocell
Panorama Education Head of Product Marketing
Marcus Andrews
Pendo Sr. Director of Product Marketing
Kevin Garcia
Anthropic Product Marketing Leader
Leah Brite
Gusto Head of Product Marketing, Employers
Susan "Spark" Park
Monzo Director of Product Marketing
Jeff Hardison
Calendly VP of Product Marketing
April Rassa
Clari VP, Solutions Marketing
Julien Sauvage
Clari VP, Brand, Content and Product Marketing
Related Questions
Should messaging/positioning change from release to release? Or should it be broad enough to carry you through at least a year?How should a startup approach what to name their new category? How important is it to do that and how should the company weave that name into their messaging?What are the assets that product marketing owns? And the best way to vet the assets with key stakeholders? Can you share your experience about segmentation and personas definition? At our start-up we have a history of deeply understanding our users' needs and can create loyalty and retention. But we find we are so careful about getting it "right" when it comes to what our product does that we lose the succint, repeatable marketing message. Do you feel that a succinct, hook-worthy statement that is 80% "right" is better than a "right" statement that is convoluted and hard to remember? Can you validate product messaging via website testing on a small percentage of traffic?