Use Cases and Product Roadmaps

A few days ago, Random linked to a product roadmap for Firefox, a web browser. A product roadmap shows the expected changes to a product over time.

Product roadmaps can have different audiences, and I believe the format of the roadmap should depend on the audience a product manager is trying to target. One common format for a roadmap shows features that the company plans to add to the product. Users and analysts are accustomed to thinking about products in terms of features, so to some extent this format is helpful and natural.

However, particularly if the audience for the product roadmap is internal, it might be worthwhile to orient it around use cases rather than features. The high-level use cases for a product typically don't change much during its lifetime. Yet the constraints around these use cases do change; even if the use cases stay the same, you make the product easier to use, more secure, or more reliable.

One way to format your product roadmap, therefore, is in terms of the use cases and the enhanced constraints you will attach to them as the product matures. How much easier will it be to use your product, in measurable terms? How much more secure will your product be, in measurable terms? How much more reliable will your product be, in measurable terms? You don't even have to mention the features that will lead to these improvements.

Comments

bob said…

OhmyGod, don't leave home without your Safe Harbor statement when it comes to talking up roadmaps, espcially if you're selling software (vs giving it away, as Firefox so generously does).

And please, please, please, never put anything in writing for a customer without that same Safe Harbor statement and (hopefully) a rock-solid NDA.

It's not like we don't want to talk to customers and share our directions with them - just be careful about what you commit to.

Fri Feb 03, 10:24:00 AM 2006

Roger L. Cauvin said…

I share your call for extreme caution when making promises to customers. If we are "forced" to make commitments to customers, we should do what we can to set expectations low and overdeliver.

Fri Feb 03, 10:43:00 AM 2006

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...

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 ...

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problems she faces or the ...

Cauvin

Search This Blog