FeatureBenefit Map

Feature/Benefit Map


You want to make certain that key marketing objectives match key development efforts. You have a Market Map to identify the key market segments you're targeting.


What is the best way to capture compelling features and their benefits for each market segment?


  • People often think they understand the key features and benefits for a given market segment when they really don't.

  • A feature may be a benefit to more than one market segment.

  • Features that apply to multiple market segments may not provide the same perceived benefits to each one.

  • Developers tend to think of features (cool), while marketing people tend to think of benefits (compelling advantages, reasons to purchase). This gap often results in poorly designed products and/or products that can't win in the market.

  • Developers need to understand the nature and intent of future benefits so that they can be certain the tarchitecture is designed to meet them.


For each market segment capture the key features and benefits that motivate to purchase the product. It is crucial that you list features and benefits together. Omitting one gives the other inappropriate influence.

Choose an ordering for your map that makes the most sense. I've had good results ordering first by time and then by difficulty/complexity. Others get good results from ordering by what the market wants or what sales can sell. Paul Germeraad from Intellectual Assets, Inc., has organized features into a product tree where the edges of the tree are the features in the last release. The features of the next release are placed around those edges. Paul draws lines around the features proposed for the next release. One advantage of this visualization is that the entire company can feel good about the growth of their product. Another is very practical: The expanding size of the perimeter correlates with the growth of the product development organization. As the product tree grows, so do the needs of the team in caring for and feeding it (including the maintenance team).

Resulting Context

You have a representation of the key features and associated benefits needed to attack target market segments. This will provide the technical team with the data they need to update their tarchitecture map so they can realize these features.

Related Patterns

  • Market Map

  • Tarchitecture Roadmap

Beyond Software Architecture[c] Creating and Sustaining Winning Solutions
Beyond Software Architecture[c] Creating and Sustaining Winning Solutions
ISBN: 201775948
Year: 2005
Pages: 202

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net