Resources > Articles

Design Value Propositions Like User Stories: The 3WH Method

Post Author
  • Ben Snipes is the product line director for tax at Wolters Kluwer, where he is responsible for the overall product management, strategic vision, financial performance and growth execution of the tax product line in the legal and business markets. Ben earned an M.B.A. at Georgetown University?s McDonough School of Business and an LL.M. in taxation at the Georgetown Law Center. He earned a J.D. with International Law Certification from the Florida State University College of Law. Prior to earning his law degree, he earned a B.A. in political science and business administration from the University of Florida. He resides in New York City. Connect with Ben on LinkedIn at https://www.linkedin.com/in/benjaminsnipes.

Design Value Propositions Like User Stories: The 3WH Method

Value propositions are big-picture positioning statements that explain the benefit your product provides customers. They can also help your marketing team understand what resonates with your target audience. But how do you document and share these value propositions? My suggestion: Take a page from the agile playbook and apply user stories.

User stories are used in agile, lean startup and scrum for software development and normally follow this template:

As a <role>, I want <goal/desire> so that <benefit>.

Product development teams complete this template to clarify the end user, the desired objective and the benefit to build. The role is the who, the goal is the what and the benefit is the why. By understanding the customer’s fundamental motivations, developers can ensure they are serving customer needs and delivering satisfaction.

This same format can also be used to write value propositions that provide clear messaging around customer needs to sales and marketing. For that, I use the 3WH methodology, which incorporates <who>, <why>, <what> and <how>. Done early in the process, it can help guide the entire project.

Author

  • Ben Snipes is the product line director for tax at Wolters Kluwer, where he is responsible for the overall product management, strategic vision, financial performance and growth execution of the tax product line in the legal and business markets. Ben earned an M.B.A. at Georgetown University?s McDonough School of Business and an LL.M. in taxation at the Georgetown Law Center. He earned a J.D. with International Law Certification from the Florida State University College of Law. Prior to earning his law degree, he earned a B.A. in political science and business administration from the University of Florida. He resides in New York City. Connect with Ben on LinkedIn at https://www.linkedin.com/in/benjaminsnipes.

Author:

Other Resources in this Series

Most Recent

The image features the term use scenario being revealed underneath a ripped piece of paper
Article

What is a Use Scenario [ +7 Examples]

The purpose of drafting use scenarios is to help your development and design teams to start thinking about solutions. Context is the foundation of innovation, and you’ll be providing a tool that will be the starting point for collaborative and productive meetings.
Article

[Comprehensive Guide] Product Owner vs Product Manager

Learn how to separate the roles of product owner and product manager on Agile teams and uncover some common challenges with confusing these roles. Including a short primer on the Agile revolution.
Article

Use Scenarios are Stories That Provide Context

The problem with today’s user stories is that they aren’t interesting. And they aren’t stories. The solution is use scenarios. It’s a narrative. It explains the problem in the form of a real-life story.
Article

Benefits of Bundle Pricing

Bundle pricing is simply a strategy where services or products are packaged together for one (often reduced) price rather than priced separately. This article covers some benefits of bundle pricing followed by a system for getting started.
Article

A Quick Guide to Value-Based Pricing

Value-based pricing begins with knowing the customer’s willingness to pay based on the perceived value of your product. You can charge less than a customer’s willingness to pay, and they feel like they’ve received an

OTHER ArticleS

The image features the term use scenario being revealed underneath a ripped piece of paper
Article

What is a Use Scenario [ +7 Examples]

The purpose of drafting use scenarios is to help your development and design teams to start thinking about solutions. Context is the foundation of innovation, and you’ll be providing a tool that will be the starting point for collaborative and productive meetings.
Article

[Comprehensive Guide] Product Owner vs Product Manager

Learn how to separate the roles of product owner and product manager on Agile teams and uncover some common challenges with confusing these roles. Including a short primer on the Agile revolution.

Sign up to stay up to date on the latest industry best practices.

Sign up to received invites to upcoming webinars, updates on our recent podcast episodes and the latest on industry best practices.

Training on Your Schedule

Fill out the form today and our sales team will help you schedule your private Pragmatic training today.

Subscribe

Subscribe

Training on Your Schedule

Fill out the form today and our sales team will help you schedule your private Pragmatic training today.