{"id":53436,"date":"2024-01-04T13:13:29","date_gmt":"2024-01-04T18:13:29","guid":{"rendered":"https:\/\/sdtimes.com\/?p=53436"},"modified":"2024-01-04T13:13:46","modified_gmt":"2024-01-04T18:13:46","slug":"the-pitfalls-of-product-roadmaps","status":"publish","type":"post","link":"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/","title":{"rendered":"The pitfalls of product roadmaps"},"content":{"rendered":"

Many organizations today assume a product roadmap is essential \u2013 the only logical way to understand where a product is right now and where it will be at specific points down the road. They believe a clear delineation of milestones and deadlines will give them a view into the future and, hopefully, some control over it.<\/span><\/p>\n

Internal stakeholders often seek clarity when the company\u2019s growth hinges on product revenue, as it does for many SaaS providers. The sales team is eager to know what new features they\u2019ll have to attract clients, and the marketing team is striving to build the brand and launch effective advertising and PR campaigns at exactly the right moment. Meanwhile, operations managers want to be ready with the resources needed in the days ahead. External clients are also conditioned to ask for a product roadmap, seeking assurance that the vendor is innovative, on top of the market and staying abreast of trends.<\/span><\/p>\n

For all these reasons, you\u2019re probably faced with regular requests for product roadmaps. Don\u2019t automatically comply. A roadmap is rarely the best way to give any of your stakeholders what they really want \u2013 an understanding of your product strategy and direction.<\/span><\/p>\n

Numerous downsides<\/b><\/p>\n

There\u2019s an inherent problem with roadmaps. Nobody can predict the future, so no roadmap will ever be 100% accurate. Things change. In fact, constant change is one of the hallmarks of a SaaS business. We need to be super nimble, agile and able to pivot quickly in an industry that\u2019s in perpetual motion.\u00a0<\/span><\/p>\n

When we design a time-driven schedule that commits to delivering X by Y, we\u2019ve created a no-win situation. If we don\u2019t follow our original plan, we lose credibility and the confidence of our customers as well as colleagues.\u00a0<\/span><\/p>\n

On the other hand, if we firmly adhere to a rigid schedule of deliverables, we lose the flexibility we need to adjust to new market conditions or customer needs. Pivoting from a plan takes time and money, slowing production and angering customers and partners. Delays stifle innovation and derail the creative process, frustrating developers. Under the pressure of fixed, unrealistic timelines, many businesses end up making poor decisions that dissatisfy all concerned.\u00a0<\/span><\/p>\n

A smarter solution\u00a0<\/b><\/p>\n

Rather than spelling out specific milestones and deadlines, consider a more fluid approach. If someone asks me where we\u2019re taking a product, I respond with a now\/next\/later continuum that pointedly does not include a calendar-based timeline spelling out when tasks will be done. Instead, I tell them what we\u2019re currently invested in, what we\u2019re doing next and what we expect to be doing later. Great discussions inevitably follow.<\/span><\/p>\n

As an R&D organization, we focus on the speed and frequency of delivery, breaking big projects down into bite-sized elements we can release more frequently. Continuous delivery makes much more sense than a predetermined schedule. We don\u2019t assure stakeholders we\u2019ll deliver something by a certain date; we promise to provide enhancements as soon as they\u2019re available. When you roll out a product or feature in frequent iterations over time, customers can enjoy the benefits of the various elements much sooner than if you delayed everything till the whole package was fully completed. In fact, I\u2019ve found that customers often realize that what they truly <\/span>need<\/span><\/i> is different to what they <\/span>say <\/span><\/i>they want<\/span>.<\/span><\/i> Delivering continuously reveals that moment much sooner.<\/span><\/p>\n

There will be occasions when clients request a roadmap because they\u2019re hoping for a solution to a problem they\u2019re experiencing. In that case, reframe the discussion to focus on the issue and not the timeline. Explore their specific problem and determine how to resolve it. Similarly, if customers anticipate an emerging need, figure out what features and capabilities they want. Build a robust, transparent Feature Request process and be sure to provide concrete feedback showing you hear their concerns and are investing appropriately, even if that means you won\u2019t work on their request. Any time a customer offers product feedback, listen up! You will almost always get added context that will inform future development and might even hear something that deserves immediate resources.<\/span><\/p>\n

The advantage of fast, frequent updates\u00a0<\/b><\/p>\n

Once you understand your customers\u2019 current and future needs, you can explain your product strategy \u2013 where you\u2019re investing to meet today\u2019s needs and solve today\u2019s problems, and where you expect to invest next. That\u2019s much more informative than a four-quarter timeline built on assumptions made today and possibly irrelevant tomorrow.<\/span><\/p>\n

This strategy makes sense considering the basic concept of SaaS, which eliminates the purchasing of packaged or downloadable software that\u2019s more or less frozen in time. A subscription allows customers to benefit from technology that’s always evolving and improving. Emphasizing that point helps your clients realize the inefficiency of date-driven schedules that actually stifle innovation.\u00a0<\/span><\/p>\n

Product roadmaps have become something of an anachronism in today\u2019s high-speed tech world. That doesn\u2019t mean you won\u2019t get requests for them. But rather than shackling yourself to an unrealistic schedule, train yourself to explain what you’re investing in now, next and later. Concentrate on developing continuous product enhancements that you release frequently, addressing real needs as they arise. Customers will see that you\u2019re moving ahead and ushering them into the future with you. <\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Many organizations today assume a product roadmap is essential \u2013 the only logical way to understand where a product is right now and where it will be at specific points down the road. They believe a clear delineation of milestones and deadlines will give them a view into the future and, hopefully, some control over … continue reading<\/a><\/p>\n","protected":false},"author":1197,"featured_media":53439,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"om_disable_all_campaigns":false,"cybocfi_hide_featured_image":"","footnotes":"","_links_to":"","_links_to_target":""},"categories":[1],"tags":[254,145],"coauthors":[16827],"acf":[],"yoast_head":"\nThe pitfalls of product roadmaps - SD Times<\/title>\n<meta name=\"description\" content=\"Rather than spelling out specific milestones and deadlines, consider a more fluid approach to product roadmaps.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"The pitfalls of product roadmaps - SD Times\" \/>\n<meta property=\"og:description\" content=\"Rather than spelling out specific milestones and deadlines, consider a more fluid approach to product roadmaps.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/\" \/>\n<meta property=\"og:site_name\" content=\"SD Times\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/SDTimesD2\" \/>\n<meta property=\"article:published_time\" content=\"2024-01-04T18:13:29+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2024-01-04T18:13:46+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/sdtimes.com\/wp-content\/uploads\/2024\/01\/mark-konig-ECGv8s2IPG0-unsplash.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1920\" \/>\n\t<meta property=\"og:image:height\" content=\"1920\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"John Purcell\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@sdtimes\" \/>\n<meta name=\"twitter:site\" content=\"@sdtimes\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"John Purcell\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/\"},\"author\":{\"name\":\"John Purcell\",\"@id\":\"https:\/\/sdtimes.com\/#\/schema\/person\/94b97f6f61ae655cf6cdc112df5088c3\"},\"headline\":\"The pitfalls of product roadmaps\",\"datePublished\":\"2024-01-04T18:13:29+00:00\",\"dateModified\":\"2024-01-04T18:13:46+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/\"},\"wordCount\":895,\"publisher\":{\"@id\":\"https:\/\/sdtimes.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/sdtimes.com\/wp-content\/uploads\/2024\/01\/mark-konig-ECGv8s2IPG0-unsplash.jpg\",\"keywords\":[\"DevOps\",\"SaaS\"],\"articleSection\":[\"Latest News\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/\",\"url\":\"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/\",\"name\":\"The pitfalls of product roadmaps - SD Times\",\"isPartOf\":{\"@id\":\"https:\/\/sdtimes.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/sdtimes.com\/wp-content\/uploads\/2024\/01\/mark-konig-ECGv8s2IPG0-unsplash.jpg\",\"datePublished\":\"2024-01-04T18:13:29+00:00\",\"dateModified\":\"2024-01-04T18:13:46+00:00\",\"description\":\"Rather than spelling out specific milestones and deadlines, consider a more fluid approach to product roadmaps.\",\"breadcrumb\":{\"@id\":\"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/#primaryimage\",\"url\":\"https:\/\/sdtimes.com\/wp-content\/uploads\/2024\/01\/mark-konig-ECGv8s2IPG0-unsplash.jpg\",\"contentUrl\":\"https:\/\/sdtimes.com\/wp-content\/uploads\/2024\/01\/mark-konig-ECGv8s2IPG0-unsplash.jpg\",\"width\":1920,\"height\":1920},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/sdtimes.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"The pitfalls of product roadmaps\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/sdtimes.com\/#website\",\"url\":\"https:\/\/sdtimes.com\/\",\"name\":\"SD Times\",\"description\":\"Software Development News\",\"publisher\":{\"@id\":\"https:\/\/sdtimes.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/sdtimes.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/sdtimes.com\/#organization\",\"name\":\"SD Times\",\"url\":\"https:\/\/sdtimes.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/sdtimes.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/sdtimes.com\/wp-content\/uploads\/2014\/05\/deafaultlogo.png\",\"contentUrl\":\"https:\/\/sdtimes.com\/wp-content\/uploads\/2014\/05\/deafaultlogo.png\",\"width\":225,\"height\":90,\"caption\":\"SD Times\"},\"image\":{\"@id\":\"https:\/\/sdtimes.com\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/SDTimesD2\",\"https:\/\/x.com\/sdtimes\",\"https:\/\/www.linkedin.com\/company\/sdtimes\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/sdtimes.com\/#\/schema\/person\/94b97f6f61ae655cf6cdc112df5088c3\",\"name\":\"John Purcell\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/sdtimes.com\/#\/schema\/person\/image\/f8eddf912e0981316e0097e1b8413114\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/0bd327a5b192d7a650d5c329a5aa8e2f?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/0bd327a5b192d7a650d5c329a5aa8e2f?s=96&d=mm&r=g\",\"caption\":\"John Purcell\"},\"description\":\"John Purcell is the chief product officer of DoiT International and oversees the global research and development team and the DoiT product portfolio.\",\"url\":\"https:\/\/sdtimes.com\/author\/john-purcell\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"The pitfalls of product roadmaps - SD Times","description":"Rather than spelling out specific milestones and deadlines, consider a more fluid approach to product roadmaps.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/","og_locale":"en_US","og_type":"article","og_title":"The pitfalls of product roadmaps - SD Times","og_description":"Rather than spelling out specific milestones and deadlines, consider a more fluid approach to product roadmaps.","og_url":"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/","og_site_name":"SD Times","article_publisher":"https:\/\/www.facebook.com\/SDTimesD2","article_published_time":"2024-01-04T18:13:29+00:00","article_modified_time":"2024-01-04T18:13:46+00:00","og_image":[{"width":1920,"height":1920,"url":"https:\/\/sdtimes.com\/wp-content\/uploads\/2024\/01\/mark-konig-ECGv8s2IPG0-unsplash.jpg","type":"image\/jpeg"}],"author":"John Purcell","twitter_card":"summary_large_image","twitter_creator":"@sdtimes","twitter_site":"@sdtimes","twitter_misc":{"Written by":"John Purcell","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/#article","isPartOf":{"@id":"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/"},"author":{"name":"John Purcell","@id":"https:\/\/sdtimes.com\/#\/schema\/person\/94b97f6f61ae655cf6cdc112df5088c3"},"headline":"The pitfalls of product roadmaps","datePublished":"2024-01-04T18:13:29+00:00","dateModified":"2024-01-04T18:13:46+00:00","mainEntityOfPage":{"@id":"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/"},"wordCount":895,"publisher":{"@id":"https:\/\/sdtimes.com\/#organization"},"image":{"@id":"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/#primaryimage"},"thumbnailUrl":"https:\/\/sdtimes.com\/wp-content\/uploads\/2024\/01\/mark-konig-ECGv8s2IPG0-unsplash.jpg","keywords":["DevOps","SaaS"],"articleSection":["Latest News"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/","url":"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/","name":"The pitfalls of product roadmaps - SD Times","isPartOf":{"@id":"https:\/\/sdtimes.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/#primaryimage"},"image":{"@id":"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/#primaryimage"},"thumbnailUrl":"https:\/\/sdtimes.com\/wp-content\/uploads\/2024\/01\/mark-konig-ECGv8s2IPG0-unsplash.jpg","datePublished":"2024-01-04T18:13:29+00:00","dateModified":"2024-01-04T18:13:46+00:00","description":"Rather than spelling out specific milestones and deadlines, consider a more fluid approach to product roadmaps.","breadcrumb":{"@id":"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/#primaryimage","url":"https:\/\/sdtimes.com\/wp-content\/uploads\/2024\/01\/mark-konig-ECGv8s2IPG0-unsplash.jpg","contentUrl":"https:\/\/sdtimes.com\/wp-content\/uploads\/2024\/01\/mark-konig-ECGv8s2IPG0-unsplash.jpg","width":1920,"height":1920},{"@type":"BreadcrumbList","@id":"https:\/\/sdtimes.com\/softwaredev\/the-pitfalls-of-product-roadmaps\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/sdtimes.com\/"},{"@type":"ListItem","position":2,"name":"The pitfalls of product roadmaps"}]},{"@type":"WebSite","@id":"https:\/\/sdtimes.com\/#website","url":"https:\/\/sdtimes.com\/","name":"SD Times","description":"Software Development News","publisher":{"@id":"https:\/\/sdtimes.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/sdtimes.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/sdtimes.com\/#organization","name":"SD Times","url":"https:\/\/sdtimes.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/sdtimes.com\/#\/schema\/logo\/image\/","url":"https:\/\/sdtimes.com\/wp-content\/uploads\/2014\/05\/deafaultlogo.png","contentUrl":"https:\/\/sdtimes.com\/wp-content\/uploads\/2014\/05\/deafaultlogo.png","width":225,"height":90,"caption":"SD Times"},"image":{"@id":"https:\/\/sdtimes.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/SDTimesD2","https:\/\/x.com\/sdtimes","https:\/\/www.linkedin.com\/company\/sdtimes\/"]},{"@type":"Person","@id":"https:\/\/sdtimes.com\/#\/schema\/person\/94b97f6f61ae655cf6cdc112df5088c3","name":"John Purcell","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/sdtimes.com\/#\/schema\/person\/image\/f8eddf912e0981316e0097e1b8413114","url":"https:\/\/secure.gravatar.com\/avatar\/0bd327a5b192d7a650d5c329a5aa8e2f?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/0bd327a5b192d7a650d5c329a5aa8e2f?s=96&d=mm&r=g","caption":"John Purcell"},"description":"John Purcell is the chief product officer of DoiT International and oversees the global research and development team and the DoiT product portfolio.","url":"https:\/\/sdtimes.com\/author\/john-purcell\/"}]}},"_links":{"self":[{"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/posts\/53436"}],"collection":[{"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/users\/1197"}],"replies":[{"embeddable":true,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/comments?post=53436"}],"version-history":[{"count":1,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/posts\/53436\/revisions"}],"predecessor-version":[{"id":53437,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/posts\/53436\/revisions\/53437"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/media\/53439"}],"wp:attachment":[{"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/media?parent=53436"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/categories?post=53436"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/tags?post=53436"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/sdtimes.com\/wp-json\/wp\/v2\/coauthors?post=53436"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}