<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Stefan Trieflinger on Medium]]></title>
        <description><![CDATA[Stories by Stefan Trieflinger on Medium]]></description>
        <link>https://medium.com/@stefan.trieflinger?source=rss-560508926852------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ipVSzrGlgO8RonRVcY34Pg.jpeg</url>
            <title>Stories by Stefan Trieflinger on Medium</title>
            <link>https://medium.com/@stefan.trieflinger?source=rss-560508926852------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:32:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@stefan.trieflinger/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Discovery Effort Worthiness — A Shortcut for Agile Teams]]></title>
            <link>https://medium.com/@stefan.trieflinger/the-discovery-effort-worthiness-a-shortcut-for-agile-teams-eb8c1581b76c?source=rss-560508926852------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb8c1581b76c</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Stefan Trieflinger]]></dc:creator>
            <pubDate>Fri, 14 Jun 2024 16:28:57 GMT</pubDate>
            <atom:updated>2024-06-14T16:28:57.639Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Discovery Effort Worthiness — A Shortcut for Agile Teams</h3><p>Agile practices and UX methods are nowadays well-known and often adopted to develop software and products more efficiently and effectively. One expected benefit is that software and products developed iteratively can better meet customer needs in the context of requirements management. The tricky part when talking about requirements management is that new requirements are continuously being submitted by the customer or through external influences. Often, it is also unclear what is to be developed, and this must first be discovered. This significantly complicates the planning and management of requirements and, in practice, often leads to the need for continuous and comprehensive change management. This includes optimizing changes and developments to best match the users’ needs. However, in a so-called VUCA environment, which many companies are confronted with, the sole use of UX research is not sufficient to find the best solutions for customers.</p><p>The implementation of Design Thinking can support the aforementioned situation since it aims at understanding the user’s problem first and provides an open space for discovering solutions. However, when companies adopt Design Thinking, they often struggle to implement it in their agile processes and iterations. A major constraint is the high effort for conducting comprehensive Design Thinking methods to discover and validate features and requirements. On the one hand, resources are limited; therefore, not all features can be explored with methods of Design Thinking. On the other hand, it can easily happen that the effort spent on Design Thinking exceeds the actual value delivered by the respective feature.</p><blockquote>Therefore, many companies and their product owners do not know how much resources they should spend on conducting Design Thinking methods to discover, evaluate, and validate certain requirements.</blockquote><p>In order to support product people in overcoming this problem, I have developed the so-called <strong>D</strong>iscovery-<strong>E</strong>ffort-<strong>W</strong>orthiness-Index (DEW Index) together with <a href="https://medium.com/u/c5e380a5d9e9">Dominic Lang</a>, Selina Spies, and <a href="https://medium.com/u/f9e7765a384b">Jürgen Münch</a>.</p><h3><strong>The Discovery Effort Worthiness (DEW Index)</strong></h3><p>The DEW Index consists of two dimensions that primarily affect the necessity for discovery and validation of feature requests: 1) <strong>Clarity</strong> <strong>about the user’s need</strong> (how well understood is the actual demand of the user?) and 2) <strong>Potential value</strong> (how much value does the feature deliver?).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/981/1*KL1v9ImkgMsl7PucUw84mg.png" /><figcaption>Formula to develop the DEW Index</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/421/1*upcbI9VHo7zATCS0wb0zWg.jpeg" /><figcaption>Dimension of the DEW Index</figcaption></figure><p>The different weighting is due to the fact that a low level of ambiguity and, thus, a high level of certainty about a user story particularly increases the need for Design Thinking. Furthermore, it is expected that a high level of uncertainty directly leads to a higher inaccuracy in the estimation and rating of the potential value, which means that higher unclarity also might influence the rating of the second dimension and, therefore, has more impact on the necessity of discovery and validation. Considering this weighting, the approach to calculating the DEW Index is to rate each feature request relative to each other against both dimensions on a scale from 1 to 10, where 10 represents high potential and high clarity, respectively.</p><h3>Calibration of the DEW Index</h3><p>Before I describe how you can use the DEW Index, one more important thing: To enable you to easily select the appropriate measures from the mapping table and, therefore, optimize the effort spent for discovery and validation, you must implement the DEW Index into your specific circumstances. The reason for this is that the relative dimension rating from 1 to 10 can vary between different teams. To do this calibration you can proceed as follows: <strong>1) assign corresponding Design Thinking methods to user stories from the backlog together with experts or based on experience, 2) rate this set of user stories from the backlog on the two dimensions of clarity and potential value, 3) calculate the DEW Index based on the rating, 4) map the corresponding Design Thinking methods to the results of the DEW Index calculation (i.e, create a mapping table that shows which DEW Index values are suggesting which methods and method bundles would be accurate).</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sk68COnMBnxInD7zwPCV1w.png" /><figcaption>Overview of an example bundles</figcaption></figure><h3><strong>Application of the DEW Index</strong></h3><p>In the first step, you receive a new idea or a requirement that you need to evaluate regarding the right effort for Design Thinking. Therefore, you or the team rate the idea on the dimensions of clarity and potential value. At this point, we recommend doing the rating in comparison to a reference user story to ensure that the result fits into the team’s calibrated mapping. Once you have assessed its clarity and expected potential, the next step is to calculate the “Discovery Effort Worthiness Index” (or DEW Index) with the formula developed above. After you have performed the calculation, use the calculated DEW Index to select one of the recommended Design Thinking methods or method bundles from the bundle mapping.</p><p>Please note that this mapping usually consists of method bundles instead of single methods. Executing just one single Design Thinking method is typically not sufficiently increasing clarity about the user demands or the expected value, so a bundle with a combination of methods can be more adequate. For example, such a bundle may consist of first conducting a brain dump, using the results for narrative interviews, and concluding the research with a Design Thinking workshop. These bundles can be used iteratively in several design thinking iterations. Moreover, the bundles that can be found in the mapping table are to be understood as a recommendation and orientation, not as a default. This is also why the methods and method bundles are not assigned to an exact DEW Index value and why the table should not show decimals. The DEW Index depicts the suitable effort for discovery and validation in a simplified way on a range from 1 to 10, taking the relation of the items into account. That means that the methods and method bundles are also sorted in relation to each other and to the DEW Index in this table. You can take the calculated DEW Index of a user story, investigate the mapping table, and see which method range would be appropriate and then individually pick the ones he sees most feasible or promising.</p><blockquote>Now you have a tool to systematically determine Design Thinking methods to your various user stories. Try it out. What do you think about the DEW Index? <em>Please leave a comment, and do not hesitate to contact me if you have any questions or suggestions.</em></blockquote><h3>References</h3><p>Stefan Trieflinger, Selina Spies, Dominic Lang, and Jürgen Münch (2021). Tailored Design Thinking Approach — A Shortcut for Agile Teams In <em>Software Business: 12th International Conference, ICSOB 2021, Drammen, Norway, December 2–3, 2021, Proceedings 12</em> (pp. 37–49). Springer International Publishing.</p><p>Stefan Trieflinger, Dominic Lang, Selina Spies, Jürgen Münch (2023). The Discovery Effort Worthiness Index: How much Product Discovery should you do and how can this be Integrated into Delivery?. <em>Information and software technology</em>, <em>157</em>, 107167.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb8c1581b76c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Roadmap Transformation Approach]]></title>
            <link>https://medium.com/@stefan.trieflinger/product-roadmap-transformation-approach-7b026ea4abba?source=rss-560508926852------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b026ea4abba</guid>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[product-roadmap]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Stefan Trieflinger]]></dc:creator>
            <pubDate>Mon, 19 Feb 2024 19:26:12 GMT</pubDate>
            <atom:updated>2024-02-19T19:26:12.478Z</atom:updated>
            <content:encoded><![CDATA[<p>In my last blog, I presented the DEEP Product Roadmap Self-Assessment Tool I developed with <a href="https://medium.com/u/c5e380a5d9e9">Dominic Lang</a> and <a href="https://medium.com/u/f9e7765a384b">Jürgen Münch</a>. The DEEP model enables you to assess your current product roadmapping practices in order to uncover improvement potentials. You can find the blog about the DEEP Self Assessment Tool here: <a href="https://bit.ly/deeptool">bit.ly/deeptoo</a>l</p><p>However, the DEEP model does not provide a systematic process on how you can approach the improvement of your roadmapping practices to achieve a higher overall maturity level in the DEEP model. Therefore, I will now present the product roadmap transformation approach that I also developed with <a href="https://medium.com/u/c5e380a5d9e9">Dominic Lang</a> and <a href="https://medium.com/u/f9e7765a384b">Jürgen Münch</a>. This approach will help you conduct a successful product roadmap transformation and achieve a higher level in the DEEP model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sn_wr8TiYLQb8Hyl0oKE0A.jpeg" /><figcaption>Product Roadmap Transformation Approach</figcaption></figure><p>Overall, the product roadmap transformation approach consists of the phases 1) Analyse, 2) Set Goals and Choose Measures, 3) Execute, and 4) Operate. In the following, I will present the purpose of each of these phases — Let’s go :- )</p><p><strong>Phase Analyse:</strong> The phase “Analyse” focuses on answering the question of which dimension of the DEEP model promises the most benefit when improved. Please note that the lowest-rated dimension does not necessarily have to be the highest priority for improvement. The reason for this is that the decision also depends on the company’s goals, the position of the person who plans and implements the methods (e.g., member of the management, head of product management, product owner), and the product team’s ability. Identifying the dimension that offers the most benefit for improvement is crucial for efficiently conducting the product roadmap transformation. This sounds very simple, but it is not easy to do :-) I have, therefore developed the following guidelines to help you select the most promising dimension for improvement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/1*YWEJPAIgdHzEcZReDOaJtQ.jpeg" /><figcaption>Procedure for identifying the most promising dimension for improvements in the DEEP model</figcaption></figure><p>In the case that you have achieved an overall maturity level of three, four, or five in the DEEP model, I recommend selecting one of the following dimensions: 1) roadmap items, 2) roadmap detailing, 3) product discovery, 4) confidence, 5) ownership, 6) responsibility, 7) extent of alignment or 8) prioritization. In contrast, if you have reached an overall maturity level of one or two in the DEEP model, I suggest disregarding the two dimensions of “prioritization” and “extent of alignment.” The reason why the dimension “prioritization” was excluded is that an essential success factor for an effective and efficient prioritization process in a dynamic and uncertain market environment is to understand the value that should be delivered to the customer and the business. Suppose a user of the DEEP model selects a stage that considers the factor customer value (independent of the dimension). In that case, this leads to an overall maturity level of three or higher. Consequently, a company at level one or two does not include the customer value (which is crucial for the prioritization) in the roadmapping process; thus, improving the dimension prioritization within these levels is not advisable. The reason for excluding the dimension “extent of alignment” is that the product roadmap should be in a sufficiently mature state so that the stakeholders are able to align their activities with the roadmap. Therefore, the dimension alignment should not be considered until the product roadmap has reached a higher level of maturity. Based on this pre-selection, I suggest to apply the following criteria for the final determination of the dimension to be improved:</p><p><strong>Roadmap items and detailing of the roadmap:</strong> I recommend improving the dimension “roadmap items” before improving the dimension “roadmap detailing.” The reason for this is that using roadmap items of different granularity (such as products, themes, outcomes, and epics) is likely to lead to a correlation between the timeline and the level of detailing of the roadmap items. It should be noted that ideally, the short-term planning consists only of roadmap items with high confidence.</p><p><strong>Product discovery and confidence:</strong> I recommend considering improving the dimension “product discovery” before improving the dimension “confidence.” “Product discovery” is the ability of a company to identify and validate products or features before implementation, such as through customer interviews or rapid prototyping. The conduction of product discovery activities aims to reduce the uncertainty to a level that allows starting to build a solution that provides value for the customer and the business. This includes high confidence that the planned solutions will greatly impact the customer and business goals. Therefore, conducting product discovery activities is likely to contribute to achieving confidence.</p><p><strong>Ownership and responsibility:</strong> The dimensions “ownership” and “responsibility” should be considered together. The dimension “ownership” describes who owns the roadmap (i.e., signs off and approves the roadmap), while the dimension “responsibility” answers the question of “who is responsible for defining the roadmap items and conducting the roadmapping process.” In more detail, I recommend considering the following aspects:</p><p><strong>Role and authority of the “change agents”:</strong> The role and authority of those responsible for transforming the product roadmapping practice in an organization must be considered. The extent to which improvement is promising and the extent to which improvement can be influenced must be weighed here.</p><p><strong>Company context and culture:</strong> The corporate context and culture must also be taken into account when considering which dimension to select. Here, the impact of an improvement must be weighed against the associated effort.</p><blockquote>So far, so good. We have now analyzed our results of the DEEP assessment and selected the most promising dimension for improvement. Now, the question arises: Which measures are suitable for achieving an improvement in our selected dimension? Therefore, I provide the phase “Set Goals and Choose Measures” as follows:</blockquote><p><strong>Phase Set Goals and Choose Measures:</strong> The phase “Set Goals and Choose Measures” includes the definition of a clear improvement objective and corresponding measures that contribute to achieving the defined objective. An example of an objective could be to improve the dimension “extent of alignment” from level 2 to level 4 by establishing a process that fosters alignment. Conceivable measures in this context could be 1) the development of a shared product vision by conducting workshops with various stakeholders, 2) the review of this product vision by conducting customer interviews, and 3) the consolidation of the content of all existing and loosely coupled product roadmaps based on the previously created product vision. However, the question arises as to what measures we should take to achieve the defined goal? Therefore, I developed two mapping tables, which build on each other. Below, you will find the first map, called <strong>Goal Opportunity Map.</strong></p><p>The y-axis of the Goal-Opportunity Map shows the dimension of the DEEP model. Improving a dimension of the DEEP model can be achieved by creating artifacts (and the capabilities built through the artifact development) that are essential for operating in a volatile market environment but are still missing in the current product roadmapping process. The Goal-Opportunity Map looks as follows:</p><figure><img alt="Goal-Opportunity Map" src="https://cdn-images-1.medium.com/max/1024/1*JDnZScFENyF8xlS34xUQzw.jpeg" /><figcaption>Goal-Opportunity Map</figcaption></figure><p><strong>Application of the Goal-Opportunity Map:</strong> You can apply the Goal Opportunity Map by entering the identified dimension to be improved in order to obtain an artifact to achieve that improvement. This is marked by the crosses that connect the dimensions and the artifact. For example, the dimension “Roadmap Items” can be improved by developing the artifact’s product vision, outcomes, solution ideas, and validated learnings. Please note that I recommend developing only one artifact per iteration cycle of the product roadmap transformation process.</p><p>However, the application of the Goal-Opportunity Map does not provide the answer to the question of what methods must be performed in order to develop the required artifacts. Therefore, I developed a second map, called <strong>Goal-Activity Map</strong>, that looks as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jh8SH3f8FeiyiuPBdkb3Hg.png" /><figcaption>Goal-Activity Map</figcaption></figure><p><strong>Application of the Goal-Activity Map:</strong> To obtain a suitable measure, enter the artifact you obtained by applying the Goal-Opportunity Map on the X-axis (product vision, outcomes, solution ideas, or validated learnings). As with the Goal-Opportunity Map, the connection is also indicated by the crosses between the artifacts and the measures. For example, solution ideas can be created by conducting the methods of “Impact Mapping” or developing an “Opportunity Solution Tree”.</p><blockquote>Now that we have selected our methods, we can start implementing them. This takes place in the phase “Execute” of the product roadmap transformation process.</blockquote><p><strong>Execute:</strong> The phase “Execute” aims to implement the measures identified in the previous phase and analyse their impact on the roadmapping process, including the following steps: 1) plan (the preparation for executing the identified measures), 2) implementation (conducting the identified measures), 3) review (analysing of the impact of the conducted measures), and 4) retrospective (reflecting the approach for conducting the measures, for instance, workshops or interviews). Please note that the substeps review and retrospective are critical in order to make statements about whether the methods conducted have led to an improvement and whether they have been applied efficiently.</p><p><strong>What to do if the phases review or retrospective fail?</strong></p><p>I am often asked how to proceed if the case review or retrospective fail. The phase review fails if it reveals that the methods implemented did not positively impact the roadmapping process. For example, merging several loosely coupled roadmaps has not led to a usable central roadmap. It may also happen that the phase retrospective shows that the selected method was not carried out optimally (e.g., not enough various perspectives were considered in a workshop). If one of these events occurs during your product roadmap transformation, I recommend returning to the phase “Analyse” and iterate from there. The reason for this suggestion is that taking into consideration the learnings gained during the conduction of the process and changes in the frame conditions that have occurred during the time might lead to different decisions regarding which dimension should be in focus and which measures will most likely support them.</p><p><strong>Operate: </strong>Last but not least, the phase “Operate” consists of additional tests in order to ensure that the measures are conducted in accordance with the needs and requirements of the company.</p><blockquote>Now, you have all the information you need to prepare your roadmap for operating in a volatile market environment. Let’s do it;- ) Please leave a comment, and do not hesitate to contact me if you have any questions or suggestions.</blockquote><h3>References</h3><p>Stefan Trieflinger, Jürgen Münch, Stefan Wagner, Dominic Lang, Bastian Roling (2021). A Transformation Model for Excelling in Product Roadmapping in Dynamic and Uncertain Market Environments. In <em>Product-Focused Software Process Improvement: 22nd International Conference, PROFES 2021, Turin, Italy, November 26, 2021, Proceedings 22</em> (pp. 136–151). Springer International Publishing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b026ea4abba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DEEP: The Product Roadmap Self- Assessment Tool]]></title>
            <link>https://medium.com/@stefan.trieflinger/deep-the-product-roadmap-self-assessment-tool-e0bf1430d50d?source=rss-560508926852------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0bf1430d50d</guid>
            <category><![CDATA[product-roadmap]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Stefan Trieflinger]]></dc:creator>
            <pubDate>Wed, 17 Jan 2024 17:06:37 GMT</pubDate>
            <atom:updated>2024-01-17T17:06:37.053Z</atom:updated>
            <content:encoded><![CDATA[<h3>DEEP: The Product Roadmap Self-Assessment Tool</h3><p>Are you frustrated with using product roadmapping and interested in improving your product roadmapping practices? The DEEP Self - Assessment Tool enables you to assess your current product roadmapping capabilities in order to identify improvement potentials and how to switch to an outcome-driven approach. together with <a href="https://medium.com/u/c5e380a5d9e9">Dominic Lang</a> and <a href="https://medium.com/u/f9e7765a384b">Jürgen Münch</a>, I developed the DEEP tool in my dissertation. Visit <a href="https://bit.ly/problemsroadmaps">https://bit.ly/problemsroadmaps</a> to get insights into the problems with feature-driven product roadmaps and why we need a tool like the DEEP Self - Assessment Tool. DEEP stands for <strong>D</strong>eliver value”, “<strong>E</strong>mbrace learning”, “<strong>E</strong>volve with change”, and “<strong>P</strong>rioritize ruthlessly.</p><h3>THE DEEP Self-Assessment Tool</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*35z2Osw4KZqiq5BK0kQztA.png" /><figcaption>DEEP Product Roadmap Self-Assessment Tool</figcaption></figure><h3>Structure of the DEEP</h3><p>The DEEP Self-Assessment Tool consists of nine dimensions, each presenting a relevant aspect for product roadmapping in a dynamic and uncertain market environment. Examples of dimensions are which items are used on the product roadmap (roadmap items), how often and in what manner the roadmap is adjusted (reliability), or in what manner product discovery activities are conducted (product discovery). During the development of the DEEP Self-Assessment Tool, we observed that the nine dimensions and their corresponding stages differ in their importance regarding successful product roadmapping. This means that being mature in the dimension roadmap items or roadmap detailing was more critical than achieving excellence in the dimensions ownership or extent of alignment. Similarly, the stages also contribute differently to reaching maturity. For example, moving from stage 1 to stage 2 can contribute less to overall maturity than moving from stage 4 to stage 5 since the gap between stage 4 and stage 5 could be bigger. This means that developing skills, processes, or artifacts requires more effort. In order to include these observations in the DEEP Self-Assessment Tool and provide a valuable self-assessment tool, we decided to integrate a scoring model. The purpose of such a scoring is that practices are comparable with respect to their maturity.</p><h3>Application and Levels of the DEEP</h3><p>You can perform a self-assessment by answering all questions and, selecting the applicable stages for each dimension, and summing up the corresponding score. The minimum score that can be reached is nine points, the maximum is 100. As a result, the user obtains the maturity of each dimension as well as an overall maturity level as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/467/1*ZdRIObIkdr2V06-mI2cykA.png" /><figcaption>Levels of the DEEP</figcaption></figure><p>Below, you will find the meaning of a higher level after summing up the points of the selected nine dimensions. The higher the level, the more orientation and confidence the product roadmap provides and takes into account the delivery of value to the customer and the business. As the picture below shows, the increase in levels is not linear, i.e, you don’t have to reach level 2 to get to level 3. That means it is possible to move from level 2 to level 4. The same applies to the stages within a dimension. For example, it is possible for a company to move from stage 2 to stage 5 within a dimension.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UyExQCoDepNpGCSXf0SxcA.png" /><figcaption>Levels of the DEEP Model</figcaption></figure><h3><strong>What benefits will you earn by using the DEEP?</strong></h3><p>The DEEP Self-Assessment Tool was tested in various case studies. These studies showed that the DEEP helps to gain the following benefits:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*35USGnFcZ3qZ5T-Woy8gBw.png" /></figure><h3>What´s coming next?</h3><p>The DEEP enables you to self-assess your current product roadmapping practices. However, the DEEP does not contain any information on how to achieve a higher level. This includes analyzing which dimension should be tackled for transformation and what methods or techniques should be conducted to improve the corresponding dimension. I will address these issues in my next blog.</p><h3>References</h3><p>Stefan Trieflinger, Jürgen Münch and Dominic Lang. “Transformation Towards a Product-Led Company: Case Studies from Industry.” <em>Proceedings of the 5th International Workshop on Software-intensive Business: Towards Sustainable Software Business</em>. 2022.</p><p>Stefan Trieflinger, Jürgen Münch and Dominic Lang. “DEEP: The Product Roadmap Maturity Model: A Method for Assessing the Product Roadmapping Capabilities of Organizations.” <em>Proceedings of the 2nd ACM SIGSOFT International Workshop on Software-Intensive Business: Start-ups, Platforms, and Ecosystems</em>. 2019.</p><p>Stefan Trieflinger, Jürgen Münch and Dominic Lang. “The Product Roadmap Maturity Model DEEP: Validation of a Method for Assessing the Product Roadmap Capabilities of Organizations.” <em>Software Business: 10th International Conference, ICSOB 2019, Jyväskylä, Finland, November 18–20, 2019, Proceedings 10</em>. Springer International Publishing, 2019.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0bf1430d50d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Feature-Driven Product Roadmaps Fail in the Digital World]]></title>
            <link>https://medium.com/@stefan.trieflinger/why-feature-driven-product-roadmaps-fail-in-the-digital-world-61ec3e37c2e2?source=rss-560508926852------2</link>
            <guid isPermaLink="false">https://medium.com/p/61ec3e37c2e2</guid>
            <category><![CDATA[product-roadmap]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Stefan Trieflinger]]></dc:creator>
            <pubDate>Fri, 12 Jan 2024 14:24:55 GMT</pubDate>
            <atom:updated>2024-01-12T14:24:55.157Z</atom:updated>
            <content:encoded><![CDATA[<p>You are asking a big software company for a specific feature, and they tell you they have it on the roadmap for next year. What is your reaction? Honestly, most times, your first reaction is to think that this means you will never receive the feature, and you will start to build a workaround. At least, from my experience, that usually holds true, but why is that the case? A short introduction to the pitfalls of roadmapping.</p><p>Over the years, I have worked for several companies from different industry domains with various digital products. In this context, one thing, in particular, caught my eye:<em> </em>It seems that companies operating in the digital world are increasingly struggling to create reliable product roadmaps. This opens the question of the reasons for the failure of product roadmapping in volatile environments and how companies can switch to a new approach. I, therefore, decided to address this problem in my dissertation and developed various tools with <a href="https://medium.com/u/c5e380a5d9e9">Dominic Lang</a> and <a href="https://medium.com/u/f9e7765a384b">Jürgen Münch</a> to tackle it.</p><p>First of all, before making any conclusions or suggestions, we studied which product roadmapping approach software-intensive companies are currently using. To find this out, we conducted an interview study with several German companies and an analysis of the grey literature. The results show that the most common approach is a traditional format with a fixed time-based chart containing detailed products or features over a long time horizon. This roadmap format is usually referred to as feature-driven product roadmaps. The purpose of such roadmaps is to inform stakeholders at which point in time a product is ready for market launch. Below, you will find an example of such a feature-driven product roadmap.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xjakugtjbRW0BZxnEAi6Wg.png" /><figcaption>Feature-Driven Product Roadmap</figcaption></figure><p>Feature-driven product roadmaps aim to inform stakeholders at which point in time a product is ready for market launch. However, in a dynamic market environment with associated uncertainties, it is almost impossible to predict which products, features, or services will satisfy customers’ needs, especially in the mid and long term. Therefore, feature-driven product roadmaps work well in market environments that are predictable, stable, and reliable. Consequently, several problems arise when using feature-driven product roadmaps in a dynamic and uncertain market environment. I will discuss these problems in detail below.</p><h3>Common Problems with Product Roadmaps</h3><p><strong>Feature-Driven Mindset: </strong>As mentioned, product roadmaps often consist of features, including exact delivery dates, on a timeline over a long-time horizon, e.g., more than one year in advance. However, such detailed feature planning upfront does not work in a dynamic and uncertain market environment. Some of the reasons for this are the emergence of new technologies, rapidly changing customer behavior, and less predictability of markets and demands. Therefore, features estimated beyond the next release tend to change as new risks or dependencies are uncovered. Therefore, feature-driven product roadmaps are usually often subject to frequent adjustments. These adjustments are associated with a high effort since all the features that have been worked out in detail, including their associated responsibilities, must be rescheduled. Moreover, frequent ad-hoc adjustments decrease the reliability of the roadmap, and nobody considers the roadmap as a trusted planning tool. Another problem with feature-driven product roadmaps is that when customers or stakeholders see a feature to be delivered on a specific date in the product roadmap, they will interpret this as commitment, and expectations are raised. However, the uncertainty that comes with developing products in a dynamic market environment makes it very likely that features will not be delivered as planned and communicated. This applies particularly to features planned for the mid and long-term in the product roadmap and leads to the circumstance that customers or stakeholders perceive the non-delivery as a broken promise and are disappointed and dissatisfied. Last but not least, feature-driven roadmaps consider features, but they do not include the value to be delivered to the customer. This leads to the problem that the features planned might not contribute to the solution of customer problems and are therefore not bought or used by customers.</p><p><strong>Too many details in the product roadmap:</strong> Another problem is the inclusion of too many details in the product roadmap. This means, for example, very detailed descriptions of user stories, requirements, or resources. The main reason for including too many details in the product roadmap is that product managers feel obliged to include the wishes of every stakeholder in the product roadmap. However, including too many details blurs recognition of the strategy to achieve a company’s product vision. This causes the product roadmap to be understood by all stakeholders, leading to misunderstanding and a decrease in the execution of the product strategy. In addition, if the underlying reason for conducting the planned product development in the roadmap is buried under details, it will be difficult to generate enthusiasm and excitement among the employees.</p><p><strong>Individual opinions decide which items will be included in the product roadmap:</strong> In many companies’ management or experts (e.g., product managers, product owners, etc.) decide which items to place on the product roadmap. The problem with this approach is that only individual opinions determine the product roadmap’s content, but the customers’ perspectives are not included. This approach can lead to the development of products based on false assumptions and use cases. In the worst case, this can lead to the team members feeling unappreciated and losing their commitment to the company.</p><p><strong>Not reviewing and updating the roadmap: </strong>Furthermore, several authors point out that creating the product roadmap is seen as a one-time activity rather than a continuous process. This means that companies often create and work on their product roadmap at the beginning of the year and use it as a fixed document with no further changes. However, the problem is that priorities, resources, budget, and external factors such as competitors or major customers can change at any time, affecting the content of the product roadmap. Therefore, it is crucial to continuously review and update the product roadmap at a short time interval (e.g., every week or as a cadence of stakeholder meetings takes place). Otherwise, the company forgoes the opportunity to incorporate findings into the product development process after the product roadmap is created.</p><p><strong>Lack of an enterprise-wide known product vision: </strong>Many companies do not have a product vision or have a product vision but never use it. The danger of not having or communicating a product vision is that the teams involved in product development are unclear about the overall goal of developing the planned products in the product roadmap. First, this situation makes it difficult for the teams to identify and prioritize measures contributing to product success. Consequently, the teams will be unable to identify which measure contributes most to achieving the product vision and will struggle to prioritize various measures.</p><p><strong>Identification and implementation of customer feedback channels: </strong>Another problem is that companies often struggle to identify and implement data collection channels for customer feedback. One reason for this is that product managers often stay in their offices and do not leave the building to talk to (potential) customers. Another reason is that in the race to meet deadlines, product teams do not have enough time and resources to devote to identifying customer feedback channels. The risk of not involving customer feedback in the product roadmapping process is that the development of the product roadmap will be based on assumptions without validation. As a result, products that do not bring about the intended change in customer behavior may be included in the product roadmap and developed. Consequently, these products will not succeed on the market.</p><p><strong>Unrealistic Expectations:</strong> Another pitfall is to make unrealistic and arbitrary expectations on the roadmap. Setting unrealistic expectations can originate from various sources, for example, from management to the operational level but also from product management to software development. Such behavior will generally damage the relationship between the expectation setter and recipient. A typical example of the setting of unrealistic expectations is the specification of non-realistic release dates.</p><p><strong>Lack of criteria for the conduction of the product roadmap prioritization process: </strong>Moreover,<strong> </strong>product managers often prioritize their roadmap items based on individual opinions. This includes views of the management or various members of the product team as well as customer requests. However, this includes the pitfall that subjective opinions are often influenced by personal bias and often present only a single point of view. Therefore, there is a low probability that these opinions reflect the most important current customer problems and are, consequently, inappropriate for application in the prioritization process of the product roadmap.</p><p><strong>Creation of a single product roadmap for all stakeholders:</strong> A common mistake is to create a single product roadmap. The problem with this approach is that a product roadmap is an artifact that needs to be reviewed by many stakeholders, such as the CEO, CPO, marketing, sales engineering, and customers. This means that the information that is focused on and emphasized should be tailored to the stakeholder to whom the product roadmap is presented. Therefore, creating a single roadmap will not be sufficient for informing and collecting feedback from these stakeholders.</p><h3><strong>Let’s talk about solutions to these problems</strong></h3><p>Do these problems sound familiar to you? Over the next few weeks, I will present our holistic approach that enables you to transform your product roadmap to the requirements of a dynamic and uncertain market environment. Let´s stay in touch — Follow me and leave a comment.</p><h3><strong>What´s coming next?</strong></h3><p>In the next blog, I will present a tool that enables you to assess your current product roadmapping capabilities. The results of this assessment help you to identify improvement potentials and pave the way to switch to an outcome-driven product roadmapping approach.</p><h3><strong>References</strong></h3><p>Stefan Trieflinger, Jürgen Münch and Dominic Lang. “Why Traditional product roadmaps fail in dynamic markets: global insights.” <em>International Conference on Product-Focused Software Process Improvement</em>. Cham: Springer International Publishing, 2022.</p><p>Stefan Trieflinger, Jürgen Münch and Dominic Lang. “What’s Hot in Product Roadmapping? Key Practices and Success Factors.” <em>Product-Focused Software Process Improvement: 20th International Conference, PROFES 2019, Barcelona, Spain, November 27–29, 2019, Proceedings 20</em>. Springer International Publishing, 2019.</p><p>Stefan Trieflinger, Jürgen Münch and Dominic Lang.“Why Feature-Based Roadmaps Fail in Rapidly Changing Markets: A Qualitative Survey.” <em>Software-intensive business: start-ups, ecosystems and platforms: proceedings of the International Workshop on Software-intensive Business: Start-ups, Ecosystems and Platforms (SiBW 2018): Espoo, Finland, December 3, 2018.-(CEUR workshop proceedings; 2305)</em>. RWTH Aachen, 2018.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61ec3e37c2e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>