<?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 John Haggerty on Medium]]></title>
        <description><![CDATA[Stories by John Haggerty on Medium]]></description>
        <link>https://medium.com/@jghaggerty?source=rss-48faa0cd7b68------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*bEdPtg6j5G5Bnm_1O54dRw.jpeg</url>
            <title>Stories by John Haggerty on Medium</title>
            <link>https://medium.com/@jghaggerty?source=rss-48faa0cd7b68------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:12:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jghaggerty/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 Product Manager's Guide to Rugby: Drawing Parallels from the 2023 World Cup]]></title>
            <link>https://medium.com/@jghaggerty/the-product-managers-guide-to-rugby-drawing-parallels-from-the-2023-world-cup-91ba8ba2495f?source=rss-48faa0cd7b68------2</link>
            <guid isPermaLink="false">https://medium.com/p/91ba8ba2495f</guid>
            <category><![CDATA[product-management-tool]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[John Haggerty]]></dc:creator>
            <pubDate>Mon, 16 Oct 2023 18:54:00 GMT</pubDate>
            <atom:updated>2023-10-16T18:54:00.482Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UAky6XfXXu-2Y5AR" /><figcaption>The opening ceremonies from the Paris Fan Zone at Place de la Concorde</figcaption></figure><p>Bonjour, mes amis! I recently returned from a 5-week tour in France, and let me tell you, the croissants were buttery, the wine was velvety, and the rugby was unparalleled! At first glance, rugby is a sport of brute strength, quick reflexes, and unyielding endurance. But as I witnessed the 2023 Rugby World Cup unfold in the picturesque landscapes of France, a new revelation dawned upon me. Beyond the tackles and tries, rugby offers product managers a trove of lessons and qualities to be wielded. Intrigued? Let&#39;s dive deeper and bridge the seemingly distant worlds of rugby and product management.</p><h3>Teamwork: Portugal&#39;s Historic Win Over Fiji</h3><p>When Portugal clinched that unexpected victory against Fiji, it wasn&#39;t just an underdog story for the ages. It was a lesson in the sheer power of collaboration. Every pass, every tackle, every move seemed orchestrated, almost like a harmonious dance. It showcased a team that believed in each other, relied on each other&#39;s strengths, and trusted one another to cover their vulnerabilities.</p><p>In product management, teamwork plays a role just as crucial. A harmonious collaboration between developers, designers, marketers, and other stakeholders can differentiate between a product that merely exists and one that excels. In my own experiences in the PM world, it&#39;s not just about individual expertise but about how well a team can synergize those unique talents to create something exceptional.</p><p>Consider those brainstorming sessions where a junior developer&#39;s idea complements a senior designer&#39;s vision, leading to a groundbreaking feature. Or those challenging times when one department falls short, only for another to step in seamlessly, ensuring the product remains on track. This is the essence of teamwork, the magic ingredient in Portugal&#39;s win and successful product management.</p><h3>Strategy: New Zealand&#39;s Tactical Mastery Against Ireland</h3><p>A Japanese Proverb states that strategy without execution is a daydream, and execution without strategy is a nightmare. In their riveting face-off against Ireland, the New Zealand All Blacks demonstrated this mantra flawlessly. Each move, each formation, seemed calculated, always staying a few steps ahead of the opposition.</p><p>Product management, in many ways, dances to a similar tune. Crafting a visionary roadmap is just one piece of the puzzle. The real challenge lies in navigating the challenges that come along the way — ever-evolving market dynamics, user behavior shifts, and the occasional unexpected curveball from competitors.</p><p>In the match, it was evident that the All Blacks weren&#39;t just playing reactively. They proactively anticipated Ireland&#39;s moves, much like how adept product managers preempt user needs or foresee market shifts. It serves as a reminder that the best strategies are dynamic, agile, and adaptable, always keeping an eye on the end goal while being flexible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YCm6DigK8vo520J4" /><figcaption>Ireland vs South Africa at Stade de France</figcaption></figure><h3>Adaptability: South Africa&#39;s Resilience Against France</h3><p>Watching South Africa pivot their game plan mid-way, adjusting to the formidable French offense, was a masterclass in adaptability. Against the roaring backdrop of French supporters, the Springboks displayed a resilience that showcased their physical prowess and mental agility.</p><p>In the product world, adaptability is the cornerstone of success. Whether it&#39;s a sudden change in market regulations, a disruptive technological innovation, or a global event impacting user behavior, the landscape is ever-shifting. The most successful product managers treat these changes not as setbacks but as opportunities to pivot, reassess, and innovate.</p><p>South Africa&#39;s match against France serves as a poignant reminder of this. Just as they adjusted their strategies on the fly, navigating challenges to clinch the win, product managers must embrace adaptability as their North Star, ensuring they remain relevant and impactful in a constantly evolving ecosystem.</p><h3>Continuous Learning: Wales&#39; Resolve Post Argentina Loss</h3><p>Defeat, as Wales showed us, isn&#39;t the end but often the beginning of a renewed journey. Their loss to Argentina could have been a moment of despair, but they transformed it into a catalyst for reflection, growth, and future victories. It was a testament to the power of perspective and the spirit of continuous learning.</p><p>This ethos finds a resonant echo in product management. Every product journey witnesses its share of hurdles. Some features may not resonate with users as anticipated, or a marketing strategy might not yield the expected traction. However, the essence of progress lies in not just acknowledging these setbacks but in dissecting them, understanding the underlying reasons, and iterating for better outcomes.</p><p>Wales&#39; approach after their match with Argentina drives home this point. It emphasizes that setbacks are merely stepping stones in rugby and products, teaching moments that pave the way for future successes.</p><h3>Passion &amp; Commitment: The Indomitable Spirit of Irish Fans</h3><p>The enthusiasm, the singing, the unwavering support even in the face of defeat — the Irish fans brought to life the heart of rugby. Their commitment transcended the match&#39;s scoreline, showcasing an unshakeable and profound bond with their team.</p><p>Similarly, in product management, passion, and commitment form the bedrock of every successful venture. This is evident in those late-night brainstorming sessions, the relentless pursuit of perfection, and the unwavering belief in a product&#39;s potential even when faced with challenges.</p><p>The dedication of the Irish fans serves as a vibrant reminder of this ethos. It underscores the importance of believing in the journey, staying committed through the highs and lows, and channeling passion into tangible results. Whether it&#39;s the roaring stands of a rugby stadium or the bustling offices of a tech startup, this spirit drives success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AL7Tlvpi8BliZZEC" /><figcaption>Stade de France shortly after Ireland&#39;s win over Scotland</figcaption></figure><p>As we eagerly await the upcoming semifinals and the grand finale of the 2023 Rugby World Cup, the journey thus far has been nothing short of exhilarating. Even though we won&#39;t witness the passionate Irish supporters serenading the stands with the haunting melodies of &quot;Zombie&quot; or the poignant &quot;The Fields of Athenry,&quot; I urge you to tune in. Experience the sport I cherish, the sheer dynamism of it, and the myriad of lessons it imparts. Like product management, rugby is a dance of strategy, adaptability, and passion. It&#39;s about seizing opportunities, learning from setbacks, and always pushing the boundaries. So, as the world watches the final chapters of this World Cup unfold, let it be a reminder to all product managers: to tackle challenges head-on, to evolve constantly, and to always play with heart, passion, and unwavering commitment. 🏉💼🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91ba8ba2495f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Does Your Roadmap Have Product-Market Fit?]]></title>
            <link>https://medium.com/@jghaggerty/does-your-roadmap-have-product-market-fit-c180dc907cc4?source=rss-48faa0cd7b68------2</link>
            <guid isPermaLink="false">https://medium.com/p/c180dc907cc4</guid>
            <category><![CDATA[product-roadmapping]]></category>
            <category><![CDATA[product-roadmap]]></category>
            <category><![CDATA[build-a-product-roadmap]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-leadership]]></category>
            <dc:creator><![CDATA[John Haggerty]]></dc:creator>
            <pubDate>Tue, 16 May 2023 13:41:23 GMT</pubDate>
            <atom:updated>2023-05-16T13:41:23.068Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7MlP98zld6_XF3y2.png" /></figure><p>As product managers and product leaders, we understand the critical role that product roadmaps play in guiding our product strategy and communicating our vision. They serve as a roadmap for success, outlining the milestones and initiatives that will lead us to achieve product-market fit.</p><p>However, it is essential to recognize that roadmaps are not just static documents. They are products designed to meet our stakeholders&#39; needs and expectations. Let&#39;s explore the concept of product-market fit within the context of roadmaps and discuss the importance of testing and validating our roadmaps with stakeholders to ensure they align with their needs.</p><p>One of the strengths of product roadmaps is their ability to foster alignment and synchronization across teams and stakeholders. By clearly communicating our product strategy and vision, roadmaps ensure that everyone involved is on the same page.</p><p>However, involving stakeholders in the roadmap development process is vital for product-market fit. This means engaging with them, gathering their feedback, and validating that the roadmap fulfills their needs and expectations. For example, in my experience as a product leader, I have conducted regular stakeholder meetings and workshops to gather insights and ensure that the roadmap aligns with their priorities.</p><p>By involving stakeholders throughout the roadmap&#39;s lifecycle, we can ensure that it remains responsive to their changing needs. For instance, at my previous company, we conducted extensive customer interviews and usability testing to validate our roadmap assumptions and ensure they effectively addressed their pain points. Today, I do the same with the consumers of the roadmap — our stakeholders.</p><p>A customer-centric approach is crucial when designing a roadmap that has product-market fit. It is essential to understand our target market&#39;s pain points and desires and incorporate them into the roadmap. Continuous discovery practices like user interviews, surveys, and feedback loops can provide valuable insights to evolve the roadmap. A product roadmap is not just a static plan but a product that requires product-market fit that needs to be validated with its users, your stakeholders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*V9Iz5dMii7jF8P3T.png" /></figure><p>While roadmaps offer valuable benefits, they also have drawbacks that must be navigated. One challenge is the potential rigidity that can arise from strictly adhering to a predefined roadmap. Product roadmaps develop rigidity due to several factors. Including:</p><ol><li><strong>Overcommitment to a Plan</strong>: Product teams may become over-attached to the initial roadmap they have created. They might feel pressured to adhere strictly to the plan, even when market conditions or customer needs change.</li><li><strong>Lack of Feedback and Validation</strong>: A product roadmap needs to be developed with sufficient input from stakeholders and customers to avoid becoming detached from reality. With continuous feedback and validation, the roadmap may reflect changing market dynamics and customer expectations.</li><li><strong>Limited Room for Iteration</strong>: Some roadmaps are designed with a fixed timeline and set of features, leaving little room for iteration and adaptation. This fixed mindset can hinder the team&#39;s response to new information, feedback, or emerging opportunities.</li><li><strong>Organizational Pressures and Expectations</strong>: In some instances, external pressures from stakeholders or higher-level management can contribute to the rigidity of a roadmap. Stakeholders may have specific expectations or demands the product team feels obligated to meet, even if it means deviating from the evolving market conditions.</li></ol><p>To address this, adopting an agile and flexible mindset is crucial. Regularly reassessing and adapting the roadmap based on new information and market dynamics allows us to stay responsive to change. Moreover, roadmaps should be viewed as living documents that can be refined and modified based on stakeholder feedback and continuous discovery practices. This iterative approach ensures the roadmap remains relevant and aligned with product-market fit.</p><p>In my current role at ListReports and MBS Highway, we encourage a culture of continuous learning and improvement within our product team. We emphasize the importance of gathering data, seeking feedback, and embracing a growth mindset. This mindset lets our team view the roadmap as a living document that evolves based on new information and insights.</p><p>Navigating the strengths and limitations of roadmaps while embracing adaptability and flexibility allows us to optimize their effectiveness. We need to treat roadmaps as products and living artifacts. We must embrace continuous discovery and validate our assumptions, enabling us to navigate our products and the roadmap to product-market fit. Through collaboration, communication, and a commitment to quality, we can unlock the full potential of our roadmaps and drive our products toward success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c180dc907cc4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Management Skills for Product Leaders]]></title>
            <link>https://medium.com/@jghaggerty/product-management-skills-for-product-leaders-dcf4d0b39b95?source=rss-48faa0cd7b68------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcf4d0b39b95</guid>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[product-discovery]]></category>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-leaders]]></category>
            <dc:creator><![CDATA[John Haggerty]]></dc:creator>
            <pubDate>Tue, 09 May 2023 13:07:12 GMT</pubDate>
            <atom:updated>2023-05-09T17:21:17.305Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*35c-Dtubpbu4x13L.png" /></figure><p>Product management is a complex and multifaceted role that requires various skills, from leadership and team management to technical knowledge and market research. Product leaders need to have a deep understanding of the products they oversee and the markets they operate in, plus the ability to communicate effectively with all stakeholders involved in the product development process. In my experience, applying product management skills as a product leader can inspire and align the product team and the broader organization.</p><p>One of the most critical skills that product leaders must possess is the ability to inspire and motivate their teams to work toward a common goal. They need to be able to create a shared vision and align their teams behind it, ensuring that everyone is working towards the same objectives. By doing so, they can build trust with their team and stakeholders, fostering collaboration and driving product success.</p><p>Here are four key areas where product management skills can be applied as a product leader to deliver inspiration and alignment for the product team and the broader organization.</p><h3><strong>The one-on-one</strong></h3><p>One way to apply product management skills as a product leader is by approaching one-on-one meetings as discovery sessions, focusing on listening more than talking. When meeting with a direct report or stakeholder, resist the urge to jump in and offer solutions immediately. Instead, ask open-ended questions to understand their perspective and their challenges. Try to get to the root cause of the problem and ask follow-up questions for more clarity.</p><p>By taking the time to listen and understand, you can build trust with your team and stakeholders. People are more likely, to be honest, and open with you if they feel heard and valued. This can help you uncover issues that you may have yet to be aware of and identify opportunities for improvement.</p><p>In addition to listening, taking notes during the meeting and following up afterward is essential. This shows that you accept their feedback seriously and value their input. You can use these notes to identify patterns and themes across your team or stakeholders.</p><p>You can also help your team develop their problem-solving skills. Instead of immediately providing solutions, ask your direct reports to create their ideas and solutions. This can help them develop critical thinking skills and take ownership of their work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eBvAXUBfpbJ57p9_.png" /></figure><h3>Finding Product Market Fit</h3><p>As a product leader, it’s essential not just to develop a product strategy but also to effectively deliver the product strategy, product vision, and product roadmap to the organization. Cross-functional collaboration with departments such as sales, marketing, and customer success is vital to ensure success within the organization. By prioritizing internal alignment and incorporating stakeholder feedback, a product leader can ensure that their team is delivering what is needed in a manner that works for the stakeholders across the organization.</p><p>To foster collaboration, discovery tactics can be incorporated into deliverables like sprint reviews, release updates, and the product roadmap. During my time at ListReports, we’ve used <a href="https://review.firstround.com/how-superhuman-built-an-engine-to-find-product-market-fit">Rahul Vohra’s Product Market Fit Engine</a>, allowing us to validate that our deliverables to the internal teams have product market fit. Through surveying internal stakeholders, such as sales and customer success teams, we gained valuable insights into our customers’ pain points and needs, which informed how we operate.</p><p>In addition to surveys, we hold regular meetings with other departments to discuss our product roadmap and gather feedback. We discuss features and how to deliver the message internally and to our customers. This helps us ensure that we are aligned with the organization’s needs and that our team provides what is needed for internal success.</p><p>By prioritizing internal alignment and incorporating stakeholder feedback, a product leader can ensure that their team is delivering what is needed in a manner that works for the stakeholders across the organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DMEAbIuR8pjaaum6.png" /></figure><h3>Data-Informed Decision-Making</h3><p>As a product leader, one of your key responsibilities is ensuring that your team continuously improves and grows. To do this, you need to provide them with regular feedback and opportunities for development. One way to do this is by using a scoring matrix combining quantitative and qualitative data. This can help you identify areas where your team members excel and areas where they need improvement.</p><p>One approach that has worked for me is creating a scoring matrix using tools such as <a href="https://www.strongproductpeople.com/pmwheel">Petra Wille’s PM Wheel</a> and <a href="https://www.laurenchanlee.com/writing/introducing-the-product-decagon-a-way-for-pms-to-navigate-to-their-dream-job">Lauren Chan Lee’s Product Decagon</a>. These tools help you assess your team members’ skills across various product management domains. By combining these tools with my assessment criteria, I’ve created a comprehensive scoring matrix that captures the quantitative and qualitative aspects of my team’s performance.</p><p>Qualitative data includes weekly 1:1 notes, quarterly surveys, and annual reviews. This data can provide valuable insights into your team’s mindset, motivation, and communication skills. Quantitative data includes self-assessments, manager assessments, and role-level scoring. I feed these data points can then be visualized into a spider-web chart giving details about where gaps are at the individual and team levels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XRturBUjnEmWXzoy7Ry70g.png" /><figcaption>Sample Data Visualization</figcaption></figure><p>You can use this data to identify patterns and trends, highlight successes and areas for improvement, and communicate your team’s progress to stakeholders. This can help you build a case for additional resources, support, and investment in the product team.</p><h3>Clearly Defined Outcomes</h3><p>It’s crucial to clearly understand why you are implementing changes and what you hope to achieve. This requires defining the desired outcomes and setting achievable goals. However, it’s not enough to set these goals; you must communicate them effectively to your team and stakeholders. Without effective communication, your team may not fully understand the reasoning behind the changes, which can lead to a lack of buy-in and reduced morale.</p><p>Setting your goals requires thinking ambitiously while acting realistically. It’s easy to get carried away with setting lofty goals, but if they are not achievable, they can quickly become demotivating for your team. It is crucial to divide more significant objectives into smaller attainable and measurable milestones to guarantee that progress is being achieved. Sounds a bit like iterative development.</p><p>To measure the success of your goals, you must have clear metrics in place. These metrics should be tied to your desired outcomes and be measurable, achievable, and aligned with the company’s objectives. By tracking progress against these metrics, you can assess whether you are on track to achieve your goals and make adjustments if necessary. Additionally, it would be best to communicate progress to your team and stakeholders to ensure transparency and maintain alignment.</p><p>Product management tools and skills can be applied as a product leader to deliver inspiration and alignment for the product team and the broader organization. By inspiring and motivating the teams, fostering collaboration, using data to drive decisions, and setting achievable but iterative goals, product leaders can ensure their team is delivering what is needed in a manner that works for the stakeholders across the organization, driving product success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcf4d0b39b95" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When is Too Much Customer Discovery Bad?]]></title>
            <link>https://medium.com/@jghaggerty/when-is-too-much-customer-discovery-bad-cefee096b33b?source=rss-48faa0cd7b68------2</link>
            <guid isPermaLink="false">https://medium.com/p/cefee096b33b</guid>
            <category><![CDATA[product-discovery]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-risk-management]]></category>
            <category><![CDATA[product-management-tool]]></category>
            <category><![CDATA[product-delivery]]></category>
            <dc:creator><![CDATA[John Haggerty]]></dc:creator>
            <pubDate>Mon, 01 May 2023 14:02:47 GMT</pubDate>
            <atom:updated>2023-05-01T14:02:47.043Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/896/0*xwnjGDqkplrB6s1U.png" /></figure><p>In today’s fast-paced business world, startups and established companies often place a high value on customer discovery, which involves gathering and analyzing information about potential customers to improve the chances of product-market fit. While this approach is immensely beneficial, as highlighted by product experts Teresa Torres and Marty Cagan, there is a risk of becoming overly reliant on data and analysis. This phenomenon, known as analysis paralysis, can hinder progress and prevent companies from achieving their goals. Let’s explore the importance of customer discovery and the potential pitfalls of relying too heavily on it.</p><p>As a product manager, you’re constantly balancing discovery and delivery to ensure you create valuable products for your customers. The more confident you are in a solution and the less risk it has, the less discovery you need to do. But, as you become less secure or the situation becomes riskier, you need to do more discovery. This tradeoff is crucial in ensuring you deliver value to your customers while minimizing risk.</p><p>But how do you balance being first to market with needing discovery and validation? The approach you take depends on the level of confidence in your solution and the level of risk involved. If your solution has low risk and you are confident in it, being first to market is more important than conducting more discovery. However, if the situation is riskier or you need more confidence, conducting more discovery may be necessary before you can confidently launch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/697/1*t1S_S3puJNHupMHH2iytcw.png" /></figure><p>To draw a line between when to proceed with minimal discovery and when more validation is necessary, you can quantify risk on an x-axis and confidence on a y-axis. Anything above that line is considered a “Safe Bet,” where you can proceed with minimal discovery. Items that fall into the category of low risk but have higher confidence are considered “OK Bets,” where you have a common need for discovery but still need to do some validation. On the other hand, items that are high risk and low confidence are considered “Bad Bets” and require a lot of confirmation through discovery before proceeding. Most product initiatives fall in the middle of the road and are classified as “Not Ideal Bets.” This means they require more discovery than most people expect.</p><p>Conducting more discovery may be necessary when the solution involves high risk, or you need more confidence. Drawing a line by quantifying risk and confidence can help you determine whether to proceed with minimal discovery or to conduct more validation. Most product initiatives fall in the middle of the road and require more discovery than people expect. It’s essential to find the right balance to avoid analysis paralysis and ensure that you’re making the best decisions for your product.</p><p>To better understand this tradeoff, let’s look at some examples.</p><h3>Safe Bets</h3><p>While I was at InboxDollars, we had to update our sign-up and sign-in flows to account for GDPR and CCPA. These were regulatory changes that were required to be implemented. The legal team informed us more about what we had to do than discovery with the end users. This was a “safe bet” because it was a regulatory requirement, and there was no risk in implementing the changes.</p><p>Regulatory changes like these are often necessary and non-negotiable. Therefore, while minimal discovery may be needed to ensure that the implementation complies with the regulation, there is often little need to delve deeply into the user experience. In situations like this, the product manager’s role is to ensure that the implementation is in line with the regulation while minimizing any negative impact on the user experience.</p><p>Safe Bets are initiatives with a low risk of failure and high confidence that they will deliver value to the end users. These may include regulatory changes or well-established features expected by the market. While some discovery is always necessary, the focus should be on execution and ensuring the implementation aligns with the required standards. The product manager’s role is to manage the project effectively and ensure the implementation is successful while minimizing any negative impact on the user experience.</p><h3>OK Bets</h3><p>Some features or functionalities are well-established, and their success is almost guaranteed. These are often referred to as “table stakes” features. As a product manager, you still need to validate their relevance to your specific user base, but the level of risk is low compared to other, more innovative features.</p><p>At Merrill DataSite, we were developing a new virtual data room product platform. One of the features that we needed to include was a keyword search functionality. This is a common feature in the virtual data room space (and pretty much everywhere else), and we knew that our customers expected it. However, we still needed to validate that our implementation met their needs and expectations.</p><p>We conducted a few rounds of user testing with existing customers to validate this feature. We asked them to perform everyday search tasks and provided feedback on the results. After releasing the feature, we also monitored usage data to ensure it was being used as expected. Overall, we were confident that this feature met our customers’ needs.</p><p>While this was an OK Bet, ensuring we delivered value to our customers was still necessary. The discovery process helped us validate that our implementation was meeting their needs and gave us insights into potential areas for improvement. By doing this validation upfront, we ensured that our delivery process was efficient and that we were delivering value to our customers with the minimum viable product.</p><h3>Bad Bets</h3><p>“Bad Bets” are the riskiest bets a product manager can take. These are initiatives with high risk and low confidence, which means they require a lot of validation through discovery before proceeding. In many cases, these bets can have significant consequences for the company if they fail, such as a loss of revenue or a negative impact on brand reputation. Therefore, it is critical to understand the risks involved and determine whether the potential rewards justify the investment in discovery.</p><p>As a product manager or product leader, it is essential to recognize the signs of a “Bad Bet.” These can include a need for more understanding of the customer’s needs, unclear product requirements, or a lack of available data to support the initiative. In such cases, the product manager needs to prioritize discovery to increase confidence and reduce the risks associated with the initiative.</p><p>Several times in my career, there have been proposals for new products, features, or functionalities. These are often to open up new verticals or revenue streams. These are the times when it’s better to do the discovery needed to increase your confidence above the line into the “safe bet” range. More often than not, launching a new product or entering a new market without sufficient validation results in a product that fails to deliver the intended value and a market already saturated.</p><p>Bad Bets are the riskiest bets a product manager can take on, and they require a lot of validation through discovery before proceeding. As a product manager, it is essential to understand the risks involved, recognize the signs of a Bad Bet, and prioritize discovery to increase confidence and reduce risks. Failure to do so can result in a loss of revenue, a negative impact on brand reputation, and missed opportunities.</p><h3>Not Ideal Bets</h3><p>Not Ideal Bets are those product initiatives that fall in the middle of the road and require more discovery than most people expect. These initiatives are often more complex or innovative than OK Bets, and the level of risk is higher. As a result, more validation and discovery are required to increase confidence levels and ensure that the product delivers value to the customers.</p><p>At Merrill DataSite, we expanded the search functionality to include filters and facets. This required more discovery with users to help us understand what they were searching for and their expectations. We conducted several rounds of user research and user testing to validate that our implementation was meeting the needs of our customers. We asked them about their search behavior, what criteria they used to filter their searches, and what information they wanted to see in the search results. Based on this feedback, we iterated on our design and functionality until we had a product that met their needs.</p><p>The discovery process for “Not Ideal Bets” can be more time-consuming and expensive, but it’s essential to ensure that you deliver a product that meets your customers’ needs. Doing this validation upfront can avoid costly mistakes and ensure you deliver value with the minimum viable product.</p><h3>First to market</h3><p>It’s important to note that there’s increased value in being first to market, which reduces the overall weight of the risk score. The sooner you can get something out, the better, but that only matters when you’re first to market. If you’re not first, you must ensure that you deliver a superior product based on customer needs and preferences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/0*mOyczM09Po5hmDVI.png" /></figure><p>In conclusion, as a product manager, balancing discovery and delivery is vital to create valuable products for your customers while minimizing risk. Understanding the different bets and associated risks is crucial in making informed decisions about where to focus your efforts. Remember that there’s increased value in being first to market, but that doesn’t mean you should rush to release a product that doesn’t meet your customers’ needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cefee096b33b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PM’s Guide to Stakeholder Management]]></title>
            <link>https://medium.com/@jghaggerty/pms-guide-to-stakeholder-management-36e2e6002a4d?source=rss-48faa0cd7b68------2</link>
            <guid isPermaLink="false">https://medium.com/p/36e2e6002a4d</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[pm]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[product-leadership]]></category>
            <dc:creator><![CDATA[John Haggerty]]></dc:creator>
            <pubDate>Mon, 24 Apr 2023 21:54:07 GMT</pubDate>
            <atom:updated>2023-08-21T21:35:46.194Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A PM meeting with Stakeholders" src="https://cdn-images-1.medium.com/max/1024/0*ZLxG0SGiyHkrS5-2.png" /></figure><p>As a product manager, your success depends not only on your ability to create great products but also on your ability to manage stakeholders effectively. Stakeholder management is a critical skill that can help you build strong relationships with everyone involved in your product’s success, from developers and designers to executives and customers.</p><h3>What is a Stakeholder?</h3><p>Simply put, if you think of all the people or groups with a stake in your product’s success, those are your stakeholders. This might include your team members, customers, investors, executives, and other stakeholders. Stakeholder management aims to build strong relationships with these stakeholders and ensure everyone is aligned around the product vision and goals.</p><p>So why is stakeholder management so crucial for a product manager in a product-led organization? Here are a few key reasons:</p><ol><li><strong>It helps you build trust and credibility</strong>: When you can effectively manage stakeholders, you build trust and credibility with everyone involved in your product’s success. This can help you get buy-in for your ideas, build stronger partnerships, and ultimately drive better outcomes for your product.</li><li><strong>It helps you prioritize effectively</strong>: As a product manager, you constantly face competing priorities. By understanding your stakeholders’ needs and goals, you can make more informed decisions about which features to prioritize and when. This can help you avoid wasting time and resources on less important features to your stakeholders.</li><li><strong>It helps you communicate effectively</strong>: Communication is critical in any product management role. When managing stakeholders effectively, you can share more effectively with everyone involved in your product’s success. This can help you avoid misunderstandings, get buy-in for your ideas, and ultimately drive better outcomes for your product.</li><li><strong>It helps you stay aligned with your product vision</strong>: As a product manager, it’s your job to ensure everyone on your team is aligned around the product vision and goals. By effectively managing stakeholders, you can ensure everyone is on the same page and working towards the same goals.</li></ol><figure><img alt="A Product Manager working on a laptop in a forest" src="https://cdn-images-1.medium.com/max/1024/0*XxyVAe144aUWPIwm.png" /></figure><h3>Breaking down Stakeholder Management</h3><p>So how can you effectively manage stakeholders as a product manager in a product-led organization? Here are a few tips:</p><ol><li><strong>Identify your stakeholders</strong>: The first step in stakeholder management is to identify all the people or groups who have a stake in your product’s success. This might include your team members, customers, investors, executives, and other stakeholders.</li><li><strong>Understand their needs and goals</strong>: Once you’ve identified your stakeholders, take the time to understand them. What do they want to achieve? What are their pain points? How can your product help them achieve their goals?</li><li><strong>Learn how to communicate effectively</strong>: Communication is vital in stakeholder management. You need to understand your stakeholders’ style of communication. What do they use to communicate - email, Slack, or prefer meetings?</li><li><strong>Schedule regular updates</strong>: Ensure you communicate regularly and clearly with all your stakeholders. This might include regular status updates, discussions, and other forms of communication. Plus, follow up with your stakeholders. Are they getting what they need from your updates?</li><li><strong>Build strong relationships</strong>: Building solid relationships with your stakeholders is critical. Take the time to get to know them and build trust and credibility.</li><li><strong>Prioritize effectively</strong>: Use your understanding of your stakeholders’ needs and goals to prioritize effectively. Ensure you focus on the features and projects that will impact your stakeholders the most.</li></ol><p>Here is an example of a <a href="https://docs.google.com/spreadsheets/d/1bM-I17iRCGeTJmcER4tBCq7memxtP3Sk58TJfDdHomI/edit?usp=sharing"><strong>Stakeholder Engagement Map</strong></a><strong> </strong>that can be used to keep track of the Who, What, Where, When, Why, and How of stakeholder management.</p><figure><img alt="Stakeholder management guide" src="https://cdn-images-1.medium.com/max/1024/1*oYpcH4HZdeKE5WZlZ37bMA.png" /></figure><p>In conclusion, stakeholder management is critical for any product manager. By effectively managing your stakeholders, you can build trust and credibility, prioritize effectively, communicate more effectively, and stay aligned with your product vision. Take the time to understand your stakeholders’ needs and goals, communicate regularly and clearly, and build strong relationships with everyone involved in your product’s success. With effective stakeholder management, you can drive better outcomes for your product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36e2e6002a4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>