Skip to main content

Buying Features

One of Luke Hohmann's great innovation games is "Buy a Feature":
Create a list of potential features and provide each with a price. Just like for a real product, the price can be based on development costs, customer value, or something else. Although the price can be the actual cost you intend to charge for the feature, this is usually not required. Customers buy features that they want in the next release of your product using play money you give them. Make certain that some features are priced high enough that no one customer can buy them. Encourage customers to pool their money to buy especially important and/or expensive features. This will help motivate negotiations between customers as to which features are most important. This game works best with four to seven customers in a group, so that you can create more opportunities for customers to pool their money through negotiating.
A nice consequence of using this approach is that it gets customers away from the mentality that features come for free. They must prioritize and balance the value of features versus development costs.

If you haven't checked out Luke's book, Innovation Games, I definitely recommend it.

Nonetheless, in my next post, I will discuss an important limitation of this approach and propose a variation that addresses the limitation.

Comments

Post a Comment

Popular posts from this blog

Dancer Test

Are you left-brained or right-brained? Supposedly, your brain lateralization determines how you view this animation. Some people see her rotating clockwise. Others see her rotating counter-clockwise. Some see her unpredictably changing the direction of her rotation. Supposedly, people who see clockwise rotation are right brained. People who see counter-clockwise rotation are left brained. I originally came across this animation here .
6 comments
Read more

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos...
32 comments
Read more

5 Ways Companies Make Product Decisions

In the last blog entry, we reviewed the  four problems that companies face, or are trying to overcome, as they make product decisions .  Now we'll look at the ways that most companies make their product decisions. Companies that develop, market, and sell products and solutions make strategic and ongoing tactical decisions.  They decide what features to include in their products, what messages they will use to communicate the value of their products, what marketing tactics they will use, what prospective customers they will target, and many day-to-day choices. Whether or not these decisions are deliberate or ad hoc, most companies use some combination of the following ways of making product decisions. (A downloadable "map" that summarizes the product decision landscape is included at the end of this article.) Customer Wants Product decisions based on feature requests, focus groups, and what prospects and customers say they want. Companies are selling products to ...
12 comments
Read more