<?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 Gayathri Govindaraju on Medium]]></title>
        <description><![CDATA[Stories by Gayathri Govindaraju on Medium]]></description>
        <link>https://medium.com/@withgayathri?source=rss-886086c8327f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jgNP_4Y645vXEwe1-Ap5zg.jpeg</url>
            <title>Stories by Gayathri Govindaraju on Medium</title>
            <link>https://medium.com/@withgayathri?source=rss-886086c8327f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:16:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@withgayathri/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[Maximize Stakeholder Buy-In For A Collaborative Product Strategy And Product Roadmap]]></title>
            <link>https://medium.com/agileinsider/maximize-stakeholder-buy-in-for-a-collaborative-product-strategy-and-product-roadmap-8f649d336a25?source=rss-886086c8327f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f649d336a25</guid>
            <category><![CDATA[product-roadmap]]></category>
            <category><![CDATA[communication-strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <dc:creator><![CDATA[Gayathri Govindaraju]]></dc:creator>
            <pubDate>Sat, 14 Feb 2026 00:30:45 GMT</pubDate>
            <atom:updated>2026-02-14T00:30:45.415Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*1_WRfC16jqogOi-96o86mw.png" /></figure><p>Without the right stakeholders involved, you’ll struggle to strategize your product and find it challenging to deliver the roadmap. The most effective product strategy and product roadmap become ineffective when you lack stakeholders’ buy-in. The final products built will be useless and will not serve the business purpose.</p><p>You shouldn’t worry if you follow the tips in this article to ensure stronger stakeholder engagement, more efficient decision-making, and, eventually, launch a successful product through collective efforts.</p><h3>Identifying &amp; involving the right stakeholders</h3><p>Stakeholders typically include senior management, marketing, sales, service, operations, finance, and HR, as well as external partners and, in some cases, board members. Especially in larger organizations, the stakeholder group can be larger than typical, making it hard to get everyone’s buy-in. Coordinating and communicating with everyone can be time-consuming and impractical.</p><p>What should you do in such a case? How can we enhance stakeholder engagement and ensure that the right messaging reaches the group promptly?</p><p>Conduct a stakeholder analysis using tools such as the <a href="https://www.projectmanagement.com/wikis/368897/stakeholder-analysis--using-the-power-interest-grid#_"><strong><em>Power-Interest Grid</em></strong></a>, as<strong> </strong>shown in the figure below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/366/1*DAfhYhRS6JOp0vDGchchPw.png" /><figcaption><em>Reference: PMI</em></figcaption></figure><p>Identify just those who should be part of your <strong><em>focus group</em></strong>. The stakeholders in the focus group are the individuals whose input and support are required from the strategy stage through to execution and release.</p><p>Depending on their influence and genuine interest in the product, place stakeholders in the appropriate quadrants to spend your efforts wisely. For example, people with <strong><em>high interest and high power</em></strong> are the real players. They are generally involved in every stage from product strategy to product launch. Their expertise is required to make the right decisions, and their support helps with faster execution.</p><p>Depending on their roles, keep the stakeholders in the other quadrants informed about the changes and project progress throughout. Invite them to timely review meetings, demo sessions, or one-on-one meetings with high-power stakeholders who are the actual context-setters.</p><h3>Secure the buy-in strategically</h3><blockquote>Approvals are not always straightforward.</blockquote><p>According to the <strong><em>Power-Interest Grid</em></strong>, some stakeholders hold greater power and interest and therefore have more influence on decisions framing the product strategy.</p><p>While smaller strategy updates and roadmap changes are not critical, larger and more critical updates require better coordination. The greater the impact of a decision is, the more buy-in it needs from the different stakeholder groups. In cases of new implementations or significant feature changes, the strategy has an even higher impact, and the stakeholders should unanimously agree.</p><p>You may use techniques such as the <a href="https://simplystakeholders.com/stakeholder-engagement-assessment-matrix/"><strong><em>stakeholder agreement scale </em></strong></a>to achieve even greater understanding and clarity. Check the figure below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*U8uAMwVwBwtlJBL0BgvrFQ.png" /><figcaption><em>Reference: Simply Stakeholders</em></figcaption></figure><p>A sign of achieving unanimity is when most people completely agree or endorse the strategy, even though a few have minor reservations. Similarly, when nobody flags that they can’t support the strategy or roadmap, signaling no disagreement with the approach, consider that it is a GO decision from the board.</p><p>In case of disagreement, get help from the high-power &amp; high-interest stakeholders in your grid quadrant. Then the person in charge unblocks the decision process and helps everyone move forward.</p><h3>Collaborate to develop the Product Strategy and Roadmap</h3><p>For better collaboration, always engage stakeholders on strategy updates and roadmap progress. Secure their support by proactively collecting their feedback, making the relevant updates, and implementing their suggestions to deliver the best product that serves the exact business purpose. This is a simple workflow when the proposed changes are simple to implement, and the stakeholders are closely aligned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*2XAEtNS3Rqd5O4idFShX7g.png" /></figure><p>What happens when the bigger changes are required? How can you get agreement when stakeholder groups are more diverse and have different approaches to achieving the final product?</p><p>In that case, act smart and choose a less time-consuming approach. Accept that it is hard to reach the required level of buy-in. A better way to co-create the product strategy and roadmap is to quickly reach unanimity without making weak compromises by educating stakeholders about their respective ideas, interests, and associated concerns.</p><p>Bring people together through collaborative workshops. It is also smart to get help from a skilled facilitator to prepare and lead the discussion, ensuring everyone is heard and no one dominates the decision-making process. This is especially helpful when the group is pretty diverse and new to collaborative decision-making. While there are endless digital resources to achieve this, a personal meeting is always better than an online one, just to understand the nuances and connect better.</p><p>You can take this approach and the product to the next level by looping in customer feedback. See my article <a href="https://medium.com/agileinsider/customer-feedback-loops-the-biggest-contributor-to-a-successful-product-316444902e1"><strong><em>Customer feedback loops — The biggest contributor to a successful product</em></strong></a>.</p><h3>Help Stakeholders Fulfill Commitments</h3><p>When a stakeholder agrees with the roadmap and product strategy, it is generally expected that the person will remain aligned with it until subsequent iterations. Sometimes, this won’t be the case.</p><p><em>For instance, the sales manager, a key stakeholder, is fully aware of the product features and the roadmap, yet promises a feature to an important client that is not part of the roadmap.</em></p><p>Such things can often happen out of temptation or under pressure to keep a client happy. A product manager who owns the product roadmap and features should gatekeep such incidents and help other stakeholders fulfill their commitments.</p><p>There is no room for temptations to add new features to the roadmap and get them developed at this stage. This is absolutely not the best practice because the new feature has not been approved by all key stakeholders.</p><p>The sales manager in this case has clearly consented to the roadmap and participated in the decision-making process; he should adhere to the strategy &amp; roadmap. If the product manager ignores these ad hoc deviations, there won’t be any greater meaning to collaborative stakeholder buy-in.</p><p>The best way to address such issues is by using feedback frameworks like <a href="https://www.ccl.org/articles/leading-effectively-articles/closing-the-gap-between-intent-vs-impact-sbii/"><strong><em>(SBI)™ Situation-Behavior-Impact</em></strong></a> to understand intent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1006/1*dZNpSMCzoNNtEmhlWDGhLg.png" /><figcaption>Reference: CCL - Center for Creative Leadeship</figcaption></figure><p>Take time to empathize with your stakeholders. Ask for perceptions related to each use case. Listen and describe the observations. Let the facts speak, not assumptions and prejudices, and absolutely no blame game.</p><p>Identify the underlying issues. Create a shared understanding. Define the actions required to address the issues. And be prepared to contribute to solving the issue. Clearly describe the desired outcome and impact of decisions along with the context and conditions.</p><p>Wrapping up: Set up follow-up meetings whenever needed. And finally, and importantly, always document the findings.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f649d336a25" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/maximize-stakeholder-buy-in-for-a-collaborative-product-strategy-and-product-roadmap-8f649d336a25">Maximize Stakeholder Buy-In For A Collaborative Product Strategy And Product Roadmap</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mindsets for complex CRM projects]]></title>
            <link>https://medium.com/salesforce-business-analysts/mindsets-for-complex-crm-projects-e2b302c90991?source=rss-886086c8327f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2b302c90991</guid>
            <category><![CDATA[person-to-person]]></category>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[people-first]]></category>
            <category><![CDATA[crm]]></category>
            <dc:creator><![CDATA[Gayathri Govindaraju]]></dc:creator>
            <pubDate>Tue, 18 Nov 2025 07:57:52 GMT</pubDate>
            <atom:updated>2025-11-18T07:57:52.362Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*778cseGulPMumof9" /><figcaption>Photo by <a href="https://unsplash.com/@kommers?utm_source=medium&amp;utm_medium=referral">KOMMERS</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Innovation and technology have always been at the forefront of the discussions. And as a result, digitalization and automation are in full swing. That’s why we continue to hear phrases like: “We have digitized our procurement transactions; We are automating all the manual processes in our sales team.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*xl49bDN9vGmxuahWw1nlzQ.png" /></figure><p>Complex CRM implementations are not simply software rollouts — they are <strong>organizational change initiatives</strong>.</p><h3>The Idea of the People-First Approach while executing CRM projects</h3><p>The focus of each project should range <strong>from people (</strong><em>often referred to as “providers”)</em> <strong>to people (</strong><em>the “stakeholders”)</em>. Therefore, technology succeeds only when the people who use it are considered the main vectors of the project — meaning they should be understood, involved, and enabled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*1_WRfC16jqogOi-96o86mw.png" /></figure><p>Especially with CRM projects, technology plays a more central role and affects multiple teams–Sales, Marketing, Customer Success, Finance, and Support. If people don’t have a common understanding of goals and processes, the CRM becomes fragmented, regardless of how well it’s configured.</p><p>Configurations based solely on documentation can quickly become impractical. When teams collaborate instead of pushing requests through tickets, misunderstandings are reduced and decisions are quicker.</p><blockquote>Users generally don’t resist technology — they resist <strong>unclear and disruptive change</strong>. This is very well-known in the context of project management, but unfortunately, it is often poorly implemented.</blockquote><h4>Change management strategy to make adoption more natural</h4><p>Technological transformations and innovative projects need to have a bigger scope, including the stakeholders. If the project scoping and change management are not taken seriously, the projects fail or remain as shelved projects, resulting in cost ineffectiveness and demotivated teams.</p><p>Change management is critical for minimizing project risks. Even larger organizations often fail to implement change management as part of comprehensive project management.</p><p>Here are some examples that indicate a lack of preparation:</p><p><strong>“We rolled out the new CRM feature… and discovered the training plan still says <em>‘TBD’.</em>”</strong></p><p><strong>“Our change management strategy was basically: <em>‘Everyone will just… figure it out, right?’</em>”</strong></p><p><strong>“We introduced the new system on Monday. By Tuesday, the most-used feature was the <em>panic button.</em>” </strong>😅</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*5IbTsT3oXhNybW13waLMxQ.png" /></figure><p>As you may have already identified, poor scoping and preparation are one of the primary reasons for project failures.</p><h3>What Does Change Management Involve and How Can Organizations Act?</h3><p>The speed at which digital innovation is happening forces organizations to change and adapt to the new times. Changes involve adapting to new processes, acquiring new tools, reforming legacy systems, keeping up with <em>the AI expectations to align with the competitive needs, and enabling</em> successful marketing, sales, support, and finance teams.</p><p>In this scenario, all we need to do is prepare people to be ready and willing to adopt the changes. Therefore, change management should be systematic and well-planned, ensuring a smooth transition towards the organization’s goals.</p><p>Let’s now look at some <strong><em>suggestions and action points</em></strong> that apply to projects of all sizes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/395/1*20oxd4EbgrN7lavaa-bOiQ.png" /></figure><ul><li><strong>Defining the why?</strong> — This motivation should be the center of every communication with the involved stakeholders, so that they are well-prepared and ready to embrace the upcoming changes.</li></ul><blockquote>“If you want to go fast, go alone; if you want to go far, go together.”</blockquote><ul><li><strong>People and Teams </strong>— Ensure the experts from every team are consulted and informed about the project objectives and related changes. Utilize the famous frameworks like <a href="https://en.wikipedia.org/wiki/Responsibility_assignment_matrix">RACI </a>to ensure that each group of stakeholders is placed in the correct quadrants.</li><li><strong>Timeframe </strong>— Allow sufficient time for implementation. Consider the crucial tasks, such as data migration, user onboarding, end-user training, and comprehensive change management.<br>Recognize that adding more people doesn’t necessarily lead to faster progress. <em>Give designated individuals the required time and expertise without rushing through the process.</em></li><li><strong>Motivation &amp; Communication </strong>— Leadership teams should be the first to adopt and motivate the other internal teams. Ensure communication occurs at various stages of the project across multiple communication channels, so that all involved stakeholders are well-informed, allowing further communication to flow top-down to their respective teams.</li></ul><blockquote>“if everything is a priority, nothing is a priority”.</blockquote><ul><li><strong>Prioritization &amp; Meeting Expectations</strong> — Prioritization is key in agile projects. This helps align with project delivery expectations.</li><li><strong>Celebrate &amp; Acknowledge</strong> — Celebrating small victories keeps teams motivated and shines a light on their creativity. That can be team gatherings, cakes, or gift cards; what matters is celebrating and acknowledging the moments of hard work.</li></ul><p>These ideas present a crucial plan that places people as the primary focus. Follow these action points and contribute to impactful change management that focuses on real people, rather than merely documenting processes.</p><h3>Summary</h3><p>A project is always done <em>by</em> people and <em>for</em> people. <br>Especially complex CRM projects succeed not because the system is powerful, but because <strong>people are aligned, heard, and empowered to use it well. ✨</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2b302c90991" width="1" height="1" alt=""><hr><p><a href="https://medium.com/salesforce-business-analysts/mindsets-for-complex-crm-projects-e2b302c90991">Mindsets for complex CRM projects</a> was originally published in <a href="https://medium.com/salesforce-business-analysts">Salesforce Business Analysts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Onboarding Playbooks for SaaS Businesses: What Works, What Fails, and Why]]></title>
            <link>https://medium.com/agileinsider/onboarding-playbooks-for-saas-businesses-what-works-what-fails-and-why-0f8dd33a0bd2?source=rss-886086c8327f------2</link>
            <guid isPermaLink="false">https://medium.com/p/0f8dd33a0bd2</guid>
            <category><![CDATA[crm]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[saas-onboarding]]></category>
            <category><![CDATA[user-onboarding]]></category>
            <dc:creator><![CDATA[Gayathri Govindaraju]]></dc:creator>
            <pubDate>Fri, 26 Sep 2025 11:31:21 GMT</pubDate>
            <atom:updated>2025-09-26T11:31:21.773Z</atom:updated>
            <content:encoded><![CDATA[<p>In the world of SaaS, a customer’s first 30 days can make or break their long-term relationship with your product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*hyUvm4DYI74qzmNJwSCobA.png" /></figure><p>An effective onboarding process doesn’t just teach users how to click through features — it ensures they understand the <em>value</em> your product delivers. Yet, many SaaS companies still get onboarding wrong.</p><p>Let’s break down and assess what strategies are achieving results, which ones are falling short, and why. Understanding these elements will empower us to make informed decisions and drive success forward.</p><h3><strong>Onboarding: Why It Matters More Than Ever</strong></h3><p>Customer acquisition costs are rising, and competition is fierce. Switching costs, on the other hand, are lower than ever. If customers do not find value quickly, they are likely to churn.</p><p>A well-organized onboarding playbook speeds up time-to-value (TTV), decreases churn, and lays the groundwork for expansion revenue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*Bx87NQIm1Kz7zpEgek1E1A.png" /></figure><h3><strong>Exploring Effective Approaches to SaaS Onboarding</strong></h3><h4>1. Value-driven First Experience</h4><ul><li>Help users toward their “AHA” moment quickly.</li></ul><blockquote><strong><em>For example, <br></em></strong>You recognize the value of <strong><em>Dropbox </em></strong>when you successfully upload your first file. <br><strong><em>Slack </em></strong>demonstrates its real worth the moment you send your first message, invite a coworker, or quickly find a relevant channel.</blockquote><ul><li><strong>Why it works:</strong> Users immediately see the benefit of the product and feel a <strong><em>sense of accomplishment.</em></strong></li></ul><h4>2. Personalized Pathways</h4><ul><li>Use customer data (role, company size, use case) to<strong><em> tailor onboarding </em></strong>steps.</li><li><strong>Why it works:</strong> Personalization helps to <strong><em>reduce cognitive load</em></strong> by ensuring that users are only presented with information that is relevant to them. This targeted approach keeps users engaged.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*19ESA7h1K9_6pCv4FVufZQ.png" /></figure><h4>3. Multi-Channel Engagement</h4><ul><li>Combine in-app guides, tailored emails, and human touch (CSM check-ins) to craft a <strong><em>powerful, layered onboarding experience</em></strong> that ensures your customers thrive.</li><li><strong>Why it works: </strong>Customers engage with content in various ways. <strong><em>Some prefer to explore independently, while others require a little push.</em></strong></li></ul><h4>4. Definitive Milestones and Strategic Playbooks</h4><ul><li>Establish clear milestones (for example, “Invite 5 team members within 7 days”) and track the progress through your CRM. <br>This approach will help you monitor the milestones effectively!</li><li><strong>Why it works:</strong> Both the customer and customer success teams understand the progress clearly.</li></ul><h3>What Usually Goes Wrong in SaaS Onboarding</h3><h4>1. Over-Engineering the Product with Excessive Features</h4><ul><li>Introducing users to an overwhelming array of features right from the start.</li><li><strong>Why it fails:</strong> When users are presented with too many options at once, they can quickly feel confused and frustrated, which often leads to disengagement. <br>Instead, focusing on the core functionality allows customers to grasp the product’s primary value. This empowers users to build familiarity, ensuring they recognize the product’s value.</li></ul><h4>2. One-Size-Fits-All</h4><ul><li>Offering the same experience for both solopreneurs and enterprise teams with 500 employees.</li><li><strong>Why it fails:</strong> Different users have different jobs-to-be-done; a generic flow rarely satisfies their needs.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*k8nqayP6qwUiUg2nBY1fyg.png" /></figure><h4>3. Neglecting Human Touch</h4><ul><li>Relying solely on automation or self-serve tutorials.</li><li><strong>Why it fails:</strong> Complex or high-value customers often need a guided approach. <br>When they don’t receive the support they require, it can lead to frustration and increase the risk of churn. It’s essential to blend automation with personal interactions, providing the compassionate guidance that helps customers feel valued and supported on their journey.</li></ul><h4>4. Not Measuring Engagement</h4><ul><li>Running onboarding in the dark without tracking.</li><li><strong>Why it fails:</strong> Without key metrics like <strong><em>activation rate or time-to-value</em></strong>, you miss the opportunity to scale. <br>Focusing on these engagement milestones empowers you to make informed decisions, fosters a culture of continuous improvement, and ensures that every new member feels welcomed, valued, and ready to thrive.</li></ul><h3>Building Your Onboarding Playbook</h3><blockquote><strong>Iterate &amp; Improve:<br></strong>Onboarding is never “done.”<br>Treat onboarding as an evolving product. Regularly review metrics, feedback, and user behavior to refine the process continuously.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*V75fRxaWYnBtgAxQ25AmvQ.png" /></figure><p>Here’s a simple framework to start:</p><ol><li><strong>Map the Customer Journey:</strong> <br>Identify and outline critical steps from sign-up to the first significant value realization. Create a visual mapping for clarity.</li><li><strong>Set Clear Goals and Outcomes:</strong><br>Identify key performance indicators (KPIs) that will measure success effectively.</li><li><strong>Design Personalized Paths:</strong><br>Segment users by role, company size, or use case to create tailored onboarding flows. Develop specific content that resonates with each segment’s unique needs.</li><li><strong>Create Engaging Content:</strong><br>Utilize diverse content formats (videos, infographics, articles) that are easily digestible and guide users through an engaging onboarding.</li><li><strong>Blend Automation &amp; Human Touch:<br></strong>Use in-app prompts and automated emails for straightforward tasks, while deploying CSMs for complex accounts to provide personalized assistance.</li><li><strong>Define Metrics &amp; Feedback Loops:</strong><br>Track activation rates, churn, and overall user engagement. Conduct regular surveys and feedback sessions to gain insights into user experiences and areas for improvement.</li><li><strong>Celebrate Milestones:</strong><br>Recognize and reward users for achieving specific milestones during onboarding. This could be in the form of certifications, badges, or incentives, reinforcing their sense of progress.</li><li><strong>Encourage Community Building:</strong><br>Foster forums, user groups, or webinars where users can connect, share experiences, and learn from each other.</li></ol><h3>Final Thoughts</h3><p>Great onboarding is about delivering value, not providing more comprehensive, user-focused, and adaptable features. It’s about making the customer successful in <em>their</em> context. When SaaS companies nail onboarding, they don’t just reduce churn — they create loyal advocates who drive growth.</p><p>So, ask yourself: <em>Does your onboarding help customers unlock value in the first 30 days, or does it overwhelm and confuse them?</em> The answer may determine your next renewal rate. 😉</p><p>If you’re in SaaS, what’s the best (or worst) onboarding experience you’ve seen? Share in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0f8dd33a0bd2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/onboarding-playbooks-for-saas-businesses-what-works-what-fails-and-why-0f8dd33a0bd2">Onboarding Playbooks for SaaS Businesses: What Works, What Fails, and Why</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Achieving goals with Quarterly Roadmaps — A Comprehensive Guide]]></title>
            <link>https://medium.com/agileinsider/achieving-goals-with-quarterly-roadmaps-a-comprehensive-guide-77045827024e?source=rss-886086c8327f------2</link>
            <guid isPermaLink="false">https://medium.com/p/77045827024e</guid>
            <category><![CDATA[product-roadmap]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[okr]]></category>
            <category><![CDATA[product-strategy]]></category>
            <dc:creator><![CDATA[Gayathri Govindaraju]]></dc:creator>
            <pubDate>Sun, 01 Oct 2023 17:13:02 GMT</pubDate>
            <atom:updated>2023-10-01T17:13:02.608Z</atom:updated>
            <content:encoded><![CDATA[<h3>Achieving goals with Quarterly Roadmaps — A Comprehensive Guide</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*md3tppOhuz0zHtWm_1AhpA.jpeg" /></figure><p>A sustainable roadmap backed by right data is essential for making <em>informed product-related decisions</em>. In today’s scenario, most of the organizations have adopted modern agile methodologies to meet their customers’ needs and to stay ahead in the global competition.</p><p>This article explains the importance of having quarterly roadmaps along with some best practices to properly structure a long-term product roadmap and decide how you plan to execute your plan within the quarter.</p><h3>What is a quarterly roadmap?</h3><p>Quarter roadmaps are the product roadmaps that give an overview of your product development at least for a span of 3 months. This helps you to look beyond just <strong><em>the now and later stages</em></strong> by overcoming the uncertainties and obscurities about what you will build and how.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mFG24OkMMOSZwKQMZ6PnYw.jpeg" /></figure><p>This is a good way to connect with your practices during planning stages and refine them. Having well-planned futuristic roadmaps minimizes vagueness and further complexities. This helps you to illustrate the product direction, your target group of users, your stakeholders and where and how to market it further.</p><h3>Why is it important to have quarterly roadmaps?</h3><p>Quarterly roadmaps help the teams to focus on the product needs at a specific time. Business goals are usually measured based on various parameters like user retention, conversions, market expansion, etc… which involves a lot of iterations around building and testing. Having a quarterly plan helps better align product planning with the flow of product needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N6n1UWia1BovtOOR9dGluQ.jpeg" /></figure><p>This gives the product managers the ability to access various data sources and choose the right data-driven strategies to handle customer feedback and gain the right performance metrics. This is crucial both for developing sustainable products and having better processes in place.</p><h3><strong>Objectives and Key Results — OKRs </strong>🌱</h3><p><strong>Objectives &amp; Key Results (OKRs)</strong> are a notable way for measuring and setting the product market purpose. Combining OKRs with quarterly roadmaps is even great as it helps you to work in a more product-focused way.</p><p>This enables the product managers to take definitive initiatives and describe what specific activity the team is working to achieve a particular OKR. This inturn shows the importance of the OKR in the product roadmaps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2l-hBlZcAelPTxJaIS559Q.jpeg" /></figure><p>This way of clarity in working teams opens up for channels for clear communications, new thoughts &amp; strategies and product market perceptions. Mapping out all these initiatives, thoughts and perceptions on a quarterly roadmap helps the team get a visibility on what they are working on and what they are achieving by this. This also allows your team to fix problems in different possible ways and successfully achieve the objectives.</p><h3>What do quarterly roadmaps look like in reality? — A step-by step guide</h3><h4><strong>1. Do you have your OKRs ready for the quarter? </strong>📈</h4><p>Make sure your goals for the quarter are aligned well with your product goals and the overall organizational needs.</p><p>Company/ product goals change depending on the clients, market and other internal reasons. Be sure about what you want to achieve in this quarter and add only them in your quarterly roadmap. It is easy for new product managers to become over-ambitious — avoid that and strictly stick to the OKRs for the quarter.</p><h4><strong>2. Prioritize and align </strong>📝</h4><p>Start planning. Organize the ideas and prioritize them as defined initiatives. While prioritizing, discuss the initiatives among the team members and see if they are relevant and meet your objectives for the quarter.</p><p>See what customer problems you are going to solve. Take the help of <a href="https://www.productplan.com/learn/product-management-frameworks/">prioritization frameworks/ techniques like: RICE or Story Mapping</a>.</p><h4><strong>3. Identify the bottlenecks and possible ways to solve </strong>🔐</h4><p>Identify the resources that you have and get a high-level estimate. This helps to avoid misalignments and mis-communications in the later stages. Choose between top-down or bottom-up approaches to have more realistic estimates.</p><p>Understand the dependencies and expectations between development, product and commercial teams.</p><h4><strong>4. Involve your stakeholders in the communication </strong>💬 <strong>&amp; create a high-level roadmap</strong></h4><p>Create different versions of scenario-based roadmaps with clear priorities and share them with your stakeholders. This is a great way to ensure open communications that are aligned with the team’s expectations and product goals. Get as much clarity as possible in this stage.</p><h3><strong>Things you should be aware while creating your quarterly roadmaps</strong></h3><h4><strong><em>Being flexible can make you more adaptable for changes</em></strong></h4><p>A quarter is really a good amount of time to shift priorities, change goals and to get in new customer requests. Therefore, it is important to be flexible even though a quarterly roadmap is a solid plan that shows further development towards the set objectives.</p><h4><strong><em>Ensure that everyone are on the same page</em></strong></h4><p>A project is a combined work of various teams. It does not mean that everyone else has to wait until your team finishes your work. Then it is a waste of time. Right? Use the quarterly roadmap to share your priorities and progress, tasks and assignments, releases and feedback. This will eventually become a well-integrated productivity tool.</p><h4><strong>Use frameworks wherever needed instead of building everything by yourself</strong></h4><p>For Example, you can build your product roadmaps using many tools like spreadsheets, powerpoint, etc…, but they are NOT dedicated for this purpose. Means, they lack the key features that a proper product tool/ framework is built for. In addition, it takes a really long time to build roadmaps when you use the wrong tools.</p><p>Choose the tools that are fast, visually appealing, easily integrated and shareable across your stakeholders. Basically, just right for your purpose.</p><p><strong>Quarterly roadmaps </strong>can be a powerful tool for your organization to achieve the strategic goals efficiently. They improve clarity in your goal alignments, communications and make you adaptable and ready for changes. I hope you can harness the full potential of quarterly roadmaps to drive your organization towards success 🏆.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77045827024e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/achieving-goals-with-quarterly-roadmaps-a-comprehensive-guide-77045827024e">Achieving goals with Quarterly Roadmaps — A Comprehensive Guide</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking Growth: The Power of Product-Led Growth (PLG) Strategy for Product Managers]]></title>
            <link>https://medium.com/agileinsider/unlocking-growth-the-power-of-product-led-growth-plg-strategy-for-product-managers-4164112d3544?source=rss-886086c8327f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4164112d3544</guid>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[growth-strategy]]></category>
            <category><![CDATA[product-led-growth]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[customer-acquisition]]></category>
            <dc:creator><![CDATA[Gayathri Govindaraju]]></dc:creator>
            <pubDate>Tue, 23 May 2023 18:14:04 GMT</pubDate>
            <atom:updated>2023-05-23T18:14:04.614Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*A3SOYR_wcqNK1CLF2sZXzQ.png" /></figure><p>In today’s competitive market, where customers have numerous choices, <strong><em>product-led growth (PLG)</em></strong> has emerged as a game-changing strategy for product managers.</p><blockquote>PLG shifts the focus from traditional marketing tactics to building a product that speaks for itself, captivates users, and drives growth organically.</blockquote><p>As a <em>product manager</em>, understanding and harnessing the power of PLG can be the key to unlocking rapid customer acquisition and retention. <br>In this blog post, we will delve into the core concepts of PLG, explore its benefits, and provide practical insights on how product managers can successfully implement this strategy to achieve remarkable results. Let’s dive in!</p><p><strong>Product-led growth (PLG)</strong> is a marketing and growth strategy that has gained immense popularity in recent years.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*-P_XY_TPK09aPL4cYhEIHQ.png" /></figure><p>It’s a customer-centric approach that focuses on delivering a product that can sell itself. As a product manager, you can leverage PLG to drive growth and increase customer acquisition. Let’s explore what PLG is, its benefits, and how you can implement it as a product manager.</p><h3>What is Product-Led Growth (PLG)?</h3><p><em>Product-Led Growth</em> is a growth strategy that focuses on building a product that is so valuable and intuitive that users can’t help but recommend it to others. PLG companies prioritize delivering an exceptional user experience that helps users solve their problems quickly and easily. The goal is to get users to rely on the product to such an extent that they become loyal customers who spread the word about the product to their network.</p><h3>Benefits of Product-Led Growth Strategy</h3><p>There are several benefits of using a product-led growth strategy along with conventional product management practices, including:</p><ol><li><strong>Higher Customer Retention:</strong> A product that is easy to use and delivers value to users will naturally result in higher customer retention.</li><li><strong>Increased Customer Acquisition:</strong> When users love a product, they are more likely to recommend it to others, resulting in increased customer acquisition.</li><li><strong>Better Conversion Rates:</strong> If a product is intuitive and delivers value, users are more likely to convert to paying customers.</li><li><strong>Faster Time to Value: </strong>By focusing on delivering value through the product, users can experience the benefits more quickly, leading to faster time to value.</li></ol><h3>Implementing a Product-Led Growth Strategy</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*jyNPxL9in_uJqCqnNuzNjw.png" /></figure><p>As a product manager, you can implement a <em>product-led growth</em> strategy by following these practices:</p><ol><li><strong>Focus on User Experience: </strong>User experience is critical to PLG. Focus on making your product intuitive and easy to use, and continuously iterate based on user feedback.</li><li><strong>Deliver Value Quickly: </strong>PLG is all about delivering value quickly. Identify the core value proposition of your product and ensure that users experience it as soon as possible.</li><li><strong>Leverage Virality: </strong>Encourage users to share your product with others by building in virality. Make it easy for users to invite others to use the product and incentivize them for doing so.</li><li><strong>Emphasize Free Trials: </strong>Offer free trials or freemium models that allow users to experience the product before committing to a purchase.</li><li><strong>Measure and Optimize: </strong>Measure the success of your PLG strategy through metrics like customer acquisition cost (CAC), customer lifetime value (CLTV), and conversion rates. Use these metrics to continuously optimize your PLG strategy.</li></ol><blockquote>Product-led growth is a powerful growth strategy that can help product managers increase customer acquisition and retention.</blockquote><p>By focusing on user experience, delivering value quickly, leveraging virality, emphasizing free trials, and measuring and optimizing, product managers can create a product that sells itself. By implementing a PLG strategy, you can create a product that delights customers and drives growth for your business.</p><p>Embracing a product-led growth strategy unlocks product’s true potential. It can be a game-changer for product managers seeking to drive customer acquisition and retention. Prioritizing and integrating the above mentioned implementation strategies creates a product that can sell itself.</p><p>The <em>customer-centric approach</em> of PLG empowers products, creates a loyal user base that becomes brand advocates. It eventually propels businesses to new heights, delights customers and achieves sustainable growth.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4164112d3544" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/unlocking-growth-the-power-of-product-led-growth-plg-strategy-for-product-managers-4164112d3544">Unlocking Growth: The Power of Product-Led Growth (PLG) Strategy for Product Managers</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Things I’ve learnt as a Product Manager]]></title>
            <link>https://medium.com/agileinsider/5-things-ive-learnt-as-a-product-manager-1a574ba3ca12?source=rss-886086c8327f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a574ba3ca12</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[lifestyle]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Gayathri Govindaraju]]></dc:creator>
            <pubDate>Sat, 18 Feb 2023 18:18:34 GMT</pubDate>
            <atom:updated>2023-02-18T18:18:34.211Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nmZAQpP96OkS6fat-RNahg.jpeg" /></figure><p>Product management is a challenging and rewarding career path that requires a unique set of skills and knowledge. However, getting into product management can be a daunting task, especially if you’re new to the field.</p><p>In this blog post, I will share some valuable insights and lessons that I’ve learnt as a product manager.</p><h3><strong>Communication is Key </strong>💬</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H2qihtQloaNKbzPphJLfTw.jpeg" /></figure><p>Product management is all about communication. It is important to be able to clearly communicate with a wide range of stakeholders, including developers, designers, executives, customers, and team members. Communication skills are essential to understanding the needs of your team and your customers, as well as conveying your ideas effectively.</p><h3>Data is Your Best Friend 📈</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lSeQ-u4Ox4Dni4Bv66fo5Q.jpeg" /></figure><p>Data is a vital part of product management. You need to be able to analyze data to make informed decisions about your product. It’s important to be able to understand what data to collect, how to analyze it, and how to use it to make informed decisions.</p><p>Efficient use of data helps you to understand the user needs and demands. You can therefore make great improvements to your product.</p><h3>The Importance of Prioritization 📝</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jl3IyFW1mZokvBXurAAqLA.jpeg" /></figure><p>One of the biggest challenges in product management is prioritization. You need to be able to prioritize features, bugs, and issues based on their impact and urgency. It’s important to have a clear understanding of what is most important to your customers and your business, so you can focus on delivering value.</p><p>Especially in startups, the priorities change more quickly. As a product manager, it is critical to understand the business value to ensure sustainable product success.</p><h3>It’s Okay to Say “No” 👩‍💻</h3><p>As a product manager, you will be faced with a lot of requests and demands. It’s important to remember that you can’t say “yes” to everything. Saying “no” is an essential skill in product management. You need to be able to prioritize and make tough decisions, even if it means saying “no” to stakeholders.</p><p>This might bring some resistance among your teammates and stakeholders. Clear the clutter by prioritizing the product goals. Put your viewpoints in a logical way and explain the challenges.</p><h3>It’s a Continuous Learning Process</h3><p>Product management is a constantly evolving field, and there is always something new to learn. It’s important to stay up-to-date on industry trends, best practices, and new technologies. Product management requires a growth mindset and a willingness to learn and adapt to new challenges.</p><p>Product management is an exciting and dynamic career path that requires a unique set of skills and knowledge. By keeping these insights in mind, you’ll be better prepared for the challenges and rewards of the field. Remember to communicate effectively, use data efficiently, prioritize wisely, be willing to say “no,” and continue to learn and grow.</p><p>I hope you resonated with most of the points mentioned in the article, if you have already worked in product management for sometime.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a574ba3ca12" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/5-things-ive-learnt-as-a-product-manager-1a574ba3ca12">5 Things I’ve learnt as a Product Manager</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Customer Feedback Loops — The Biggest Contributor to A Successful Product]]></title>
            <link>https://medium.com/agileinsider/customer-feedback-loops-the-biggest-contributor-to-a-successful-product-316444902e1?source=rss-886086c8327f------2</link>
            <guid isPermaLink="false">https://medium.com/p/316444902e1</guid>
            <category><![CDATA[feedback-loop]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[communications-strategy]]></category>
            <category><![CDATA[product-marketing]]></category>
            <dc:creator><![CDATA[Gayathri Govindaraju]]></dc:creator>
            <pubDate>Wed, 07 Dec 2022 15:18:23 GMT</pubDate>
            <atom:updated>2022-12-07T15:18:23.120Z</atom:updated>
            <content:encoded><![CDATA[<h3>Customer Feedback Loops — The Biggest Contributor to A Successful Product</h3><p>When a product is released into the market, success depends on how well the product solves the users’ pain points.</p><p>The product manager’s responsibility is to improve the product by identifying such use cases. Integrating continuous customer feedback loops is very powerful for understanding real-time user experiences and quickly improving your product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*DGWAzsj9USUhUHUPgxIxjA.png" /></figure><h3>Why is customer feedback looping so critical?</h3><blockquote>Allowing customers to share feedback makes them feel that they are heard and valued.</blockquote><p>A customer feedback loop is a process that allows the product teams to track the customers’ experiences. Having built-in customer feedback loops within the product makes the overall tracking process simpler, faster, and inexpensive. The customer success and support teams can suggest quick tips for the user’s issues more efficiently and understand the churn rate in a better way. The parameters like–reasons for cancellation, feedback comments, and help center ratings, are some of the important ones.</p><p>Information about known product limitations and frequently asked questions should be documented and made available to the users in dedicated places like–the help center, tutorials, and so on.</p><p>Track all this abstract information in a concrete and scalable way.</p><ol><li><strong>Customer Satisfaction Score (CSAT)</strong>–tells you how happy your customers are with the overall performance of your product.</li><li><strong>Customer Effort Score (CES)</strong>–helps you to identify how easy it is for your customers to navigate within your product/ application. This mainly focuses on ease of use.</li><li><strong>Net Promoter Score (NPS)</strong>–is a survey that gathers information about how the customers feel while using your product. Depending on this score, you can divide the users into 3 categories: <em>Detractors, Passives, and Promotors</em>.</li></ol><p><em>Promotors</em> are the users who are highly satisfied with your product and are willing to be your beta testers, contribute to the improvements and are willing to recommend and promote your product.</p><blockquote>A smart product manager knows how to leverage their promotors in the right way and foster overall product success.</blockquote><h3>How to implement the customer feedback loop process?</h3><p>Setting up a process for looping customer feedback is critical. Here are some useful steps that help you to get started.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*Jo2-ViIzU8eqDSqw-AFNwg.png" /></figure><ol><li><strong>Track the information</strong><br>Gather all the required data and turn it into important and scalable information.</li><li><strong>Learn from the pattern</strong><br>Make the best use of the information to answer imperative questions that can give you explicit performance indices.</li><li><strong>Get your action points ready</strong><br>Let all this scalable information contribute to your actions. Collaborate with the required stakeholders and sort out the challenges and complexities.</li></ol><p>This way, you turn abstract insights into measurable actions. Closing the customer feedback loop in this way improves the product, and increases customer satisfaction and customer retention.</p><h3>How to implement the customer feedback loop process?</h3><ul><li>→ Acting on the feedback</li><li>→ Achieving the desired improvement in the product</li><li>→ Communicating the updates and the next steps to your users</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*CrEEIsMuxCib3eBJPk33TA.png" /></figure><blockquote>Processing feedback loops efficiently is a perfect win-win instance both for the customer as well as for the product itself.</blockquote><p>The product managers get to collect the feedback and show their loyalty while the customer feels that he is heard and taken care of.</p><h3>Some best practices</h3><ol><li>Accept that your product comes with certain known limitations. They need to be explicitly documented. This saves a lot of time for everyone.</li><li>When a certain reported bug is fixed, let the world know that it is fixed. Better reach out to the person who reported the bug and inform them that it is fixed. Even better is to get confirmation that it is working as it should.</li><li><strong><em>The user usually comes with a concern and rarely with a bug. </em></strong><em><br></em>He is not a product specialist. Just explain to him the way how it has to be done on the platform. Provide necessary information and direct him to relevant help center articles or tutorials.</li><li>Feedback looping has to be an ongoing process throughout the product life cycle.</li><li><strong><em>Product marketing is a vital part.</em></strong> <br>Send out product updates frequently. Let the users know what features to expect. Not everyone needs all the information. Segregate your users and channel the information properly.</li></ol><blockquote>Don’t find customers for your products. Find products for your customers, says Seth Godin</blockquote><p>Do you have more techniques for implementing customer feedback loops? Share them in the comments along with your thoughts and best practices.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=316444902e1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/customer-feedback-loops-the-biggest-contributor-to-a-successful-product-316444902e1">Customer Feedback Loops — The Biggest Contributor to A Successful Product</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Resolving Conflicts as a Product Manager]]></title>
            <link>https://medium.com/agileinsider/resolving-conflicts-as-a-product-manager-6742502fbf7?source=rss-886086c8327f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6742502fbf7</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[corporate-team-building]]></category>
            <category><![CDATA[conflict-management]]></category>
            <dc:creator><![CDATA[Gayathri Govindaraju]]></dc:creator>
            <pubDate>Sat, 12 Nov 2022 20:13:19 GMT</pubDate>
            <atom:updated>2022-11-12T20:13:19.449Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IoLvXckWh78ADKVMiWZ4Sw.jpeg" /></figure><p>Product managers have to always deal with disagreements and arguments while tracking feedback and cross-functional requests from various teams. They could be feature specific, design related or timelines dependent, a product manager should manage all of them by focusing on your product and its priorities.</p><p>It is quite possible to get into conflicts, disagreements about product strategy, timelines and so on.</p><p>Surrounded by all these, how would you keep up your calm and seamlessly work towards your product goals?</p><p>In this article, I will give you <strong><em>5 practical ways to resolve conflict situations </em></strong>without kicking down the ladders.</p><h4>1. Building trust</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d7JM50Azwd0wGM3-F9ab9A.gif" /></figure><p>A product manager has to interact with various stakeholders with different kinds of backgrounds and goals. Because of different product interests, it could be a challenge to make them clearly understand your intentions and strategies. The conflicts that arise in such settings can be resolved by establishing trust between parties.</p><blockquote>Be a good and patient listener.</blockquote><p>Don’t be biased on your viewpoints or judgemental about others’ thoughts.</p><p>Try to give constructive feedback. Try to make as many 1–to–1 conversations as possible. This way, you can empathize with each other and get into common agreements quickly.</p><p>Once you develop trust, you can handle disagreements and conflicts in a more subtle way.</p><h4>2. Pair viewpoints with context and illustrations</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-TzAHnTOOQwS9ltZru9DYw.jpeg" /></figure><p>While you put your views forward, always back them up with examples or relevant use cases. This helps your stakeholders tune-in.</p><p>While making an action plan, understand that your stakeholders are from different backgrounds and might have different interests. Expect that their questions can go out of your scope. Try to embrace those questions instead of feeling nuked.</p><p>Give them the context and why it is important. Keep important stakeholders in the communication loop. Share analytics related to the feature performance. Frequently share information about customer interviews, feedback etc.. This makes them feel included.</p><h4>3. Appreciate feedback</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pouka9AxPdG0O_y7tdLJWA.jpeg" /></figure><p>Receiving feedback needs a stable and calm mind. Heated arguments or retaliating at one another can get you nowhere. It can only worsen the situation.</p><p>See where the other person is coming from. Get a clarity on what specific feature the person is unsatisfied with. If fixing it takes time, agree upon a specific deadline. Outline the action items and circulate among the involved stakeholders.</p><p>Invite a group of people to test it. Propose your ways of A/B testing which makes the feature further better. Show your affinity towards the product, so that everybody will understand that whatever you are doing is certainly for the overall betterment.</p><h4>4. Efficient meetings</h4><p>We tend to hover over the same things during our meetings. Looking at a bigger picture of the issue could fix this. Try to get a process in place to address and track bigger issues. Focus on the root cause. This helps to build better systems in a longer run.</p><h4>5. Bonus — Turn down your discussion before it turns into an ego clash</h4><p>It is quite a human tendency to get into defensive mode when someone points out flaws. It is not always easy to confess our faults. Ask for their explicit opinion about the shortcomings.</p><p>Having internal retrospectives help to quickly resolve things internally. This will also make your approaches and processes better every next time.</p><p>Working with people with diverse backgrounds towards common product goals is not an easy task. On this journey, it is quite common to meet conflicts. Learning to resolve them in the right ways helps you flourish both professionally and personally.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6742502fbf7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/resolving-conflicts-as-a-product-manager-6742502fbf7">Resolving Conflicts as a Product Manager</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Does Agile work for marketers?]]></title>
            <link>https://medium.com/agileinsider/does-agile-work-for-marketers-143b613a376?source=rss-886086c8327f------2</link>
            <guid isPermaLink="false">https://medium.com/p/143b613a376</guid>
            <category><![CDATA[agile-marketing]]></category>
            <category><![CDATA[agile-for-marketing]]></category>
            <category><![CDATA[agile-marketing-scrum]]></category>
            <category><![CDATA[product-marketing-manager]]></category>
            <category><![CDATA[agile-marketing-teams]]></category>
            <dc:creator><![CDATA[Gayathri Govindaraju]]></dc:creator>
            <pubDate>Fri, 10 Jun 2022 12:27:25 GMT</pubDate>
            <atom:updated>2022-06-10T12:27:25.819Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PHIZj4LQB0yPA2fEs7i7YA.jpeg" /></figure><p>When we talk about agile, it has been mostly considered as a buzzword among IT teams.</p><p><strong><em>How does agile methodologies help teams in general?</em></strong></p><blockquote>“Perfection is not attainable, but if we chase perfection we can catch excellence.”<br>– Vince Lombardi</blockquote><p>👆 This is exactly what integrating Agile practices can do to your marketing teams.</p><p>Following Agile methodologies helps to break down a complex project into smaller increments, gathering continuous feedback, and makes your workflow flexible so that you can adapt to changes quickly.</p><p>Not just with IT teams, with time, Agile has been significantly successful within many other teams as well, and marketing is not an exception.</p><p>Since the past decade, the word <em>Agile Marketing</em> has been gaining its importance. In this article, we will be looking at different perspectives of Agile marketing, important takeaways and overall benefits of <em>Agile empowered Marketing</em>.</p><h3>Is “Agile Marketing’’, just a buzzword?</h3><blockquote>A collaborative report published by AgileSherpas &amp; Forrester Research for the year 2021 indicated that more than 50% of marketers embraced Agile practices in their work — <a href="https://www.agilesherpas.com/4th-annual-state-of-agile-marketing-report">Agile marketing report 2021</a>.</blockquote><p><a href="https://www.agilesherpas.com/4th-annual-state-of-agile-marketing-report">4th Annual State of Agile Marketing Report</a></p><p>Integrating Agile practices with conventional marketing helps to create self-organised cross-functional teams that can effectively work with feedback driven iterations. This helps to improve the overall strategic vision of your team by getting your short term and long term goals in place.</p><h3>It is time to unleash the benefits of Agile marketing</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YA2eSWx-T90QgU3k227EMA.jpeg" /></figure><ul><li>Generic marketing teams usually work with detailed plans. To reap greater benefits from agile practices, encourage your team to focus on frequent releases</li><li>Marketing teams’ work model is data driven and it usually works hand-in-hand with the other teams like: customer success, sales, tech, and so on. In addition to using the power of market data, trends and statistics, agile gives you the scope to consciously experiment with certain parameters.</li><li>Agile marketing gives you the opportunity to understand your customers and their timely needs. This helps you to anticipate the forthcoming challenges. The readiness to accepting challenges indicates your commitment towards customer satisfaction.</li></ul><h3>5 takeaways from the Agile Marketing Manifesto</h3><p><a href="https://agilemarketingmanifesto.org/">Agile Marketing Manifesto</a> was created in 2012 to serve as a reference to the Agile best practices. It helps to guide the marketing teams that are consciously evolving towards Agile.</p><ol><li>Focus on customer needs instead of business processes.</li><li>Customer satisfaction lies in delivering early value through your product.</li><li>Consider logical &amp; statistical experimenting over rigid conventional practices.</li><li>Unleash the benefits of feedback-driven iterations.</li><li>Flexible work approach helps to quickly respond to changes rather than following strict plans.</li></ol><h3>Let’s see the benefits of Agile empowered marketing</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TnibgNQeydwK-1yZe6w_fQ.jpeg" /></figure><p>Implementing Agile best practices should be done smartly. Especially in marketing, it should not be done for its own sake or just for fascination for the new buzz word. Think agile as a solution to a particular business challenge, or a way to achieve a product goal. Only then, you can reap the benefits of Agile marketing in practice.</p><p>Here are some important advantages of Agile marketing:</p><ul><li><strong>High Productivity with early value</strong></li></ul><p>Delivering early value is always an undeniable benefit of Agile marketing. This is achieved through improving overall structure, planning and execution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wWPZ4BVD9UBQ5W6uDrZklQ.jpeg" /></figure><p>Instead of handling and operating bigger teams with dedicated job titles, Agile encourages smaller cross-functional, yet effective teams. Working in smaller teams helps to make faster iterations without delays due to dependencies.</p><p>This way of structured work model contributes to significant productivity.</p><ul><li><strong>Better communication &amp; collaboration</strong></li></ul><p>Smaller cross-functional teams handle communication effectively. Agile marketing focuses on transparent work flows and communications. Visual communication encourages collaboration between individuals and teams. Use of <em>Kanban boards</em> is a perfect example of transparent and collaborative communication.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kjGsTserOgHNEY6NgeKZMw.jpeg" /></figure><p>Transparency in communication makes the workflow predictable and conveys the team’s accountability. This makes the teams more responsible and helps them to have better relationships within the team and with the customers.</p><ul><li><strong>Flexibility &amp; Readiness</strong></li></ul><p>Agile marketing guards the businesses by enabling them to work flexibly. Agile marketing teams work on an iterative basis instead of just following the given marketing plan.</p><p>Having an annual plan ready for the whole year would not help the organisations because of the changing customer expectations and market conditions. This can never make you ready for the real-time business challenges and it rather gives high disappointment among the marketing teams.</p><p>In Agile methodology, teams are allowed to work for a goal by having flexibility to change their plans and workflow based on data and customer feedback.</p><ul><li><strong>Logical and Statistical workflow</strong></li></ul><p>One-time planning for the whole project is not suitable for our present day’s scenario. The plans should go according to the needs of customer. Agile emphasises experimentation. It means, marketing teams should make data-driven marketing campaigns to make the success more measurable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dxnYA9bu6Gybn6XKlTjt-w.jpeg" /></figure><p>The Agile marketing teams should keep an eye on key metrics and monitor the process efficiency. Run A/B tests and measure results. This will eventually improve the quality of your campaigns and hence the results.</p><ul><li><strong>Makes businesses more competitive</strong></li></ul><p>Agile helps to operate marketing teams flexibly with a great speed. With the focus on the real-time challenge, the marketing campaigns become more targeted and prompt.</p><p>The data-driven actions ensure that the next step in planning contributes to continuous improvement and keep you up for the competition.</p><blockquote>What best practices would you implement in your marketing team to make it work the Agile way? Do you have more insights to optimise Agile for your marketing team to maximise success?</blockquote><p>Feel free to share your thoughts in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=143b613a376" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/does-agile-work-for-marketers-143b613a376">Does Agile work for marketers?</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Things To Avoid in Product Management]]></title>
            <link>https://medium.com/agileinsider/3-things-to-avoid-in-product-management-7c5e7fde271f?source=rss-886086c8327f------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c5e7fde271f</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[be-your-own-boss]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Gayathri Govindaraju]]></dc:creator>
            <pubDate>Tue, 29 Mar 2022 11:57:56 GMT</pubDate>
            <atom:updated>2022-03-29T11:57:56.747Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S6Lib4bYi2msRHXX027dog.jpeg" /></figure><p>The importance for a product manager role has been increasing as the need for more innovative products increases day-by-day. To be able to effectively execute product strategies, product managers need to upgrade themselves technologically according to everyday’s trends.</p><p>While making a product delivery, a product manager thinks from several viewpoints to —</p><ul><li>ensure that the product is solving the right customer challenge</li><li>ensure that the product is not over engineered or burdened with features</li><li>make the product as feasible as possible for any anticipated changes or upgrades</li></ul><p>Statistics say that most of the product managers today don’t have a professional degree in product management. Rather they earn the position through their knowledge and skills that they developed through their experience and constantly upgrading themselves through books, blogs, tech conferences &amp; networks etc…</p><p>A product manager always focuses on making the product successful and useful to all the stakeholders.</p><p>Nevertheless, it is not the case with all the product managers. Depending on their background and their previous work experience, they tend to go biassed while developing a product. How to get over that?</p><p>Further in this article, let’s see what are those 3 things that should be avoided in product management.</p><h3>1. Over emphasising on the product itself 🧐</h3><p>A product manager’s role is to make impressive products. It does not mean that you focus on the PRODUCT alone!</p><p>Before you do anything related to your product, you should be able to listen to the noise around and turn the noise into perspectives. <strong>Listen, listen &amp; listen!!</strong></p><p>No wonder that a product manager’s day is loaded with meetings. Learn from those meetings. Understand expectations from each stakeholder.</p><p>Gather information and record them as requirements. Assess the requirements and map them to different features towards execution. There may be many who use your product, but keep in mind who actually need your product the most.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nmZAQpP96OkS6fat-RNahg.jpeg" /></figure><p>Overloading a product with too much functionality will make your product more valuable than it’s price. And it will soon join the list of the <em>most underused products</em>.</p><blockquote><strong>Product Management is not about the PRODUCT. It is about the USERS</strong>. The challenges your product solves is more important than the futuristic features it has.</blockquote><p>Know your user first. Then you will understand what is needed and how to build a sustainable, useful and well-functioning product.</p><h3>2. Customer satisfaction is everything 🤝 🤝</h3><p>The user of your product becomes your customer. Satisfaction of your customer contributes to the success of your product.</p><p>I personally, ensure that there is a good feedback system in place in my product management life cycle as it solves many problems and improves the product on a whole.</p><p>But, a product manager should never go to an extreme of solving individual customer issues seriously. Focusing on one issue will make the product weigh heavy on one side and eventually become too tailored. This restricts the usage of your product as it suits just a smaller group of your customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r7h80PfYddmkq9hrhBDrWw.jpeg" /></figure><blockquote>A product manager should understand the overall persona of an ideal customer.</blockquote><p>When a new feature request or a change request is made by your customer, you should first thoroughly assess the requirement. Validate with your internal teams. Take their opinions. If you feel it is beneficial, make internal test groups to estimate the outcomes and then make a decision based on the incremental value.</p><h3>3. Forgetting the rule of “Be Your Own CEO” 👩‍💼</h3><p>There are great product managers out there who are talented and knowledgeable, but fail. Why?</p><p>Because not all the product managers remember the rule of “Being your own CEO”. Yes, an efficient product manager is often described as the CEO of his product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KYlFUWaia73oLOSzRZwOXw.jpeg" /></figure><p>A product manager should know the purpose, value, vision and drive of his product. This is his contribution to the overall growth and expansion of the company in multiple dimensions.</p><p>To be successful as a product manager, one should have necessary resources, know his responsibility, take the control to lead the product and communicate the progression across the organisation internally and to the external stakeholders.</p><p>If a product manager just does what is told and waits until someone instructs about something, it means that he lacks vision and motivation to drive the product growth. This takes the process nowhere and the organisation sees no outcome or revenue growth.</p><p>—</p><blockquote><strong>Don’t find customers for your products, find products for your customers</strong>, says Seth Godin.</blockquote><p>I absolutely believe in this. Without properly knowing your user group, it is impossible to launch a competitive and innovative product in the market.</p><p>—</p><p>The above mentioned 3 things mislead your efforts or take you nowhere in product management. An efficient product manager should avoid them to successfully build world-class products.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c5e7fde271f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/3-things-to-avoid-in-product-management-7c5e7fde271f">3 Things To Avoid in Product Management</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>