Developer Relations Is an All-Company Effort  [[3. Resources/Readwise/Full Document Contents/Articles/Developer Relations Is an All-Company Effort|Full Document Contents]] ## Document Notes # Title: Understanding Developer Relations and Its Challenges - - - tags: #DeveloperRelations #DevRel #Technology #Marketing Author: Alexander Reelsen Source: DevRel Dissatisfaction Reference: [Link to the source](provide_link_here) date created: 2024-01-21T09:15 - - - ## Table of Contents: 1. Introduction to Developer Relations 2. The Evolution of DevRel Strategies 3. DevRel Professionals: A Surge and Exodus 4. DevRel Challenges and Misconceptions 5. The Importance of Company-Wide Involvement 6. Creating a Culture of DevRel 7. Realistic Expectations for DevRel ## Index Creation: - Developer Relations - DevRel Strategies - DevRel Professionals - Challenges - Company-Wide Involvement - DevRel Culture - Expectations ## 📝 Summary: This article explores the field of Developer Relations (DevRel), its evolution in response to changing technology markets, and the challenges faced by DevRel professionals. It highlights the importance of company-wide involvement in DevRel efforts and provides recommendations for creating a culture of DevRel within organizations. The article also discusses the need for realistic expectations regarding the impact and timeline of DevRel activities. ## 📖 Main Content: Developer Relations (DevRel) is a multifaceted field that includes roles like Developer Experience Engineers, Developer Advocates, Community Managers, Technical Writers, and Developer Marketers. Its primary goal is to bridge the gap between technologists and businesses by facilitating communication. DevRel professionals often represent the developer community to the company and vice versa, raising awareness about products, engaging with the developer community, and improving the developer experience. DevRel strategies encompass various activities, including podcast discussions, conference talks, blog posts, and one-on-one interactions with developers. These strategies aim to build trust, educate users, and increase product adoption, but the results may take months to years to manifest. One common mistake in DevRel teams is an imbalance between internal and external activities. While both are crucial, neglecting external efforts can hinder product visibility, while ignoring internal work can lead to poor documentation and developer experiences. DevRel teams often face unrealistic expectations, such as juggling too many tasks at once, delivering quick results in community growth, and operating in isolation without support from other teams. These misconceptions can strain DevRel professionals. To address these challenges, organizations should foster a culture of DevRel that includes early engagement in DevRel activities, inclusive strategy discussions, and non-DevRel staff involvement in initiatives. Open communication and knowledge transfer from engineering to DevRel are vital, as is integrating DevRel principles into the company's mission. However, it's essential to maintain realistic expectations about DevRel's impact and timeline, as it often involves long-term efforts that require patience. ## 🗒️ Notes - DevRel includes roles like Developer Experience Engineers, Developer Advocates, Community Managers, Technical Writers, and Developer Marketers. - Developer Relations facilitates communication between technologists and businesses. - Strategies include podcast discussions, conference talks, blog posts, and one-on-one interactions. - Imbalance between internal and external activities can hinder DevRel success. - Unrealistic expectations include juggling too many tasks, expecting quick results, and operating in isolation. - A DevRel culture should involve early engagement, inclusive discussions, and non-DevRel staff participation. - Open communication and knowledge transfer are crucial. - Integrating DevRel principles into the company's mission aligns efforts. ## 📖 References: - [Link to the source](provide_link_here) ## 🗣️ Paraphrase: 1. "Even if your product has the best user experience or solves the world's biggest problems, no one will ever use it if they don't know that it exists." - Effective marketing is essential to product adoption. 2. "DevRel demands a careful balance between external activities and internal activities." - Balancing external and internal efforts is crucial in DevRel. 3. "The real issue lies in the unrealistic expectations placed on DevRel teams." - Unrealistic expectations strain DevRel professionals. 4. "Making DevRel an all-company endeavor can look like..." - Involving the entire company in DevRel activities can include early engagement, inclusive discussions, and non-DevRel staff participation. ## 🧪 Hypotheses: 1. Future studies could explore the impact of early engagement in DevRel activities on overall product adoption and community engagement. 2. Research could investigate the correlation between inclusive strategy discussions and improved developer experiences within organizations. 3. Examining the effectiveness of integrating DevRel principles into a company's mission in fostering a collaborative and open developer community could be a valuable area of study. ### 📊 Methodology: 1. Conduct surveys and interviews with organizations that have implemented early engagement in DevRel activities to assess the impact on product adoption and community engagement. 2. Analyze data from organizations that involve DevRel in strategy discussions and compare the developer experience before and after such involvement. 3. Study companies that have integrated DevRel principles into their mission statements to understand the effects on collaboration and community building. ### 💡 Implications: - Research on the impact of early engagement in DevRel activities can inform organizations about effective strategies for product adoption and community growth. - Understanding the correlation between inclusive strategy discussions and improved developer experiences can lead to better practices within organizations. - Exploring the effects of integrating DevRel principles into a company's mission can help align efforts and foster a more open developer community. ### 🔮 Future Research: 1. Investigate the role of DevRel in addressing specific weaknesses within companies and how it contributes to overall success. 2. Explore the challenges and benefits of maintaining a balance between external and internal DevRel activities. 3. Examine the impact of realistic expectations on the job satisfaction and performance of DevRel professionals. ### ❓ Implications: - Understanding the role of DevRel in addressing company weaknesses can lead to more targeted hiring and skill development. - Research on balancing external and internal DevRel activities can inform organizations about optimizing their DevRel efforts. - Examining the impact of realistic expectations can lead to better support and management of DevRel teams. ### ✅ Logical validity: The article presents a logical and coherent argument about the challenges and importance of Developer Relations (DevRel). It identifies the need for a balance between internal and external DevRel activities and highlights the issue of unrealistic expectations. The tone is informative and insightful. ## Conclusion: Developer Relations is a vital field that facilitates communication between technologists and businesses. It involves various roles and strategies, including raising awareness, engaging with the developer community, and improving the developer experience. Challenges such as balancing internal and external activities and unrealistic expectations exist but can be addressed through a company-wide culture of DevRel. Realistic expectations are crucial for success in DevRel, as it often involves long-term efforts. > [!note]+ Document Notes > # Title: Understanding Developer Relations and Its Challenges > > - - - > tags: #DeveloperRelations #DevRel #Technology #Marketing > Author: Alexander Reelsen > Source: DevRel Dissatisfaction > Reference: [Link to the source](provide_link_here) > date created: 2024-01-21T09:15 > > - - - > <!-- deep-read:sections start --> ## Table of Contents: 1. Introduction to Developer Relations 2. The Evolution of DevRel Strategies 3. DevRel Professionals: A Surge and Exodus 4. DevRel Challenges and Misconceptions 5. The Importance of Company-Wide Involvement 6. Creating a Culture of DevRel 7. Realistic Expectations for DevRel ## Index Creation: - Developer Relations - DevRel Strategies - DevRel Professionals - Challenges - Company-Wide Involvement - DevRel Culture - Expectations ## 📝 Summary: This article explores the field of Developer Relations (DevRel), its evolution in response to changing technology markets, and the challenges faced by DevRel professionals. It highlights the importance of company-wide involvement in DevRel efforts and provides recommendations for creating a culture of DevRel within organizations. The article also discusses the need for realistic expectations regarding the impact and timeline of DevRel activities. ## 📖 Main Content: Developer Relations (DevRel) is a multifaceted field that includes roles like Developer Experience Engineers, Developer Advocates, Community Managers, Technical Writers, and Developer Marketers. Its primary goal is to bridge the gap between technologists and businesses by facilitating communication. DevRel professionals often represent the developer community to the company and vice versa, raising awareness about products, engaging with the developer community, and improving the developer experience. DevRel strategies encompass various activities, including podcast discussions, conference talks, blog posts, and one-on-one interactions with developers. These strategies aim to build trust, educate users, and increase product adoption, but the results may take months to years to manifest. One common mistake in DevRel teams is an imbalance between internal and external activities. While both are crucial, neglecting external efforts can hinder product visibility, while ignoring internal work can lead to poor documentation and developer experiences. DevRel teams often face unrealistic expectations, such as juggling too many tasks at once, delivering quick results in community growth, and operating in isolation without support from other teams. These misconceptions can strain DevRel professionals. To address these challenges, organizations should foster a culture of DevRel that includes early engagement in DevRel activities, inclusive strategy discussions, and non-DevRel staff involvement in initiatives. Open communication and knowledge transfer from engineering to DevRel are vital, as is integrating DevRel principles into the company's mission. However, it's essential to maintain realistic expectations about DevRel's impact and timeline, as it often involves long-term efforts that require patience. ## 🗒️ Notes - DevRel includes roles like Developer Experience Engineers, Developer Advocates, Community Managers, Technical Writers, and Developer Marketers. - Developer Relations facilitates communication between technologists and businesses. - Strategies include podcast discussions, conference talks, blog posts, and one-on-one interactions. - Imbalance between internal and external activities can hinder DevRel success. - Unrealistic expectations include juggling too many tasks, expecting quick results, and operating in isolation. - A DevRel culture should involve early engagement, inclusive discussions, and non-DevRel staff participation. - Open communication and knowledge transfer are crucial. - Integrating DevRel principles into the company's mission aligns efforts. ## 📖 References: - [Link to the source](provide_link_here) ## 🗣️ Paraphrase: 1. "Even if your product has the best user experience or solves the world's biggest problems, no one will ever use it if they don't know that it exists." - Effective marketing is essential to product adoption. 2. "DevRel demands a careful balance between external activities and internal activities." - Balancing external and internal efforts is crucial in DevRel. 3. "The real issue lies in the unrealistic expectations placed on DevRel teams." - Unrealistic expectations strain DevRel professionals. 4. "Making DevRel an all-company endeavor can look like..." - Involving the entire company in DevRel activities can include early engagement, inclusive discussions, and non-DevRel staff participation. ## 🧪 Hypotheses: 1. Future studies could explore the impact of early engagement in DevRel activities on overall product adoption and community engagement. 2. Research could investigate the correlation between inclusive strategy discussions and improved developer experiences within organizations. 3. Examining the effectiveness of integrating DevRel principles into a company's mission in fostering a collaborative and open developer community could be a valuable area of study. ### 📊 Methodology: 1. Conduct surveys and interviews with organizations that have implemented early engagement in DevRel activities to assess the impact on product adoption and community engagement. 2. Analyze data from organizations that involve DevRel in strategy discussions and compare the developer experience before and after such involvement. 3. Study companies that have integrated DevRel principles into their mission statements to understand the effects on collaboration and community building. ### 💡 Implications: - Research on the impact of early engagement in DevRel activities can inform organizations about effective strategies for product adoption and community growth. - Understanding the correlation between inclusive strategy discussions and improved developer experiences can lead to better practices within organizations. - Exploring the effects of integrating DevRel principles into a company's mission can help align efforts and foster a more open developer community. ### 🔮 Future Research: 1. Investigate the role of DevRel in addressing specific weaknesses within companies and how it contributes to overall success. 2. Explore the challenges and benefits of maintaining a balance between external and internal DevRel activities. 3. Examine the impact of realistic expectations on the job satisfaction and performance of DevRel professionals. ### ❓ Implications: - Understanding the role of DevRel in addressing company weaknesses can lead to more targeted hiring and skill development. - Research on balancing external and internal DevRel activities can inform organizations about optimizing their DevRel efforts. - Examining the impact of realistic expectations can lead to better support and management of DevRel teams. ### ✅ Logical validity: The article presents a logical and coherent argument about the challenges and importance of Developer Relations (DevRel). It identifies the need for a balance between internal and external DevRel activities and highlights the issue of unrealistic expectations. The tone is informative and insightful. ## Conclusion: Developer Relations is a vital field that facilitates communication between technologists and businesses. It involves various roles and strategies, including raising awareness, engaging with the developer community, and improving the developer experience. Challenges such as balancing internal and external activities and unrealistic expectations exist but can be addressed through a company-wide culture of DevRel. Realistic expectations are crucial for success in DevRel, as it often involves long-term efforts. <!-- deep-read:sections end --> ## Highlights - As a result, this led to a surge in hiring Developer Relations professionals. However, in 2022 and 2023, another shift occurred; a large influx of DevRel professionals left the industry. Some departures followed company layoffs, as businesses didn't see immediate return on their DevRel investments. Simultaneously, disillusioned individuals left voluntarily, often sharing their frustrations with unrealistic company expectations through YouTube and blogs. ([View Highlight](https://read.readwise.io/read/01hmq0m44x6vqww3790vvr0nb1)) - • Increasing community engagement • Modifying your DevRel strategy for various regions • Building relationships across your company • The art of public speaking ([View Highlight](https://read.readwise.io/read/01hmq0mjm10mj9dt8jrzbs33e5)) - Developer Relations, nicknamed DevRel for short, is a field made up of multiple roles including Developer Experience Engineers, Developer Advocates, Community Managers, Technical Writers, Developer Marketers, and more ([View Highlight](https://read.readwise.io/read/01hmq0ndfq9y4e709ap1826eeh)) - The primary objective of a DevRel team is to facilitate communication between technologists and the business ([View Highlight](https://read.readwise.io/read/01hmq0nnhssj5ta251tcpk6jwx)) - eveloper Advocates raise awareness about the company's products within the developer community and provide the community's feedback to enhance the developer experience within the company. • Creating awareness can take various forms, such as discussing the company's developer tools on podcasts, giving conference talks, and writing blog posts. • Engaging with the developer community involves direct interactions, like one-on-one conversations in forums, audio spaces, or at conferences. • Improving the developer experience often involves relaying feedback to engineering or product teams, maintaining documentation, creating user-friendly sample applications, and developing open source SDKs that complement the company's product. ([View Highlight](https://read.readwise.io/read/01hmq0nzp7r4pw5ze1zk9j5hbd)) - Developer Relations demands a careful balance between external activities and internal activities. Internal work, like community engagement and content creation, builds awareness and amplifies the company's presence. However, some DevRel teams focus too heavily on internal work, and then they struggle to make them product more known. Conversely, teams mainly focused on external efforts might neglect keeping documentation and example apps up to date. ([View Highlight](https://read.readwise.io/read/01hmq0pkr9529ejgfac2eynmdk)) - Developer Advocates often act as gap fillers, addressing specific weaknesses within the company. ([View Highlight](https://read.readwise.io/read/01hmq0q5vy33h1m5hcx2gsjz06)) - nrealistic expectations placed on DevRel teams, such as expecting the teams to: • Juggle too many tasks at once rather than focusing on specific objectives at different times, especially in smaller teams. Larger teams have bandwidth to delegate distinct areas like video production, blogging, or SDK maintenance. • Deliver quick results in areas like community growth, reputation building, and technology adoption. Such processes naturally take time. People don't instantly embrace new technologies after hearing about them. They require an engaging onboarding experience, positive interactions with the team, accessible documentation, and fun building processes. Establishing a smooth onboarding process might take several months, and improving documentation could take up to a year. • Operating in isolation without support from other teams. While DevRel supports other teams within the company, reciprocal support isn't always there. For DevRel to truly succeed, other departments must invest time and resources in helping DevRel achieve its objectives. ([View Highlight](https://read.readwise.io/read/01hmq0qfz3kc2s789jqcv7zam9)) - **Early Engagement in DevRel Activities**: Even at an early stage, try performing DevRel activities BEFORE hiring a DevRel team. This firsthand experience builds empathy, respect for the role, and a clearer understanding of the specific gaps that a DevRel team would need to fill. It could also save you some mon ([View Highlight](https://read.readwise.io/read/01hmq0qrcdngvyjtpd5w6xxqfe)) - **Inclusive Strategy and Product Discussions:** Involve DevRel in meetings regarding strategy, product development, and engineering. DevRel should be informed and participate in the process if there are changes to the code or new company initiatives. ([View Highlight](https://read.readwise.io/read/01hmq0qttb7z1k2jqwsemve3cx)) - • **Encourage non-DevRel staff to contribute to DevRel initiatives:** While DevRel leads content creation and public speaking, other employees should also be involved. For instance, an engineer sharing their perspective on tool development can boost the company's repertoire. ([View Highlight](https://read.readwise.io/read/01hmq0qzg06b2j83hg1wv2ccz8)) - **Practice working in public:** This is especially important and easy if your company has an open source product. The community needs to know the roadmap and how you're thinking about building the product so that they can make valuable contributions. Working privately and expecting DevRel to publicize internal developments can lead to communication gaps. Open source thrives on mutual learning, often requiring more than code commits. ([View Highlight](https://read.readwise.io/read/01hmq0r3hfm40v46mzw3sdjehq)) - • **Keep open lines of communication:** Maybe you're not on the DevRel, but you heard some feedback at a conference or when talking with a community member. Share that feedback with the engineering team and the DevRel team. Regular feedback sessions can help bring community insights into company processes. ([View Highlight](https://read.readwise.io/read/01hmq0r6gtr84svk1nbvqyvgwk)) - **Transfer knowledge from engineering to DevRel** - Engineers know how the product ***should*** work because they built it. Transferring knowledge empowers DevRel to create more relatable and engaging content, documentation, and use cases for the community. ([View Highlight](https://read.readwise.io/read/01hmq0r9mghzcd6j3yv340jd4j)) - **Integrate DevRel Principles in the Company Mission:** Embedding DevRel and open source principles into the company's mission aligns everyone's efforts with fostering a collaborative and open developer community. ([View Highlight](https://read.readwise.io/read/01hmq0rbm9j38nv40fj4e9xzs5)) - Note: Question: What is the primary objective of a DevRel team? Answer: The primary objective of a DevRel team is to facilitate communication between technologists and the business. Question: What is the importance of early engagement in DevRel activities? Answer: Early engagement in DevRel activities builds empathy, respect for the role, and a clearer understanding of the specific gaps that a DevRel team would need to fill. It could also save the company some money. Question: What is the danger of DevRel teams focusing too heavily on internal work? Answer: Some DevRel teams focus too heavily on internal work, and then they struggle to make the product more known. Conversely, teams mainly focused on external efforts might neglect keeping documentation and example apps up to date. 1. What are some specific examples of successful DevRel strategies mentioned in the document? 2. How does the DevRel team balance internal and external activities to improve product awareness and adoption among developer communities? 3. What are some ways in which non-DevRel staff can contribute to DevRel initiatives and support the success of the DevRel team?