PDF Summary:Product Roadmaps Relaunched, by C. Todd Lombardo, Bruce McCarthy, Evan Ryan, and Michael Connors

As today's products accelerate in speed and complexity, having an effective product roadmap is essential. In Product Roadmaps Relaunched, authors C. Todd Lombardo, Bruce McCarthy, Evan Ryan, and Michael Connors provide a guide for crafting strategic product roadmaps focused on solving customer problems rather than listing features.

The authors emphasize that effective roadmaps communicate an overarching vision, link initiatives to measurable business objectives, and prioritize themes based on user needs. Their approach advocates flexible timelines, collaboration across stakeholders, and continuously validating assumptions to align products with evolving market conditions.

(continued)...

• Develop a feedback loop with stakeholders by setting up regular check-ins via a shared online document or platform where they can list their needs and concerns as they arise. This could be a shared Google Doc or a dedicated Slack channel. For instance, if you're working on a community garden project, stakeholders can note their needs for certain tools or seeds, and others can respond with updates or solutions.

Timeframes that are expansive and permit adaptability and the acquisition of knowledge.

The authors argue that the traditional method of incorporating exact timelines and dates for feature completion in product roadmaps is generally impractical. It is crucial for your product's development strategy to be adaptable, incorporating both expected modifications identified through testing, research, and feedback, as well as unexpected changes due to market forces, regulatory updates, competitive influences, and internal company reorganizations. You may discover that tackling a particular topic requires resources or partnerships that are presently out of reach. Or worse yet, maybe you learn the customer need you intended to solve was not a real problem. Establishing precise dates often results in disappointment in these circumstances.

Opt for general time periods instead of specifying precise dates or months to communicate when your organization intends to meet customer needs and realize its goals. Roadmap items are typically arranged based on their priority, delineating objectives that are immediate, slated for the near future, or planned for the distant future, and they may be ordered chronologically by quarters or annually. Companies that follow annual product cycles should devise plans that span a year, yet remain flexible to accommodate changes in timelines. Exclude details like days, months, weeks, or seasons. These specifics might appear on project plans or release plans, but they do not belong on a strategic roadmap.

Context

• The business environment is constantly changing due to factors like technological advancements, economic shifts, and evolving consumer preferences, making rigid timelines difficult to adhere to.
• Engaging with customers and gathering feedback can reveal insights that necessitate changes in product features or priorities, ensuring the product remains aligned with user needs.
• Collaborations with other organizations might be necessary to access specialized expertise, technology, or market channels, but these partnerships can be difficult to establish due to differing priorities or strategic goals.
• Software and product development often encounter unforeseen technical challenges that can delay progress, making precise timelines unreliable.
• Using general time periods allows teams to adjust plans as new information becomes available, fostering a more responsive and adaptive approach to product development.
• Prioritization involves evaluating features or tasks based on factors like customer impact, business value, and resource availability. This helps ensure that the most critical and beneficial items are addressed first.
• Flexibility in annual planning helps mitigate risks associated with unforeseen challenges, such as supply chain disruptions or sudden shifts in consumer behavior, by allowing for quick course corrections.
• Strategic roadmaps are high-level tools meant to guide long-term vision and priorities rather than manage day-to-day operations. Including specific dates can shift focus from strategic goals to tactical execution.

Changes to the roadmap may be implemented as necessary.

The authors recommend that each product roadmap should clearly express its purpose and strategic orientation, instead of being a rigid contract. The disclaimer protects you from accusations that you have broken promises, it protects your customer by reiterating that change is possible, and it provides context for any dates or features that may appear on the roadmap.

For guidance on the particulars of a roadmap disclaimer, seek assistance from your finance or legal team, as these aspects are typically dictated by the policies of your organization. It is usually sufficient to acknowledge that the roadmap is subject to change and to indicate the anticipated release timing.

Other Perspectives

• Implementing changes as necessary could result in scope creep, where the product's features and goals continuously expand or shift, potentially leading to delays and budget overruns.
• Some customers might ignore disclaimers, especially if they are not prominently displayed or are buried in fine print, which could lead to misunderstandings and disputes.
• Relying solely on finance or legal teams for the roadmap disclaimer could result in language that is overly cautious or complex, which might confuse customers or stakeholders rather than clarifying the roadmap's flexibility.
• This approach could potentially undermine stakeholder confidence, as it may be perceived that the team is not confident in its ability to deliver on its plans.
• Focusing on release timing may divert attention from the importance of feature quality and readiness.

Acquiring knowledge of the strategic direction.

Prior to initiating the development of a product roadmap, it is important to consider several essential preparatory steps outlined by the authors. To make informed strategic choices, one must thoroughly understand the current development stage of the product. In a mature market, managing a product demands a distinct strategy and generally necessitates a more detailed roadmap compared to a Minimum Viable Product (MVP) entering a nascent or undeveloped market. Second, it is essential to perform an in-depth examination of the market conditions in which your product or service will be introduced, which includes understanding the array of competitors and making a precise assessment of its prospects for success. To ensure you're tackling genuine customer challenges, gathering feedback and insights directly from them is crucial. The elements in question are instrumental in devising a strategic approach that guides you to the successful creation of a novel product.

Recognizing the current phase of the product's lifecycle.

Lombardo, McCarthy, Ryan, and Connors outline five separate stages through which a product progresses during its evolution.

1. Introducing a fresh product.

2. Growth

3. Investigating fresh avenues within the realm of product creation.

4. Harvesting

5. The product ultimately reaches the end of its lifecycle.

The following discussion will explore how different phases of product creation demand unique product management strategies, which necessitate tailored methods for developing product roadmaps.

Adjusting the product roadmap's schedule to correspond with the present phase of the product's evolution.

A product in its early stages should be steered by a concise roadmap, covering a short period of weeks or months, whereas the approach for a product that is broadening its scope or improving existing functionalities could stretch over many quarters or even across multiple years. For instance, a business that is outlining its core capabilities will advance more swiftly than those already established with a loyal clientele and concentrate on refining and improving their offerings.

A product well-established in a stable market necessitates a strategy focused on the long-term, in contrast to a product newly introduced to a market characterized by swift changes. Businesses within the sector that produces mobile devices typically unveil new offerings every nine to twelve months, basing their strategies for product development on this rhythm, whereas companies that create semiconductors for these gadgets plan their product releases over a multi-year timeline.

Context

• A short-term roadmap facilitates clearer communication with stakeholders by setting realistic expectations and demonstrating progress through quick wins and iterative improvements.
• Startups or new product lines typically have fewer constraints and can pivot more easily, allowing them to innovate and implement changes faster than established companies with rigid structures.
• Stable markets may have well-defined regulatory frameworks, reducing uncertainty and enabling companies to focus on long-term compliance and strategic goals.
• Companies often need to allocate resources flexibly, focusing on immediate priorities and opportunities rather than long-term commitments.
• The pace of technological innovation in mobile devices is fast, with improvements in processors, cameras, and software occurring regularly. This necessitates frequent product updates to incorporate new technologies.
• Semiconductor development involves intricate design and testing processes, requiring significant time to ensure functionality and reliability. This complexity necessitates longer planning cycles.

Exploring the wider business environments and marketplaces.

The authors stress the significance of understanding the competitive environment that envelops your business in the process of developing a product roadmap. They warn that without this essential understanding, decisions and product development might rest on an unstable foundation of biased assumptions. To avoid this frequent error, it's wise to assess your product's market framework before starting discussions with your development team and key stakeholders to ensure a shared understanding of the market dynamics.

Exploring the domain of obstacles, future opportunities, and the array of competing market forces.

In the planning phase, it's crucial to conduct an in-depth examination of the problems your product intends to solve and to consider a variety of strategies that could be utilized in overcoming these issues. Which chances for achievement are most pertinent? What alternative solutions exist? Through this analysis, you can identify the key aspects to highlight for your product. Conduct a comprehensive analysis of the companies you're competing against. A comprehensive evaluation of the market competition's product range and abilities, as well as their deficiencies, may reveal areas where your own product excels. What unmet needs do customers have that competitors are not paying attention to, or are there aspects of customer dissatisfaction that remain inadequately addressed? To distinguish your product, pinpoint the shortcomings in competitor offerings and develop approaches that capitalize on those gaps.

Other Perspectives

• An in-depth examination can be resource-intensive, potentially diverting valuable time and funds that could be used for development or marketing efforts.
• Focusing on too many strategies might dilute resources and efforts, which could be more effectively concentrated on a few well-chosen paths.
• Highlighting key aspects of a product might inadvertently narrow the focus too much, causing potential customers to overlook other valuable features or benefits that are not emphasized.
• Overemphasis on competitors can inadvertently lead to imitation rather than differentiation. Companies might subconsciously adopt industry norms and standards, which can stifle originality.
• It may lead to an adversarial mindset that overlooks opportunities for partnerships, collaborations, or learning from competitors.
• Addressing every point of customer dissatisfaction could lead to feature creep, making the product overly complex and less user-friendly for the majority of users.
• This strategy might not account for brand loyalty or other intangible factors that contribute to a competitor's success despite apparent shortcomings in their offerings.
• Competitors might quickly respond and fill those gaps, which could diminish the unique selling proposition of the new product.

Gathering customer insights through interviews, analyzing their interactions, and seeking their perspectives.

Lombardo, McCarthy, Ryan, and Connors emphasize the importance of integrating suggestions from those who interact with your product into the planning of your product's future direction. The authors stress the significance of guiding the collaborative endeavors of your group to precisely recognize and convey the challenges and requirements of customers. This requires that you actively seek out and engage with your customers to validate your assumptions and ensure you are actually solving real problems for them.

Translating customer needs into key patterns and associated secondary motifs.

Upon gathering insights from your customers, you may begin integrating these valuable perspectives into the practical components of your product development strategy. The writers stress the significance of using central motifs to clearly organize and respond to user requirements. A potential motif for a customer's experience could be "Ensuring uniformity in serving our customers." To underscore the fundamental principles, they interlace narratives centered on the roles or actual experiences of individuals who use the product. A city commuter, who is determined to be on time for a meeting, needs a quick evaluation of travel time to choose the most dependable path that ensures punctuality.

User needs are given precedence through themes, while the company's goals are addressed by the objectives mentioned earlier. To tackle differing perspectives, it's crucial to focus on the objective of avoiding unanticipated customer engagements and to emphasize a narrative that prioritizes users, while aiming to amplify the enduring value for every client.

Employing narratives centered on the user and their related tasks to improve the creation of themes.

The authors highlight that themes are centered on anticipated outcomes rather than specific deliverables. A theme describes the customer's need or problem, while a specific approach outlines the strategy intended to address or satisfy that need or problem.

To ensure clarity in the reasoning and to prevent the development of features aimed only at expansion without addressing fundamental problems, the authors recommend framing each theme as a story centered on a specific customer and their unique requirement. Two common methods for structuring themes include developing stories that illustrate user experiences based on Agile software development techniques and creating narratives that correspond with the concept of job stories derived from the jobs-to-be-done framework.

Practical Tips

• When planning personal projects, ask friends or family for feedback on the outcomes you're aiming for, not the steps you plan to take. If you're organizing a home renovation, instead of asking for opinions on the color of the paint or the type of flooring, ask how they envision the space feeling or functioning when the renovation is complete. This can help you stay focused on the end result and may provide insights that change your approach.
• Observe a public space, like a coffee shop or a park, and take note of the different activities people engage in. Try to infer the underlying needs or problems they are addressing through these activities. This can enhance your ability to spot themes in customer behavior in a real-world setting. For example, you might notice someone using a portable charger, indicating a need for mobile charging solutions due to battery life limitations in current devices.
• Volunteer to solve problems for friends or family members in areas you're not familiar with, using only the resources you have at hand. This exercise will train you to think creatively and resourcefully, skills you can then apply to customer needs in any context.
• Role-play a day in the life of your user with a friend or colleague. Take turns acting out scenarios where the user interacts with the software, while the other person observes and takes notes. This role-playing exercise can uncover insights into user behavior and preferences that might not be evident from traditional user stories or use cases, providing valuable input for Agile development cycles.
• Craft your resume as a series of job stories to showcase how you've tackled specific challenges. Instead of listing responsibilities, frame your experiences as situations where you identified a need, took action, and achieved a result. For example, instead of saying "Managed a team of salespeople," you could say, "When the sales team needed to increase conversion rates, I implemented a new training program that resulted in a 20% increase in sales."

Determining the strategic direction for the roadmap and reaching a consensus on its priorities.

After aligning your product's purpose with the broader vision and objectives of your company, and identifying customer needs that emerge as general themes, you might be under the impression that the direction of your product is well-defined. Delay the start of coding for now! Prior to commencing the tasks at hand, it's crucial to organize your themes in an order that garners consensus on their importance among all stakeholders.

Determining priorities is guided by setting explicit objectives and essential results.

Do you recall the discussion regarding objectives, essential outcomes, and anticipated results? Let's put those concepts into action! By linking every theme of your product to distinct company goals, you can concentrate your efforts on addressing issues that will have the most significant benefit for your organization.

Ensuring that initiatives and broader goals fully align with the organization's objectives.

The authors stress the necessity of aligning goals with the broader mission of the company when setting priorities to prevent the risk of creating features that are not in harmony with the organization's requirements. This prioritization might entail evaluating and then reducing focus on specific customer segments that are not profitable, or diminishing activities that are inconsistent with your main objectives, like expanding into new markets or improving engagement with certain customer demographics. To ensure that your company's objectives are met, carefully evaluate every theme and solution to assess how they further the accomplishment of your organization's aims by asking, "How does this aspect advance our success?"

If it's not immediately clear how a particular item supports a business goal, it may be wise to exclude it from the strategic agenda or defer its evaluation to a later stage. By linking every item on the roadmap to your primary goals, you can clearly explain why they are included, which in turn aligns the interests of all involved parties.

Employing CPA and techniques inspired by the Kano model, alongside assessments of investment returns,

Lombardo, McCarthy, Ryan, and Connors outline a variety of effective strategies to determine which items should be included on the roadmap, among which are three key methods.

1. Examining the crucial progression of steps.

2. The dialogue then transitions to a detailed examination of the Kano model.

3. The method referred to as the ROI scorecard is employed to evaluate the return on investment.

Practical Tips

• Use a decision matrix when faced with multiple personal choices to ensure you're committing to the most impactful ones. Create a simple grid with options as rows and criteria for success as columns. Score each option against the criteria, and prioritize the ones with the highest scores, ensuring you're focusing on what truly matters.
• Use a decision-making app with a feature that allows you to input your organization's aims and evaluate potential solutions based on their alignment. Before making decisions, input the details of the theme or solution into the app and use its analysis to determine how well it serves your organizational goals. This can help ensure that every decision you make is data-driven and aligned with your aims.
• Use a modified CPA (cost per action) approach to track the effectiveness of your health and fitness regimen. Assign a 'cost' to each action, such as time spent exercising or money spent on healthy food, and then track the 'return' in terms of health benefits like weight loss or improved stamina. This can help you determine which activities give you the best health returns for your investment, allowing you to optimize your routine for efficiency and satisfaction.
• Use a decision-making app that's not specifically designed for roadmapping to help you prioritize your goals. Apps like Trello or Notion can be repurposed to create a dynamic and interactive roadmap. Create a board for your goals and use the features like labels, due dates, and progress meters to keep track of what's next. For example, you could label goals as "urgent," "important," or "long-term" and focus on completing tasks in the "urgent" category first.
• Try personalizing your services or products by observing and noting down the 'moments of delight' in your daily interactions with various services. Keep a journal for a week where you record instances when a product or service exceeded your expectations. Use these insights to brainstorm how you could introduce similar 'excitement' features into your offerings that are not yet standard in your industry or sector.
• Engage in a monthly 'ROI discussion club' with friends or family. Each month, choose a different type of investment (like a new tech gadget, a home improvement, or a stock purchase) and discuss the potential returns and risks. This social setting can provide diverse perspectives and help you refine your ability to assess investments beyond just the financial aspect.

Balancing customer advantages, implementation feasibility, and the impact on the company's operations.

Teams responsible for product development frequently evaluate the worth of potential features and initiatives by examining crucial factors like how feasible they are to implement and the advantages they offer to users. Balancing all three factors-customer value, feasibility, and business impact-at the same time, however, will make your decisions more objective and transparent, leading to better prioritization.

The authors recommend calculating a composite score for each initiative by evaluating its potential benefits against the required effort and associated risks. Ideas that achieve the most objectives with minimal effort and risk will stand out as the most favorable options. Keep in mind that the purpose of this computation is to aid in informed decision-making; it is not designed to take those decisions for you.

Securing agreement and harmony among all involved parties.

It is crucial to achieve consensus among all parties engaged with your product and to foster a collaborative environment once the course is charted and the priorities are determined. The authors highlight the complexity and extended duration often required to reach consensus on the roadmap, recommending the initiation of strategic dialogues and the facilitation of joint planning meetings. The structured setting of the workshop ensures that every participant is recognized and given the chance to express their viewpoints through specific activities.

Practical Tips

• Use a modified SWOT analysis to make informed decisions about personal investments, such as education or fitness programs, by assessing the Strengths, Weaknesses, Opportunities, and Threats of each option in relation to your personal circumstances, potential benefits, and the impact on your future.
• Use a three-jar system to manage personal finances, labeling them "Experiences" (customer value), "Savings" (feasibility), and "Investments" (business impact). Allocate your disposable income among the jars each month. For example, money in the Experiences jar could go towards activities that enrich your relationships, Savings for emergency funds or planned purchases, and Investments for stocks or retirement funds, balancing immediate gratification with long-term security.
• You can streamline decision-making by creating a simple "benefit-effort-risk" chart for daily choices. Draw a three-column chart where you list potential actions for the day and score them from 1 to 5 based on their perceived benefit, effort required, and associated risk. Opt for actions with high benefit and low effort and risk scores to prioritize your tasks effectively.
• Start a "Harmony Journal" where you note down instances where you successfully navigated a disagreement or conflict. Reflect on these entries weekly to identify patterns in your behavior that contribute to peaceful resolutions. This self-awareness can guide you in future interactions to prioritize collective harmony.
• Implement a rotating 'consensus facilitator' role in meetings. Assign a different team member for each product development meeting to act as a consensus facilitator. Their job will be to ensure that all opinions are considered and to help the group navigate towards a common agreement. This role rotation prevents dominance by any single voice and helps cultivate a culture of shared responsibility in decision-making.
• Initiate a "Feedback and Fika" tradition, where "Fika" is a Swedish concept of taking a break and enjoying coffee with others. Combine this with a structured time for giving and receiving feedback on ongoing projects or tasks. For instance, during a coffee break, team members can discuss what's working well and what could be improved in their workflow, ensuring that everyone has a voice and feels involved in the process of continuous improvement.
• Develop a habit of sending out pre-meeting 'focus questions' to colleagues or friends before any planned discussion. These questions should be designed to guide participants to think about the topics in advance, ensuring that the meeting time is used efficiently for in-depth strategic dialogue rather than just surface-level updates.
• Implement a "round-robin" approach during family meetings where each person, regardless of age, is given a set amount of uninterrupted time to voice their opinions on family decisions. This practice ensures that everyone, including children who might usually be talked over, has a chance to contribute equally to the conversation.

Using techniques like subtle bargaining and joint workshops

Conducting individual conversations to understand the viewpoints and contributions from stakeholders, then discreetly addressing any conflicting requirements or views, is essential. This approach is akin to the tactics employed by diplomatic mediators who serve as intermediaries, frequently shuttling between adversarial nations to facilitate the negotiation of peace. This technique can be highly effective in reducing friction and politics within teams, allowing you to tailor and focus each meeting around the specific concerns of a particular stakeholder and thus achieve alignment on a mutually acceptable plan. Employ your prioritization techniques efficiently, making the process clear and allowing all participants to understand the reasoning behind particular decisions.

Workshops designed for collaborative efforts convene essential participants in a single setting to collectively decide on the product's direction. The workshop agenda usually begins with a welcoming exercise, moves forward by establishing a collective goal for the product, and ends with a detailed conversation focused on ranking the different obstacles and their respective resolutions. The authors recommend engaging exercises like prompting attendees to jot down their hopes and worries on adhesive notes and to create "Cover Stories," which are imaginative news pieces or blog posts set five years in the future illustrating the successful realization of the product's goals. Participants are often prompted to distribute a set amount of funds to the theme they believe holds the greatest appeal or to rank the themes based on their expected value to the customer.

We maintain that these suggestions are beneficial, and we encourage you to engage in collaborative efforts to identify the optimal strategy for your team.

Practical Tips

• Create a stakeholder empathy map to better understand their perspectives and needs. Draw a simple chart with sections labeled 'Thinking,' 'Feeling,' 'Seeing,' and 'Doing' for each stakeholder you engage with. Fill in each section with notes from your conversations, aiming to capture the essence of their viewpoint. This visual tool can help you remember and reference each stakeholder's unique perspective when making decisions or addressing conflicts.
• Start a virtual suggestion box using a simple online form to gather ideas and feedback about your product's direction from a wider audience. Platforms like Google Forms or Typeform allow you to create a form that you can share with your network or on social media. Encourage people to submit their ideas and preferences for what they'd like to see in your product, which can help you make informed decisions without organizing a full workshop.
• Develop a collaborative goal-setting mobile app feature for existing team communication platforms. This feature would allow team members to propose and vote on goals for their projects. By integrating this into a platform they already use, like Slack or Microsoft Teams, it encourages active participation and ensures everyone is invested in the collective goal from the start.
• Create a visual obstacle map to identify and prioritize challenges in your personal projects. Start by drawing a flowchart that outlines the steps of your project. At each step, note potential obstacles and assign them a color based on severity. Red could indicate critical issues, while yellow might represent minor ones. This visual aid will help you see where the biggest challenges lie and allow you to focus your problem-solving efforts more effectively.
• Create a "worry shredder" ritual where you write down your concerns on paper and physically shred them to symbolize letting go.

Utilizing digital platforms to enhance interaction and monitor progress.

The authors acknowledge that the growth of product teams and the rise in distributed and remote workforces indicate that face-to-face collaboration and meetings might not always be possible. In these cases, software applications can be used to facilitate communication and help track the roadmap components, as well as share, revise, and update the roadmap.

There are numerous instruments designed specifically for the creation and management of roadmaps, as well as for fostering comprehensive collaboration and tracking project progress. Various digital platforms, such as ProdPad, Roadmunk, Aha!, and ProductPlan, provide specialized functionalities for developing roadmaps, which include card-based visualization tools and features for workflow organization similar to a Kanban system. A variety of platforms such as JIRA, Slack, Google Docs, Asana, and Trello can effectively incorporate elements of the product roadmap into a well-organized project management system that features columns, calendars, and timelines.

The authors stress the importance of considering factors beyond just software dependency to maintain coherence. Interacting directly with your stakeholders is essential, as it provides opportunities for in-person conversations that cannot be substituted. Working closely with your colleagues is crucial to finding the right equilibrium between the structured meetings mentioned earlier and the use of modern digital communication and visualization tools.

Practical Tips

• Use a spreadsheet to manage a collaborative roadmap with friends or family for a shared goal, such as planning a group vacation or a community project. Assign tasks, set deadlines, and update the status in the spreadsheet. This approach fosters accountability and ensures everyone is aligned and contributing to the shared objective.
• Develop a habit of weekly personal reviews using a simple spreadsheet. In one column, list the key areas of your life such as career, education, health, and personal relationships. Next to each, note down what you've done that week to advance in these areas, drawing a parallel to how a product roadmap tracks development progress.
• Improve your personal project efficiency by timing your tasks with a smartphone stopwatch and recording the results in a spreadsheet. After a week, analyze the data to identify which tasks take the longest and brainstorm ways to streamline them. This mirrors the analytics aspect of project management systems, providing you with insights into your own productivity patterns.
• Start a 'no-email day' once a month where you focus on face-to-face or phone conversations only. This will encourage you to solve issues or collaborate through direct interaction, giving you a better understanding of the nuances in communication that digital tools might miss.
• Create a "walk-and-talk" initiative in your workplace where you and your colleagues hold meetings while taking a walk outside. This combines the benefits of face-to-face interaction with the advantage of a change in environment, which can stimulate creativity and improve communication. For example, instead of booking a conference room, schedule a time to discuss projects while walking around the block or through a nearby park.