Your First 30 Days in a New DevRel Role  [[3. Resources/Readwise/Full Document Contents/Articles/Your First 30 Days in a New DevRel Role|Full Document Contents]] ## Document Notes ## Summarize: The article provides a week-by-week DevRel discovery guide for professionals in new Developer Relations (DevRel) roles. It emphasizes the importance of understanding the company's landscape, products, and stakeholders to drive maximum impact. The four-week guide covers specific tasks and objectives for each week: 1. **Week 1** - Focus on understanding the company's product offerings for developers, gathering insights from teams like sales, customer support, and the internet. 2. **Week 2** - Prepare a "What is DevRel" presentation and schedule meetings with key stakeholders from various functions across the organization. 3. **Week 3** - Conduct stakeholder interviews, aiming to listen and understand their goals, challenges, and alignment with DevRel. 4. **Week 4** - Perform a developer experience audit by evaluating the company's offerings and communications from a developer's perspective. ## Bullet Points: - **Week 1: Understand the Company Landscape** - Research product offerings for developers. - Seek insights from sales, customer support, and the internet. - Identify the company's value proposition to developers and competitors. - **Week 2: Program Preparation and Stakeholder Calls** - Create a "What is DevRel" presentation. - Schedule meetings with stakeholders from various functions. - Seek early allies and understand their goals and priorities. - **Week 3: Stakeholder Interviews** - Listen and understand stakeholder perspectives. - Identify those who understand DevRel and potential areas for improvement. - Determine team priorities and challenges for DevRel alignment. - **Week 4: Developer Experience Audit** - Examine the company's website and offerings from a developer's standpoint. - Evaluate product features, cost, implementation, and documentation. - Assess communication and promotional strategies for developers. ## Paraphrase: 1. *Week 1: Understand the Company Landscape* In the first week, your focus should be on comprehending the product offerings for developers within your company. Gather valuable insights by collaborating with teams like sales, customer support, and explore online resources. This research will prove instrumental in shaping your go-to-market strategy, so take diligent notes and organize them for future reference. 2. *Week 3: Stakeholder Interviews* As you move into the third week, shift your focus towards engaging in meaningful conversations with stakeholders. Listen actively and gauge their familiarity with DevRel. Identify potential early allies and individuals who may need more extensive explanations about your role. It's essential to grasp their objectives and priorities, as this will aid you in driving impactful outcomes for their teams. ## Conclusion: The article presents a comprehensive four-week guide for new DevRel professionals. It highlights the importance of understanding the company's product landscape, stakeholders, and the developer experience. By diligently following this guide, DevRel advocates can establish a solid foundation, ensure stakeholder buy-in, and create a successful DevRel program. ## Questions: 1. How can the DevRel discovery process be adapted for companies with different organizational structures or varying sizes? 2. In what ways can DevRel professionals leverage their early allies to gain broader support within the organization? 3. How does the developer experience audit help identify areas for improvement and influence decision-making? 4. What are some potential challenges DevRel advocates might face when aligning their goals with other functions in the company? ## Auto-tagging: DevRel, Developer Relations, Onboarding, Company Landscape, Stakeholder Interviews, Stakeholder Engagement, Developer Experience Audit, Stakeholder Buy-in, Go-to-Market Strategy, Early Allies ## Index Creation: - Developer Relations: 1 - Onboarding: 1 - Company Landscape: 2 - Stakeholder Interviews: 3 - Stakeholder Engagement: 3 - Developer Experience Audit: 4 - Stakeholder Buy-in: 3 - Go-to-Market Strategy: 1 - Early Allies: 2 ## Table of Contents: 1. Introduction 2. Week 1 - Understand the Company Landscape - Researching product offerings - Gathering insights from teams and the internet - Identifying value proposition and competitors 3. Week 2 - Program Preparation and Stakeholder Calls - Creating a "What is DevRel" presentation - Scheduling meetings with key stakeholders - Understanding stakeholders' goals and priorities 4. Week 3 - Stakeholder Interviews - Actively listening and understanding perspectives - Identifying early allies and areas for improvement - Grasping stakeholder objectives and challenges 5. Week 4 - Developer Experience Audit - Evaluating company website and offerings from a developer's perspective - Assessing product features, cost, and documentation - Analyzing communication and promotional strategies 6. Conclusion 7. Thought-Provoking Questions 8. Auto-Tagged Themes and Topics 9. Index 10. References ## References: 1. [Devocate - DevRel Discovery Guide](https://devocate.com/devrel-discovery-guide) ## Future Research: 1. Investigate the effectiveness of different onboarding strategies for DevRel professionals in diverse industries. 2. Examine the correlation between stakeholder engagement during the initial 30 days and the long-term success of DevRel programs. 3. Explore the impact of developer experience audits on product improvements and customer satisfaction. 4. Conduct comparative studies on DevRel approaches in companies of different sizes and stages of growth. ## Hypotheses: 1. Companies with well-defined developer personas are more likely to experience higher developer engagement and adoption rates. 2. DevRel professionals who effectively align their goals with stakeholders' priorities will encounter fewer challenges in gaining support and resources. 3. A positive developer experience audit outcome will result in increased user retention and positive word-of-mouth referrals. 4. Early engagement with stakeholders during the onboarding phase will positively influence the overall success of DevRel programs. ## Methodology: 1. Conduct surveys and interviews with DevRel professionals from companies of varying sizes and industries to gather data on their onboarding experiences and strategies. 2. Analyze historical data on developer engagement metrics in companies with established developer personas versus those without. 3. Perform A/B testing with different versions of the "What is DevRel" presentation to assess its impact on stakeholder understanding and buy-in. 4. Utilize user feedback and analytics to evaluate the effectiveness of changes implemented following the developer experience audit. ## Implications: The findings from future research on DevRel can significantly contribute to the field's knowledge and practice. Effective onboarding strategies and stakeholder engagement approaches can enhance the success of DevRel programs. Understanding developer preferences through audits can lead to better product offerings and improved user experiences. Ultimately, this research can inform the development of more impactful and sustainable DevRel initiatives. ## Logical Validity: The article's main arguments are logically coherent and well-structured. The four-week DevRel discovery guide provides a systematic approach for professionals to set themselves up for success in their new roles. It emphasizes the importance of understanding the company landscape, stakeholder engagement, and the developer experience. The logical flow of each week's tasks ensures a comprehensive understanding of the company's developer-related aspects. There are no apparent logical fallacies employed in the article. However, to further validate the guide's effectiveness, real-world case studies and data-driven insights from DevRel practitioners would be beneficial. These would support the claims made in the article and provide more concrete evidence of the guide's impact in various organizational contexts. Additionally, considering the evolving nature of the tech industry Abstract: This document provides a guide for > [!note]+ Document Notes <!-- deep-read:sections start --> ## Summarize: The article provides a week-by-week DevRel discovery guide for professionals in new Developer Relations (DevRel) roles. It emphasizes the importance of understanding the company's landscape, products, and stakeholders to drive maximum impact. The four-week guide covers specific tasks and objectives for each week: 1. **Week 1** - Focus on understanding the company's product offerings for developers, gathering insights from teams like sales, customer support, and the internet. 2. **Week 2** - Prepare a "What is DevRel" presentation and schedule meetings with key stakeholders from various functions across the organization. 3. **Week 3** - Conduct stakeholder interviews, aiming to listen and understand their goals, challenges, and alignment with DevRel. 4. **Week 4** - Perform a developer experience audit by evaluating the company's offerings and communications from a developer's perspective. ## Bullet Points: - **Week 1: Understand the Company Landscape** - Research product offerings for developers. - Seek insights from sales, customer support, and the internet. - Identify the company's value proposition to developers and competitors. - **Week 2: Program Preparation and Stakeholder Calls** - Create a "What is DevRel" presentation. - Schedule meetings with stakeholders from various functions. - Seek early allies and understand their goals and priorities. - **Week 3: Stakeholder Interviews** - Listen and understand stakeholder perspectives. - Identify those who understand DevRel and potential areas for improvement. - Determine team priorities and challenges for DevRel alignment. - **Week 4: Developer Experience Audit** - Examine the company's website and offerings from a developer's standpoint. - Evaluate product features, cost, implementation, and documentation. - Assess communication and promotional strategies for developers. ## Paraphrase: 1. *Week 1: Understand the Company Landscape* In the first week, your focus should be on comprehending the product offerings for developers within your company. Gather valuable insights by collaborating with teams like sales, customer support, and explore online resources. This research will prove instrumental in shaping your go-to-market strategy, so take diligent notes and organize them for future reference. 2. *Week 3: Stakeholder Interviews* As you move into the third week, shift your focus towards engaging in meaningful conversations with stakeholders. Listen actively and gauge their familiarity with DevRel. Identify potential early allies and individuals who may need more extensive explanations about your role. It's essential to grasp their objectives and priorities, as this will aid you in driving impactful outcomes for their teams. ## Conclusion: The article presents a comprehensive four-week guide for new DevRel professionals. It highlights the importance of understanding the company's product landscape, stakeholders, and the developer experience. By diligently following this guide, DevRel advocates can establish a solid foundation, ensure stakeholder buy-in, and create a successful DevRel program. ## Questions: 1. How can the DevRel discovery process be adapted for companies with different organizational structures or varying sizes? 2. In what ways can DevRel professionals leverage their early allies to gain broader support within the organization? 3. How does the developer experience audit help identify areas for improvement and influence decision-making? 4. What are some potential challenges DevRel advocates might face when aligning their goals with other functions in the company? ## Auto-tagging: DevRel, Developer Relations, Onboarding, Company Landscape, Stakeholder Interviews, Stakeholder Engagement, Developer Experience Audit, Stakeholder Buy-in, Go-to-Market Strategy, Early Allies ## Index Creation: - Developer Relations: 1 - Onboarding: 1 - Company Landscape: 2 - Stakeholder Interviews: 3 - Stakeholder Engagement: 3 - Developer Experience Audit: 4 - Stakeholder Buy-in: 3 - Go-to-Market Strategy: 1 - Early Allies: 2 ## Table of Contents: 1. Introduction 2. Week 1 - Understand the Company Landscape - Researching product offerings - Gathering insights from teams and the internet - Identifying value proposition and competitors 3. Week 2 - Program Preparation and Stakeholder Calls - Creating a "What is DevRel" presentation - Scheduling meetings with key stakeholders - Understanding stakeholders' goals and priorities 4. Week 3 - Stakeholder Interviews - Actively listening and understanding perspectives - Identifying early allies and areas for improvement - Grasping stakeholder objectives and challenges 5. Week 4 - Developer Experience Audit - Evaluating company website and offerings from a developer's perspective - Assessing product features, cost, and documentation - Analyzing communication and promotional strategies 6. Conclusion 7. Thought-Provoking Questions 8. Auto-Tagged Themes and Topics 9. Index 10. References ## References: 1. [Devocate - DevRel Discovery Guide](https://devocate.com/devrel-discovery-guide) ## Future Research: 1. Investigate the effectiveness of different onboarding strategies for DevRel professionals in diverse industries. 2. Examine the correlation between stakeholder engagement during the initial 30 days and the long-term success of DevRel programs. 3. Explore the impact of developer experience audits on product improvements and customer satisfaction. 4. Conduct comparative studies on DevRel approaches in companies of different sizes and stages of growth. ## Hypotheses: 1. Companies with well-defined developer personas are more likely to experience higher developer engagement and adoption rates. 2. DevRel professionals who effectively align their goals with stakeholders' priorities will encounter fewer challenges in gaining support and resources. 3. A positive developer experience audit outcome will result in increased user retention and positive word-of-mouth referrals. 4. Early engagement with stakeholders during the onboarding phase will positively influence the overall success of DevRel programs. ## Methodology: 1. Conduct surveys and interviews with DevRel professionals from companies of varying sizes and industries to gather data on their onboarding experiences and strategies. 2. Analyze historical data on developer engagement metrics in companies with established developer personas versus those without. 3. Perform A/B testing with different versions of the "What is DevRel" presentation to assess its impact on stakeholder understanding and buy-in. 4. Utilize user feedback and analytics to evaluate the effectiveness of changes implemented following the developer experience audit. ## Implications: The findings from future research on DevRel can significantly contribute to the field's knowledge and practice. Effective onboarding strategies and stakeholder engagement approaches can enhance the success of DevRel programs. Understanding developer preferences through audits can lead to better product offerings and improved user experiences. Ultimately, this research can inform the development of more impactful and sustainable DevRel initiatives. ## Logical Validity: The article's main arguments are logically coherent and well-structured. The four-week DevRel discovery guide provides a systematic approach for professionals to set themselves up for success in their new roles. It emphasizes the importance of understanding the company landscape, stakeholder engagement, and the developer experience. The logical flow of each week's tasks ensures a comprehensive understanding of the company's developer-related aspects. There are no apparent logical fallacies employed in the article. However, to further validate the guide's effectiveness, real-world case studies and data-driven insights from DevRel practitioners would be beneficial. These would support the claims made in the article and provide more concrete evidence of the guide's impact in various organizational contexts. Additionally, considering the evolving nature of the tech industry Abstract: This document provides a guide for individuals taking on a new role in Developer Relations (DevRel). It covers the first 30 days in the role, outlining how to get up to speed quickly and successfully. The guide discusses setting up an onboarding plan, building relationships with stakeholders, and getting familiar with the tools and processes. It also provides tips on how to effectively communicate with the team, build relationships, and gain visibility. Finally, the guide offers advice on how to set up a successful DevRel program and how to measure its success. Bullet List Summary: • Onboarding Plan: ○ Set up a meeting with stakeholders ○ Use onboarding tools to get up to speed ○ Gain familiarity with tools and processes • Relationships and Communication: ○ Get to know the team ○ Build relationships with stakeholders ○ Communicate effectively • Visibility and DevRel Program: ○ Set up a DevRel program ○ Develop strategies to gain visibility ○ Measure success Paraphrased Paragraphs: Paragraph 1: At the beginning of your new role, it is important to create an onboarding plan. This should include meeting with stakeholders to understand expectations and getting familiar with tools and processes. Paraphrase: In order to get off to a good start in your new role, it is essential to devise an onboarding plan. This should involve interacting with stakeholders to determine what is expected of you and gaining knowledge about the tools and procedures. 1. What are the most important goals and priorities of key stakeholders across the organization? 2. What challenges do I anticipate facing with internal stakeholder buy-in? 3. How can I use the developer experience audit to make improvements to the developer experience? This document provides a step-by-step guide for the first 30 days of a DevRel role. During this period, the focus should be on understanding the company landscape, preparing to speak to stakeholders, conducting stakeholder interviews, and auditing the developer experience. It is important to understand the company's product offerings, its value proposition to developers, its competitors, and its marketing funnel and sales process. This guide will help set the foundation of the DevRel program and prepare the person for the next steps of building their personas and formalizing their goals. <!-- deep-read:sections end --> ## Highlights - By the end of week 1, you should have most of these questions answered. Be sure to iterate on these answers as you grow in your role. • What products does your company offer to developers? • What is the monetization strategy for developer products? • What roles do developers play in the decision-making process currently? • Does your company have defined personas, specifically around developers? • What is the value proposition to developers? • What is the product-market fit? • Who are your competitors? • How are you different from your competitors? ([View Highlight](https://read.readwise.io/read/01gvxqbk25f60swfcgzzfrqg6x)) - Schedule time with key stakeholders across your organization for next week (week 3) ([View Highlight](https://read.readwise.io/read/01gvxqcsg4xy5j408jhs9srf2m)) - • Sales or Sales Engineering, specifically those selling to developers • Marketing or Product Marketing, specifically for developer products • Customer Success or Support, specifically those serving developers • Product, specifically those leading the developer products • Engineering, specifically those building the developer products • Other functions that are currently serving developer audiences in any capacity ([View Highlight](https://read.readwise.io/read/01gvxqd4k27w2kt1ynbn034xh7)) - Week 3 — stakeholder interviews ([View Highlight](https://read.readwise.io/read/01gvxqdbx3h469jzw0sj80jbxk)) - You should be able to answer these questions after your stakeholder interviews are completed: • Who within the company understands DevRel? • Who within the company doesn’t understand DevRel? • What are the goals & priorities of key stakeholders across the org? • What gaps or challenges do you foresee facing with internal stakeholder buy-in? • Which stakeholders will you work with on a regular basis? • What does the marketing funnel look like? • What does the sale process look like? • What tools do sales and marketing use to track conversions? • What other tools are procured and available for your use? ([View Highlight](https://read.readwise.io/read/01gvxqdsagmnh846gep9m8kvrg)) - Week 4 — developer experience audit ([View Highlight](https://read.readwise.io/read/01gvxqe0p6jatfe4t3sswq203h)) - • What products are available to you? • What features do those products serve? • How much do the products cost? • How long will it take you to implement those products? • Is there proper documentation to implement these products? • How long will it take you to reach “Hello World?” • What do the communications look like? • Do they have a published changelog? • How does your company currently appear to developers? • Are the communications and platforms promotional? ([View Highlight](https://read.readwise.io/read/01gvxqe7xgzgaw930wwgqnfwf2))