Successful DevRel No Matter Your Org Chart ![rw-book-cover](https://i.ytimg.com/vi/Rd-_Au7igJ8/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=&rs=AOn4CLC2sRgGPskL1VX9gxdemapKIHR3dw) ๐Ÿ”— **Source:** [Successful DevRel No Matter Your Org Chart](https://www.youtube.com/watch?v=Rd-_Au7igJ8) > [!note]+ Document Notes > tags: [#developer_relations, #career_growth, #open_source, #community_management, #metrics, #sales, #marketing, #developer_experience] > Author: Barrett Sonntag > Source: [YouTube - Developer Relations Talk](https://www.youtube.com/watch?v=Rd-_Au7igJ8) > Reference: [Time Stamps and Summary] > date created: 2024-11-14 > > # Title: Successful DevRel No Matter Your Org Chart > <!-- deep-read:sections start --> ## Table of Contents: - [๐Ÿ“ Summary](#-summary) - [๐Ÿ“– Main Content](#-main-content) - [๐Ÿ—’๏ธ Notes](#๏ธ-notes) - [๐Ÿ“– References](#-references) - [๐Ÿ—ฃ๏ธ Paraphrase](#-paraphrase) - [๐Ÿ“ฐ Newsletter](#-newsletter) - [โœ… Action Items](#-action-items) - [๐Ÿงช Hypotheses](#-hypotheses) - [๐Ÿ“Š Methodology](#-methodology) - [โ“ Questions](#-questions) - [๐Ÿ”ฎ Future Research](#-future-research) - [๐Ÿ’ก Implications](#-implications) - [๐Ÿง  Learning Styles Assessment](#-learning-styles-assessment) - [๐Ÿ“Š Accessibility Assessment](#-accessibility-assessment) - [๐ŸŒ DEIB Assessment](#-deib-assessment) - [โœ… Logical Validity](#-logical-validity) - [๐Ÿ” DARVO Analysis Prompt](#-darvo-analysis-prompt) - [๐Ÿ” SEO Evaluation](#-seo-evaluation) - [๐ŸŽฏ Conclusion](#-conclusion) ## ๐Ÿ“ Summary: Barrett Sonntag's talk explores strategies for navigating the varied organizational landscapes of Developer Relations (DevRel). Success hinges on adaptability, aligning DevRel goals with overarching business objectives, and fostering impactful community engagement. The session offers a roadmap for DevRel professionals to measure their impact, work cross-functionally, and thrive amidst organizational change. ## ๐Ÿ“– Main Content: ### ๐Ÿ—’๏ธ Notes #### [00:03](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=3) **Adapting to Organizational Structures** - DevRel functions differently across marketing, product, and open source contexts. - Misalignment with leadership's understanding of DevRel can risk its positioning as a cost center. #### [02:05](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=125) **Pragmatism and Business Acumen** - Demonstrate technical capabilities and pragmatism to establish credibility with leadership. - Avoid rigidly defining DevRel roles; flexibility in addressing organizational problems enhances trust. #### [06:01](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=361) **Enhancing Developer Experience** - Aim to reduce "time-to-hello-world" to improve onboarding. - Facilitate "time-to-delight" metrics to ensure developers derive satisfaction early in their journey. - Focus on affordable engagement strategies like hackathons or showcasing customer feedback. #### [08:01](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=481) **Managing Community and Marketing** - Define clear community metrics (e.g., user retention, time-to-first-API-call). - Guide issue discussions and backlogs in GitHub to foster productive community contributions. #### [11:48](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=708) **Aligning Marketing with Community Engagement** - Collaborate with sales to focus on customer advocacy and case studies. - Generate community-driven content to amplify user success stories. #### [13:45](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=825) **Revenue and Partnership Alignment** - Build healthy ecosystems that align customer and partner goals to ensure mutual benefits. - Avoid pitfalls of misalignment as seen in historic Facebook-Zynga conflicts. #### [17:43](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1063) **Open Source Contributions** - Develop pipelines from open source communities for recruiting skilled developers. - Proactively maintain open-source projects with onboarding paths for contributors. #### [19:27](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1167) **Adapting to Change** - Embrace flexibility in organizational KPIs and assess your alignment with shifting company goals. - Evaluate company maturity and developer community needs before transitioning roles. #### [22:50](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1370) **Understanding Developer Incentives** - Clarify how developers benefit financially from your platform and resolve potential conflicts. - Identify and amplify successful customers to model effective use of your product. #### [24:37](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1477) **Balancing Job Transitions** - Allocate time for job-seeking while remaining engaged in your current role. - Regularly reconnect with users to stay grounded and motivated. #### [28:16](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1696) **Supporting Sales Without Losing Focus** - Use developer empathy to design assets that align technical details with sales needs. - Build reference architectures and scalable solutions for demo purposes. #### [30:20](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1820) **Community-Centric Open Source** - Emphasize bottom-up strategies in open source contexts to support community adoption. - Adapt content to prioritize user-generated contributions and advocacy. #### [34:16](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=2056) **Product User Happiness** - Increase customer retention by focusing on user satisfaction and integrating community feedback. - Overcome attribution challenges for non-revenue APIs by linking ecosystem health with broader business goals. ### References: - [YouTube - Developer Relations Talk](https://www.youtube.com/watch?v=Rd-_Au7igJ8) - Hosted by Merlin on insights into Developer Relations. ## ๐Ÿ—ฃ๏ธ Paraphrase: 1. *Original*: "If leadership doesnโ€™t understand what you do, they may see you as a cost center." - *Paraphrase*: Leadership misalignment can cause DevRel to be viewed as a non-essential expense. 2. *Original*: "Reorganizations happen, and your career at a company is just one chapter." - *Paraphrase*: Organizational changes are inevitable; view each role as part of your career growth. ## ๐Ÿ“ฐ Newsletter: **Navigating the Many Faces of DevRel** Developer Relations thrives on adaptability and measurable success. Whether integrated with marketing, engineering, or open-source teams, DevRel professionals must align their efforts with business KPIs to showcase impact. Insights from Barrett Sonntag's session reveal practical strategies for balancing community engagement, leadership expectations, and organizational change. [Watch the full talk](https://www.youtube.com/watch?v=Rd-_Au7igJ8). ## โœ… Action Items: 1. Assess DevRel KPIs for alignment with business priorities. 2. Strengthen open-source contributor onboarding processes. 3. Develop customer success content highlighting high-quality product use. 4. Foster collaboration between DevRel, marketing, and sales teams. 5. Advocate for transparent metrics to demonstrate DevRel's tangible value. ## ๐ŸŽฏ Conclusion: Barrett Sonntag's insights illuminate the challenges and opportunities of Developer Relations across organizational contexts. His practical advice helps DevRel professionals navigate shifting structures, align with business goals, and maintain ethical, impactful practices. Short Summary for [Successful DevRel no matter your org chart](https://www.youtube.com/watch?v=Rd-_Au7igJ8) by [Merlin](https://merlin.foyer.work/) Strategies for Successful Developer Relations Across Different Organizational Structures and Understanding Your Value. [00:03](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=3) Success in Developer Relations requires adapting to different organizational structures. [02:05](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=125) Focus on demonstrating pragmatism and business acumen in Developer Relations. [06:01](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=361) Enhancing Dev experience impacts retention and community engagement. [08:01](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=481) Managing developer community and marketing effectively requires clear KPIs and engagement strategies. [11:48](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=708) Enhance marketing efforts by improving community engagement and sales collaboration. [13:45](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=825) DevRel success hinges on aligning partner and customer incentives for revenue growth. [17:43](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1063) Effective management of open source funding and community relationships is crucial for success. [19:27](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1167) Adapt to organizational changes for career success. [22:50](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1370) Understanding developer incentives and success to enhance API platform engagement. [24:37](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1477) Navigating job transitions while remaining engaged in your current role is crucial. [28:16](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1696) A developer experience role can effectively support sales without losing technical focus. [30:20](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1820) DevRel success varies by organization, highlighting community-centric approaches in open source. [34:16](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=2056) User happiness with products leads to increased customer retention and revenue. --------------------------------- Detailed Summary for [Successful DevRel no matter your org chart](https://www.youtube.com/watch?v=Rd-_Au7igJ8) by [Merlin](https://merlin.foyer.work/) Strategies for Successful Developer Relations Across Different Organizational Structures and Understanding Your Value. [00:03](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=3) Success in Developer Relations requires adapting to different organizational structures. - Understanding how Developer Relations operates in various businesses helps assess your own company's approach and goals. - Communicating effectively with leadership about your role can mitigate misunderstandings and position Developer Relations as a valuable asset. [02:05](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=125) Focus on demonstrating pragmatism and business acumen in Developer Relations. - Emphasize the importance of balancing developer experience with business goals to build credibility. - Navigate challenges by taking ownership of issues, regardless of job title, to foster trust with leadership. [06:01](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=361) Enhancing Dev experience impacts retention and community engagement. - Creating evangelists among users boosts product visibility and retention, leading to positive developer experiences and feedback. - Cost-effective strategies, like engaging engineers with customer feedback and managing open source contributions, foster community without high expenditures. [08:01](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=481) Managing developer community and marketing effectively requires clear KPIs and engagement strategies. - It's crucial to determine how to interact with the community on platforms like GitHub, including issue discussions and backlog management. - Marketing roles in developer relations should focus on measurable KPIs like community-driven content and its impact on sales conversions. [11:48](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=708) Enhance marketing efforts by improving community engagement and sales collaboration. - Focus on creating high-quality materials that showcase your product and support existing customers' needs. - Collaborate with sales to expand within accounts, fostering community advocacy and encouraging customer content creation. [13:45](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=825) DevRel success hinges on aligning partner and customer incentives for revenue growth. - Creating a healthy ecosystem can expand market awareness and drive product adoption, impacting revenue positively. - Misalignment in incentives, as seen in the Facebook-Zynga case, can undermine partnerships and harm customer experience. [17:43](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1063) Effective management of open source funding and community relationships is crucial for success. - Developing a recruiting pipeline from the open source community can attract skilled contributors aligned with your organization's tech needs. - Building strong relationships with maintainers and contributors is key to fostering collaboration and ensuring the project's sustainability. [19:27](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1167) Adapt to organizational changes for career success. - Demonstrate flexibility and align with new KPIs and goals of the organization to remain valuable. - Conduct thorough research to assess the company's culture and community needs before pursuing opportunities. [22:50](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1370) Understanding developer incentives and success to enhance API platform engagement. - Investigate how developers monetize their work and align it with the company's financial goals, identifying any potential conflicts. - Identify successful customers using the product to provide models of high-quality engagement and assess the company's maturity in the market. [24:37](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1477) Navigating job transitions while remaining engaged in your current role is crucial. - Utilize time boxing to balance job-seeking activities with fulfilling your responsibilities to the community. - Maintain connections with customers and colleagues to stay motivated and grounded in your current position. [28:16](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1696) A developer experience role can effectively support sales without losing technical focus. - Understanding the unique challenges faced by developers in large organizations enables targeted solutions. - Creating empathetic and detailed assets helps bridge the gap between technical requirements and sales efforts. [30:20](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=1820) DevRel success varies by organization, highlighting community-centric approaches in open source. - Sales engineers often face pressure for high-volume demos, leading to a need for balancing quality and efficiency in development. - The approach to DevRel differs in open source communities, focusing on community engagement rather than traditional revenue-driven strategies. [34:16](https://www.youtube.com/watch?v=Rd-_Au7igJ8&t=2056) User happiness with products leads to increased customer retention and revenue. - Happier users are more likely to pay more for products and expand their usage. - Establishing value attribution in non-revenue generating APIs is challenging but essential for ecosystem health. <!-- deep-read:sections end --> [[3. Resources/Readwise/Full Document Contents/Articles/Successful DevRel No Matter Your Org Chart|Full Document Contents]] ## Highlights - so indeed I'm here to talk to you about how you can be successful everal no matter where in the organization you fall now I have 25 minutes to cover a lot of different organizational scenarios so I apologize in advance for the lack of possible Nuance in some of these uh but it's meant to be a conversation starter and to give you all a map of the ways that Deo operates in different businesses so that you can better assess how your own company might develop and if you're a job Seeker looking at places where you might want to work you can understand the kind of ways that will be measured the kind of goals that people will hold you accountable to and so on because devel is not singularly defined we we know this it's something that comes up develon over devalon and is a continuous conversation throughout the community and for most of us that's a good thing it means that you aren't put in a specific box and it means that you as a talented individual professional can flex and use and you have scope to change roles and uh do different aspects of the job in ways where you can contribute to the organization best but it can be harmful because if the people who you roll up to your your sea level your exec Suite you're bored don't quite understand what it is that you do or they have a mental model of what you're supposed to do that doesn't match what you do then you can be put in a risked position um and the funniest and uh oh part of this slide is if your boss thinks that you are lighting money on fire that's when things get really tricky is when not only are you this ill understood in this ill understood position you are also a cost center and so in times of stress particularly Financial stress on an organization that mismatch of understanding can get particularly bad and can constitute risk for you in your role so here's how you can think about ways to drisk yourself in this position um I've learned a lot along the way about what works and what doesn't as organizations change because I have been in pretty much every organization um at Pine Cone we are in marketing at slack I was in product at Twitter in sales inbd at Facebook and engineering and then at some startups that I both worked at and consulted for devl wasn't yet part of an organization because in a 15 person company you're not necessarily thinking about all that stuff yet so I have some tips about how you can think pragmatically about the value that you bring to an organization and also some ways that you can sus out whether an organization is right for you in the interview process everything I'm about to say is a variation on this theme you need to demonstrate that technically capable customer focused and above all pragmatic and we're going to talk a lot about unpacking what pragmatism means and looks like and how you balance business Acumen and pragmatism with the feeling of devil because we're all here to do right by developers we want to improve developer experience we want to serve communities that we're a part of and we want to build cool things together and sometimes that can feel at odds with business and sometimes it doesn't and so finding a way to make sure that everything sits right both with the business goals that you have because we all work for companies here and make it still feel like something that you are with your own value system excited to do every day that's that's the kicker um so top top priority is to make sure that leadership really trusts you in that business acument pragmatism so you want to avoid saying that something is not your job so for example if you're in a marketing org and you're struggling with top a funnel it's your problem even if you aren't sure about how exactly you're going to grow top of funnel and being a purist about what devell is or isn't supposed to do doesn't serve your credibility either internally or externally so before I get into this I also want to caveat that I am talking about how to navigate all this in a healthy organization if you are being asked to do something that you think is unethical like you're doing growth hacks to con your customers into giving you their credit card information earlier in the funnel or you're being asked to go on stage and tell lies or half truths about what is technically feasible or how your product works those are red flags you should get out it's not it's not a good thing but in a healthy and just evolving organization where organizations change these these rules can be can be helpful guidelines so I've just done a quick overview of the kpis that you're likely to be accountable to in different organizations the organizational risks that you are exposed to if you are not expressing pragmatism and the type of work that is likely to be seen as valuable so we'll talk about what pragmatism with soul looks like in each ([View Highlight](https://read.readwise.io/read/01k36v9y86frbahsds7wvf23ye))