The product roadmap is a well-liked product administration software that communicates how a product is prone to evolve. However regardless of its reputation, it’s not all the time relevant. On this article, I share three situations by which utilizing a roadmap shouldn’t be advisable. I clarify why that’s, what you are able to do as a substitute to plan forward, and which steps you’ll be able to take to get nearer to creating a practical, actionable roadmap.
Hearken to the audio model of this text:
You Can’t See Additional than the Subsequent Three Months
A product roadmap ought to be a lifelike forecast that states the precise worth a product is prone to supply within the subsequent 12 months.[1] Creating such a forecast shouldn’t be all the time possible, particularly whenever you work on a brand new, revolutionary product.
When you can’t see additional than the following three months, then don’t use a product roadmap. In any other case, your plan is prone to be incorrect, which might result in disenchanted stakeholders and growth groups.[2] Within the worst case, they’ll lose belief in your capacity to information them.
As an alternative of constructing a roadmap, set a single, outcome-based purpose for the following three months. The purpose ought to state the constructive affect you need to create for the customers/clients and the enterprise. An instance for a healthy-eating product is likely to be “assist the customers perceive their consuming habits and purchase an preliminary consumer base.” Use the purpose to find out which options must be carried out to create the specified final result, for instance, providing a healthy-eating dashboard and seamless integration with main smartwatches. A sensible method to do that is to focus the product backlog on the purpose you’ve chosen.
After getting achieved the purpose, you’ll hopefully higher perceive how one can progress your product and have the ability to create a practical roadmap.[3] If that’s not the case, verify that you’ve a validated product technique, on which you’ll base the roadmap.
You Lack a Validated Product Technique
A typical reason for groups struggling to create a practical product roadmap is a scarcity of a validated product technique. Earlier than I clarify what I imply by validated, let me briefly describe what a product technique is.
A product technique describes the strategy you’ve chosen to attain product success. It states the goal group—the customers and clients, their wants, the specified enterprise objectives, and the capabilities that may set the product aside from competing choices.[4] A helpful software to seize the technique is my Product Imaginative and prescient Board, which you’ll obtain totally free along with a useful guidelines from my web site.
A validated technique is freed from important dangers and assumptions. It’s backed up by empirical proof: You’ve gotten related information to indicate that you’ve made the suitable strategic selections and chosen the suitable goal group, wants, enterprise objectives, and standout options. Executing the technique is subsequently prone to end in a profitable product.
An effective way to validate a product technique is to observe an iterative, four-step course of. As I clarify this strategy in additional element within the article Product Technique Discovery, I’ll simply present an summary right here.
Begin by choosing the largest threat contained within the technique—the uncertainty that should be addressed now so that you simply don’t make the incorrect selections and take the product down the incorrect path. Second, decide how one can finest deal with the chance you’ve chosen, as an illustration, by observing goal customers or constructing throwaway prototypes. Third, perform the required work and accumulate the related information. Fourth, consider the outcomes and use the newly gained insights to resolve find out how to right and refine the technique. Comply with this course of till you’ve addressed all main dangers.
With a validated technique in place, you’re in an awesome place to construct a practical, actionable product roadmap. There are two causes for this: First, having carried out the required technique discovery work, you’ve acquired the related information to make efficient roadmapping selections. Second, the technique varieties the premise for constructing an efficient product roadmap. The wants and enterprise objectives said within the technique assist you choose the suitable roadmap objectives. You might even have the ability to derive the outcomes on the roadmap instantly from the product technique by breaking the wants and enterprise objectives into extra particular subgoals, as Determine 1 reveals.[5]
Conversely, if you happen to don’t have a validated technique, you lack the premise for creating a practical, actionable product roadmap. If that’s the case, cease and perform the required technique discovery work. Then proceed constructing the roadmap.
Stakeholders Dictate the Roadmap Content material or View It as an Unchangeable Dedication
In my teaching work, I typically meet stakeholders who insist on getting particular options onto the product roadmap and who count on that their options can be delivered as said within the plan.
Often, there are two points at play on this scenario: First, the product supervisor/product proprietor lacks the required empowerment and finds it onerous to say no to the stakeholders. Second, the stakeholders are used to a conventional planning strategy. They see the product roadmap as a feature-based, mounted plan as a substitute of an outcome-based one that’s frequently reviewed and tailored.
My preliminary recommendation is to attempt to repair these causes: Work in your empowerment by rising your lateral management capability and lobbying for extra assist from senior administration, as I clarify within the article Understanding Empowerment in Product Administration. Moreover, use an outcome-based, adaptive roadmap like my GO Product Roadmap as a substitute of a conventional feature-based plan.
But when this fails, then I like to recommend not utilizing a product roadmap. In any other case, you threat ending up with a Frankenstein product—a unfastened assortment of options that may please the stakeholders however don’t create a lot worth for the customers and the enterprise as a complete. What’s extra, if the roadmap is seen as an unchangeable dedication, implementing it might end in a “demise march” the place the event groups frequently work additional time and find yourself being exhausted. Consequently, productiveness drops, individuals’s well being suffers, and software program high quality is compromised—which can make it tougher to boost the product sooner or later.
As an alternative of utilizing a roadmap, set a three-month purpose as advisable earlier, ideally along with the stakeholders. A collaborative strategy provides three advantages. First, it will increase the probabilities that the stakeholders will assist the purpose. Second, it helps you construct belief, which will increase your capacity to affect and information them. Third, it units you on the trail to adopting outcome-based roadmaps, as I clarify within the article How one can Get Began with End result-Based mostly Product Roadmaps.
Notes
[1] The time-frame said applies to digital merchandise. For hardware-based ones, you could require a bigger interval, say, 18 or 24 months.
[2] Whereas a product roadmap is prone to change, it ought to be secure sufficient for the next one to 3 months. If the plan modifications, say, each two weeks, the speed of change is just too excessive. The roadmap is now not a helpful, sufficiently dependable plan.
[3] Moreover, you’ve taken step one to utilizing an outcome-based, goal-oriented product roadmap, as I clarify in additional element within the article How one can Get Began with End result-Based mostly Product Roadmaps.
[4] The stand-out options are particularly vital for a revenue-generating product, as they show you how to accurately place it.
[5] I focus on the connection between the product technique and roadmap in additional element within the article Roman’s Product Technique Mannequin.