The Developer Advocate's Guide to Getting Buy-In ![rw-book-cover](https://res.cloudinary.com/theworstdev/image/upload/l_Gradient/l_text:Montserrat_64_black:The%20Developer%20Advocate's%20Guide%20to%20Getting%20Buy-In,c_fit,g_center,w_800,fl_cutter,fl_layer_apply/v1637893282/Background.png) [[3. Resources/Readwise/Full Document Contents/Articles/The Developer Advocate's Guide to Getting Buy-In|Full Document Contents]] ## Document Notes ## Summarize: This article discusses the concept of "buy-in" in the context of developer advocacy. Buy-in refers to the process of gaining support from decision-makers for proposed changes or ideas. For developer advocates, this means advocating for changes to a company's products and software based on feedback and friction experienced by developers in the community. The article emphasizes the importance of building trust, effective communication, empathy, patience, and persistence in the process of getting buy-in. Skills such as clear communication, relatable problem framing, and understanding the goals of stakeholders are crucial for success. The author shares tactics to initiate change, including collecting quantitative and qualitative data, recording user experiences, building desired outcomes, and aligning proposed changes with existing initiatives. The overall goal is to ensure that when seeking commitment from decision-makers, developer advocates have the right people on board who understand and champion the proposed changes. ## Bullet Points: - **Buy-in in Developer Advocacy**: - Developer advocates seek to advocate for changes to a company's products and software based on community feedback and friction experienced by developers. - Buy-in is the process of gaining support from decision-makers for proposed changes or ideas. - The act of getting buy-in involves building trust, effective communication, and creating champions for the proposed changes. - **Skills for Getting Buy-in**: - Communication: Clearly stating the problem, presenting solutions, and providing sufficient context and supporting information for informed decisions. - Empathy: Building relationships with stakeholders, understanding their goals and metrics, and showing how proposed changes can benefit them. - Patience: Acknowledging that change can be slow and being aware of product roadmaps and engineering timelines. - Persistence: Continuously seeking alternative approaches and reassessing the efficacy of proposed changes over time. - **Tactics for Initiating Change**: - Collecting Data: Gathering quantitative and qualitative data related to stakeholders' goals and the areas of change. - Recording Experiences: Using empathy to help others understand user frustration by documenting experiences with pain points. - Building Desired Outcomes: Creating prototypes or demonstrations to allow decision-makers to experience the benefits of proposed changes. - Look for Alignment: Finding opportunities to align proposed changes with existing plans or projects. - **Conclusion**: As developer advocates, it is essential to thoroughly understand the changes being proposed and provide compelling evidence for them, ensuring the right people are on board to champion and support these changes. ## Paraphrase: 1. One significant challenge for developer advocates is gaining "buy-in," which means obtaining support from decision-makers for proposed changes or ideas. This process involves building trust, effective communication, and having advocates who can champion the proposed changes. As developer advocates, their role is to advocate for changes to a company's products and software based on feedback and issues experienced by developers in the community. 2. To be successful in obtaining buy-in, developer advocates need to possess certain essential skills. These include clear and concise communication, where they can articulate the problem, present possible solutions, and provide relevant context and supporting information for informed decisions. Empathy is also crucial, as it helps build strong relationships with stakeholders, understand their goals and concerns, and demonstrate how proposed changes can positively impact them. Patience is necessary because change can take time, and developers should be aware of product roadmaps and engineering timelines. Persistence is key as well, as they may need to explore various approaches to obtain buy-in, and reassess the efficacy of their proposed changes over time. ## Conclusion: Developer advocates play a vital role in advocating for changes to improve products and software based on feedback from the community. The process of gaining buy-in requires building trust and effective communication with decision-makers, ensuring they understand the proposed changes and have the right people supporting them. Skills such as clear communication, empathy, patience, and persistence are essential for developer advocates to succeed in this process. By using tactics like collecting data, recording user experiences, building desired outcomes, and seeking alignment with existing initiatives, they can increase the likelihood of obtaining buy-in for their proposed changes. ## Questions: 1. How can developer advocates effectively communicate with decision-makers to gain their support for proposed changes? 2. What role does empathy play in the process of getting buy-in, and how can developer advocates build strong relationships with stakeholders? 3. How does patience impact the success of obtaining buy-in, and how can developers handle situations where changes take longer than expected? 4. What tactics can developer advocates use to initiate change and demonstrate the benefits of their proposed ideas to decision-makers? 5. How can the use of quantitative and qualitative data enhance the chances of obtaining buy-in for proposed changes? 6. In what ways can developer advocates align their proposed changes with existing initiatives to increase the likelihood of getting buy-in? 7. How can persistence and reassessment of proposed changes over time lead to successful outcomes, even in cases of initial rejection? ## Auto-tagging: developer advocacy, buy-in, decision-makers, communication, empathy, patience, persistence, data collection, user experiences, desired outcomes, alignment, proposed changes. ## Index Creation: - Buy-in: 3 - Definition: 3 - Importance in developer advocacy: 5 - Skills for Getting Buy-in: 4 - Communication: 6 - Empathy: 7 - Patience: 8 - Persistence: 9 - Tactics for Initiating Change: 10 - Data Collection: 11 - Recording Experiences: 12 - Building Desired Outcomes: 13 - Look for Alignment: 14 ## Table of Contents: 1. Introduction 2. Buy-in in Developer Advocacy - Definition - Importance in developer advocacy 3. Skills for Getting Buy-in - Communication - Empathy - Patience - Persistence 4. Tactics for Initiating Change - Data Collection - Recording Experiences - Building Desired Outcomes - Look for Alignment 5. Conclusion 6. Thought-Provoking Questions 7. Key Themes and Topics 8. Index 9. References 10. Future Research and Hypotheses 11. Methodology 12. Implications 13. Logical Validity ## References: No sources were explicitly cited in the article. ## Future Research: - Investigate further how clear communication and problem framing can influence decision-makers' perception of proposed changes. - Explore the role of empathy in building successful relationships with stakeholders and how it impacts their willingness to support proposed changes. - Conduct research on the ideal balance between patience and urgency when seeking buy-in for changes, especially in fast-paced industries. - Examine how different types of data (quantitative vs. qualitative) can be leveraged effectively to strengthen the case for proposed changes. - Investigate the impact of aligning proposed changes with existing initiatives and its effect on decision-makers' willingness to commit to the changes. ## Hypotheses: 1. Hypothesis: Developer advocates who effectively communicate the problem, propose feasible solutions, and provide supporting data are more likely to gain buy-in from decision-makers. 2. Hypothesis: Demonstrating empathy and understanding stakeholders' goals can lead to stronger relationships and increased support for proposed changes. 3. Hypothesis: Patience and persistence are positively correlated with the likelihood of obtaining buy-in for changes, with long-term efforts being more successful. 4. Hypothesis: Utilizing both quantitative and qualitative data can enhance decision-makers' understanding and acceptance of proposed Abstract: Thi > [!note]+ Document Notes <!-- deep-read:sections start --> ## Summarize: This article discusses the concept of "buy-in" in the context of developer advocacy. Buy-in refers to the process of gaining support from decision-makers for proposed changes or ideas. For developer advocates, this means advocating for changes to a company's products and software based on feedback and friction experienced by developers in the community. The article emphasizes the importance of building trust, effective communication, empathy, patience, and persistence in the process of getting buy-in. Skills such as clear communication, relatable problem framing, and understanding the goals of stakeholders are crucial for success. The author shares tactics to initiate change, including collecting quantitative and qualitative data, recording user experiences, building desired outcomes, and aligning proposed changes with existing initiatives. The overall goal is to ensure that when seeking commitment from decision-makers, developer advocates have the right people on board who understand and champion the proposed changes. ## Bullet Points: - **Buy-in in Developer Advocacy**: - Developer advocates seek to advocate for changes to a company's products and software based on community feedback and friction experienced by developers. - Buy-in is the process of gaining support from decision-makers for proposed changes or ideas. - The act of getting buy-in involves building trust, effective communication, and creating champions for the proposed changes. - **Skills for Getting Buy-in**: - Communication: Clearly stating the problem, presenting solutions, and providing sufficient context and supporting information for informed decisions. - Empathy: Building relationships with stakeholders, understanding their goals and metrics, and showing how proposed changes can benefit them. - Patience: Acknowledging that change can be slow and being aware of product roadmaps and engineering timelines. - Persistence: Continuously seeking alternative approaches and reassessing the efficacy of proposed changes over time. - **Tactics for Initiating Change**: - Collecting Data: Gathering quantitative and qualitative data related to stakeholders' goals and the areas of change. - Recording Experiences: Using empathy to help others understand user frustration by documenting experiences with pain points. - Building Desired Outcomes: Creating prototypes or demonstrations to allow decision-makers to experience the benefits of proposed changes. - Look for Alignment: Finding opportunities to align proposed changes with existing plans or projects. - **Conclusion**: As developer advocates, it is essential to thoroughly understand the changes being proposed and provide compelling evidence for them, ensuring the right people are on board to champion and support these changes. ## Paraphrase: 1. One significant challenge for developer advocates is gaining "buy-in," which means obtaining support from decision-makers for proposed changes or ideas. This process involves building trust, effective communication, and having advocates who can champion the proposed changes. As developer advocates, their role is to advocate for changes to a company's products and software based on feedback and issues experienced by developers in the community. 2. To be successful in obtaining buy-in, developer advocates need to possess certain essential skills. These include clear and concise communication, where they can articulate the problem, present possible solutions, and provide relevant context and supporting information for informed decisions. Empathy is also crucial, as it helps build strong relationships with stakeholders, understand their goals and concerns, and demonstrate how proposed changes can positively impact them. Patience is necessary because change can take time, and developers should be aware of product roadmaps and engineering timelines. Persistence is key as well, as they may need to explore various approaches to obtain buy-in, and reassess the efficacy of their proposed changes over time. ## Conclusion: Developer advocates play a vital role in advocating for changes to improve products and software based on feedback from the community. The process of gaining buy-in requires building trust and effective communication with decision-makers, ensuring they understand the proposed changes and have the right people supporting them. Skills such as clear communication, empathy, patience, and persistence are essential for developer advocates to succeed in this process. By using tactics like collecting data, recording user experiences, building desired outcomes, and seeking alignment with existing initiatives, they can increase the likelihood of obtaining buy-in for their proposed changes. ## Questions: 1. How can developer advocates effectively communicate with decision-makers to gain their support for proposed changes? 2. What role does empathy play in the process of getting buy-in, and how can developer advocates build strong relationships with stakeholders? 3. How does patience impact the success of obtaining buy-in, and how can developers handle situations where changes take longer than expected? 4. What tactics can developer advocates use to initiate change and demonstrate the benefits of their proposed ideas to decision-makers? 5. How can the use of quantitative and qualitative data enhance the chances of obtaining buy-in for proposed changes? 6. In what ways can developer advocates align their proposed changes with existing initiatives to increase the likelihood of getting buy-in? 7. How can persistence and reassessment of proposed changes over time lead to successful outcomes, even in cases of initial rejection? ## Auto-tagging: developer advocacy, buy-in, decision-makers, communication, empathy, patience, persistence, data collection, user experiences, desired outcomes, alignment, proposed changes. ## Index Creation: - Buy-in: 3 - Definition: 3 - Importance in developer advocacy: 5 - Skills for Getting Buy-in: 4 - Communication: 6 - Empathy: 7 - Patience: 8 - Persistence: 9 - Tactics for Initiating Change: 10 - Data Collection: 11 - Recording Experiences: 12 - Building Desired Outcomes: 13 - Look for Alignment: 14 ## Table of Contents: 1. Introduction 2. Buy-in in Developer Advocacy - Definition - Importance in developer advocacy 3. Skills for Getting Buy-in - Communication - Empathy - Patience - Persistence 4. Tactics for Initiating Change - Data Collection - Recording Experiences - Building Desired Outcomes - Look for Alignment 5. Conclusion 6. Thought-Provoking Questions 7. Key Themes and Topics 8. Index 9. References 10. Future Research and Hypotheses 11. Methodology 12. Implications 13. Logical Validity ## References: No sources were explicitly cited in the article. ## Future Research: - Investigate further how clear communication and problem framing can influence decision-makers' perception of proposed changes. - Explore the role of empathy in building successful relationships with stakeholders and how it impacts their willingness to support proposed changes. - Conduct research on the ideal balance between patience and urgency when seeking buy-in for changes, especially in fast-paced industries. - Examine how different types of data (quantitative vs. qualitative) can be leveraged effectively to strengthen the case for proposed changes. - Investigate the impact of aligning proposed changes with existing initiatives and its effect on decision-makers' willingness to commit to the changes. ## Hypotheses: 1. Hypothesis: Developer advocates who effectively communicate the problem, propose feasible solutions, and provide supporting data are more likely to gain buy-in from decision-makers. 2. Hypothesis: Demonstrating empathy and understanding stakeholders' goals can lead to stronger relationships and increased support for proposed changes. 3. Hypothesis: Patience and persistence are positively correlated with the likelihood of obtaining buy-in for changes, with long-term efforts being more successful. 4. Hypothesis: Utilizing both quantitative and qualitative data can enhance decision-makers' understanding and acceptance of proposed Abstract: This article provides a comprehensive guide on how to gain alignment and buy-in from stakeholders when advocating for a new technology. It outlines the importance of understanding the needs of stakeholders, how to tailor the message, and how to build relationships that enable collaboration and agreement. It also provides a framework to assess the impact of an initiative and provides tips on how to effectively communicate the value. By following these steps, developers are better positioned to build consensus and gain the necessary support for their projects. Detailed Bullet List: • Understanding Stakeholder Needs: - Identifying the stakeholders - Assessing their needs - Assessing their motivations and objectives - Tailoring the message to the stakeholders • Building Relationships: - Building relationships with stakeholders - Understanding the dynamics at play - Enhancing collaboration and agreement • Assessing Impact: - Identifying the potential impact of the initiative - Assessing the impact on stakeholders - Documenting the initiative goals and plans • Communicating Value: - Understanding how to effectively communicate the value of the initiative - Identifying the audience - Creating clear and concise messages - Utilizing visual aids to illustrate the impact Paraphrased Paragraphs: Paragraph 1: In order to gain alignment and buy-in from stakeholders, it is important to understand their needs and objectives. This involves identifying the stakeholders, assessing their motivations and objectives, and tailoring the message to meet their specific requirements. By doing this, developers can ensure that their message is received and understood. Paragraph 2: Building relationships with stakeholders is essential for achieving consensus and gaining support for a project. It is important to understand the dynamics at play and work to enhance collaboration and agreement. This can be done by offering to help with any unforeseen issues, listening to feedback, and being open and transparent about the project. 1. What are some additional tactics I can use to get buy-in for proposed changes? 2. What are the most effective ways to communicate my ideas and get buy-in? 3. What are the best ways to build relationships with decision-makers to ensure mutually beneficial changes? This document is about how to get buy-in for changes proposed by developer advocates. The process of getting buy-in involves building trust, communicating ideas well, and creating champions who will support the changes. It also involves understanding what goals decision-makers are working towards and how changes will affect their plans and the amount of work it will take. To get buy-in, it is important to present the problem clearly, present a solution, and provide enough context and supporting information. Quantitative and qualitative data can also be helpful in making the case for changes. Finally, it is important to understand product roadmaps and engineering timelines, as well as to look for other ways to help users if buy-in is not immediately available. <!-- deep-read:sections end --> ## Highlights - Getting buy-in as a developer advocate is a unique challenge. We usually are not the owners or even direct contributors to what we're trying to change. Instead, we represent this bizarre ephemeral thing called a "community." ([View Highlight](https://read.readwise.io/read/01gvy7hv5fv3ahgw1bnr7awf02)) - Make sure you're aware of product roadmaps and engineering timelines—plan for changes to take a while if adopted at all. Also, have fallbacks and short-term fixes to help reduce friction until you can get a proper fix. ([View Highlight](https://read.readwise.io/read/01gvy7jcd99wwt82n3p5xgemav)) - We have to provide so much compelling evidence for our case that not only do they support our ideas but champion them as well ([View Highlight](https://read.readwise.io/read/01gvy7ka5t9cxdk348xjq8zfcr)) - Note: This document is a guide for Developer Advocates on how to get buy-in from decision-makers in order to initiate the changes they want to make. The process involves building relationships with those decision-makers, understanding their goals and plans, and providing them with both quantitative and qualitative data to show how the change will benefit them. They should also be aware of product roadmaps and engineering timelines, and look for opportunities to include their changes in existing initiatives. Additionally, they should create prototypes or desired outcomes for decision-makers to experience the change and ensure their changes are aligned with existing plans.