What’s your product vision?
As a product leader, you already know that the most powerful way to align the independent teams you need — user experience, product marketing, sales, executives, etc. — without any authority is a compelling product vision.
Adam Nash refers to a strong product leader as a force multiplier. People respond if you paint an image of a place worth going, and a credible plan (your product roadmap) for getting there.
Product management teams have traditionally been responsible for delivering documents full of requirements: Market Requirements Documents (MRDs) that define problems experienced by some segment(s) of the market, and Product Requirements Documents (PRDs) that define a solution to be built.
Traditional software efforts–perhaps coincidentally–have been notoriously unsuccessful. Many of the software efforts surveyed were internal technology projects, but commercial software products haven’t had a dramatically different outcome.
Have a product in customers’ hands?
Get ready for an unending river of feature requests! A common problem among product management professionals is how to handle requests from clients and prospects in various market segments, along with strategic initiatives. “They’re all good ideas!” Handling feature requests combines several distinct problems:
- Tracking requests, usually including the submitting party and the date.
- Identifying the underlying problem.
- Prioritizing the changes to the product.
Product management professionals are always looking for a way to get to market faster. One common-sense way to do this is to build less prior to market launch. So what’s the least you can possibly build?
We product people seem to really like the canvas!
In my world, there are three canvases which have gained some traction….Wait, make that four.
What is Interaction Design?
Smartphone screens are small. Very small.
Because they’re small, there’s no room for unnecessary information. For this reason, interaction design–the design of exactly what is necessary for a user to flow through the system to accomplish a goal–is of primary importance in mobile. Because many mobile consumer applications also have web components, the discipline has also bled over to the consumer web.
Can a Product Roadmap De-Emphasize Dates?
In a recent post, I wrote about Selling roadmap items. To communicate “what’s coming” with Sales, Product uses an internal roadmap–and if not carefully formatted, this document may convey more certainty than is accurate. One of the strategies I suggested is to publish a product roadmap without dates.
Are you selling slots on your roadmap?
One of the problems B2B software companies struggle with is the proper application of a product roadmap. Sales teams want to know what’s coming up in future releases, so they can appeal to customer problems the product will solve in future releases. This form of “selling the future” carries the risk of enticing the customer with a feature that never arrives, or arrives later than expected. Both of these negative outcomes can naturally cause problems for the company after the deal is signed.