Viewing entries tagged with 'product roadmap'
In my prior article I discussed my favorite alternative to conventional product roadmaps. That article seemed to strike a chord in people, and I received quite a bit of very positive feedback. However, I also received more than a few questions. This didn’t really surprise me because as I said in the article, this is not a minor topic. But in my back and forth with people, I realized that there were several common and often significant confusions, and sometimes, the discussions would expose a more serious misunderstanding about product and how product teams work.
I have always loved the General George Patton quote: “Don’t tell people what to do; tell them what you need accomplished, and you’ll be amazed at the results.”
Every week I continue to find product teams laboring away on old-style product roadmaps that have been painstakingly negotiated with management and stakeholders, sometimes for several quarters in advance. I have written several times about the problems with this approach and why it so seldom results in the business impact that the organization was hoping for (see The Opportunity Backlog and Product Roadmaps).
I can¹t tell you how many times product managers have shown me their sophisticated spreadsheets and algorithms for prioritizing their long laundry list of feature requests (weighting various factors like cost, complexity, risk, customer impact, projected sales impact, documentation, dependencies, etc.) eventually leading to a single aggregated prioritized roadmap.