The Developer Advocate's Guide to Metrics and Reporting ![rw-book-cover](https://res.cloudinary.com/theworstdev/image/upload/l_Gradient/l_text:Montserrat_64_black:The%20Developer%20Advocate's%20Guide%20to%20Metrics%20and%20Reporting,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 Metrics and Reporting|Full Document Contents]] ## Document Notes Abstract: This article provides a comprehensive guide to metrics and reporting for developer advocates. It outlines the importance of metrics and reporting, provides a framework for metrics, and highlights key metrics to track. It also provides guidance on the best practices for developing reports, how to identify and analyze trends, and how to use metrics to make improvements. The article also covers how to build an effective metrics dashboard, how to collaborate with other teams, and how to use metrics to inform strategies. Overall, this article provides a comprehensive overview of metrics and reporting for developer advocates, offering a valuable set of tools and advice for those in the field. Bullet List Summary: • Importance of Metrics and Reporting: - Metrics and reporting are essential for developer advocates to understand their impact and measure success - Metrics help teams to identify areas for improvement and to inform strategizing • Framework for Metrics: - Define metrics and goals - Establish an effective tracking system - Collect data for analysis - Identify and analyze trends • Key Metrics to Track: - Number of developers engaged - Number of products shipped - Number of open source contributions - Number of bug reports • Best Practices for Developing Reports: - Gather data from multiple sources - Analyze the data to identify trends - Use the data to inform strategies - Create reports in a visually appealing way • Building an Effective Metrics Dashboard: - Choose the right metrics - Automate data collection - Design the dashboard with visual appeal - Use the dashboard to identify trends • Collaborating with Other Teams: - Be open about data and metrics - Establish a system for data sharing - Create shared goals and metrics • Using Metrics to Make Improvements: - Analyze metrics to identify areas for improvement - Set goals and objectives - Monitor progress and track results - Use insights from metrics to inform strategies Paraphrased Paragraphs: Paragraph 1: Metrics and reporting are essential for developer advocates to understand the impact and measure the success of their work. Metrics can help teams to identify areas for improvement and strategize more effectively 1. What strategies can I use to build trust in the metrics I use to measure my success? 2. What metrics are generally trusted within a given team/company/industry? 3. How can I draw a clear line between my work and trusted metrics? This document explains the importance of metrics when it comes to developer advocacy. It outlines the different types of metrics, such as trusted and untrusted metrics, and the need to prove the connection between metrics and the impact they represent. It emphasizes the importance of finding metrics that represent the work of developer advocates, and warns against competing against other teams when it comes to metrics. Lastly, it stresses the importance of understanding how companies think about metrics and the value developer advocates bring to the company in order to be successful with metrics and reporting. > [!note]+ Document Notes > Abstract: > > This article provides a comprehensive guide to metrics and reporting for developer advocates. It outlines the importance of metrics and reporting, provides a framework for metrics, and highlights key metrics to track. It also provides guidance on the best practices for developing reports, how to identify and analyze trends, and how to use metrics to make improvements. The article also covers how to build an effective metrics dashboard, how to collaborate with other teams, and how to use metrics to inform strategies. Overall, this article provides a comprehensive overview of metrics and reporting for developer advocates, offering a valuable set of tools and advice for those in the field. > > Bullet List Summary: > > • Importance of Metrics and Reporting: > - Metrics and reporting are essential for developer advocates to understand their impact and measure success > - Metrics help teams to identify areas for improvement and to inform strategizing > > • Framework for Metrics: > - Define metrics and goals > - Establish an effective tracking system > - Collect data for analysis > - Identify and analyze trends > > • Key Metrics to Track: > - Number of developers engaged > - Number of products shipped > - Number of open source contributions > - Number of bug reports > > • Best Practices for Developing Reports: > - Gather data from multiple sources > - Analyze the data to identify trends > - Use the data to inform strategies > - Create reports in a visually appealing way > > • Building an Effective Metrics Dashboard: > - Choose the right metrics > - Automate data collection > - Design the dashboard with visual appeal > - Use the dashboard to identify trends > > • Collaborating with Other Teams: > - Be open about data and metrics > - Establish a system for data sharing > - Create shared goals and metrics > > • Using Metrics to Make Improvements: > - Analyze metrics to identify areas for improvement > - Set goals and objectives > - Monitor progress and track results > - Use insights from metrics to inform strategies > > Paraphrased Paragraphs: > > Paragraph 1: > > Metrics and reporting are essential for developer advocates to understand the impact and measure the success of their work. Metrics can help teams to identify areas for improvement and strategize more effectively > > 1. What strategies can I use to build trust in the metrics I use to measure my success? > 2. What metrics are generally trusted within a given team/company/industry? > 3. How can I draw a clear line between my work and trusted metrics? > > This document explains the importance of metrics when it comes to developer advocacy. It outlines the different types of metrics, such as trusted and untrusted metrics, and the need to prove the connection between metrics and the impact they represent. It emphasizes the importance of finding metrics that represent the work of developer advocates, and warns against competing against other teams when it comes to metrics. Lastly, it stresses the importance of understanding how companies think about metrics and the value developer advocates bring to the company in order to be successful with metrics and reporting. ## Highlights - As developer advocates, avoid becoming extensions of other teams by closely learning **metrics:** the different types you'll encounter and when to use them, which are trusted and untrusted, and how to build them effectively to support *your team's* goals. ([View Highlight](https://read.readwise.io/read/01gvxrmy45nbxbbe97ja0j9cbt)) - Examples of qualitative metrics are • Comments from feedback forms • Social media interactions • Direct feedback from community members that you record ([View Highlight](https://read.readwise.io/read/01gvxrnrz2a8h88v4bmrgr2ra1)) - Examples of qualitative metrics are • Comments from feedback forms • Social media interactions • Direct feedback from community members that you record ([View Highlight](https://read.readwise.io/read/01gvxrp6hzxc0mkh9vwvq2kerz)) - Examples of quantitative metrics: • Monthly active users (products, platforms, etc.) • Content quality (average time on page, bounce rate, average watch time for videos, etc.) • Content distribution (percentage of content covering specific topics, themes, personas, etc.) ([View Highlight](https://read.readwise.io/read/01gvxrpc37p850hmq6x8n53ddv)) - An example of a success metric is MAUs (monthly active users). ([View Highlight](https://read.readwise.io/read/01gvxrq3ff7br0k5t8ngerkn4t)) - A developer advocate's value increases as they build momentum by constantly working through this cycle because the work done in each step of the process positively impacts the next one ([View Highlight](https://read.readwise.io/read/01gvxrqqm943bekjczm6cm59cr)) - Developer advocates are force multipliers, internally and externally, and our internal impact is underrepresented in DevRel success models. ([View Highlight](https://read.readwise.io/read/01gvxrqzcnxzmp51zqv78m0gmz)) - **As developer advocates, we can do the one thing neither company nor community can do, exist in both worlds.** The actual value of developer advocacy is the context you gain by innately knowing the needs, frustrations, and joys of both sides of the more significant relationship, the one between the company and the community. The deeper we embed ourselves into each world, the more context we gain, becoming more effective. ([View Highlight](https://read.readwise.io/read/01gvxrrv1v93ca8eswb32txz69)) - I see Developer advocacy as similar to being a principal engineer. You work cross-functionally within a company and identify gaps and opportunities that impact the business (and, in our case, the community) using the context you've accrued from the internal and external relationships you've built. ([View Highlight](https://read.readwise.io/read/01gvxrt2q4z5j7spvr5j83ntyy)) - Note: The Developer Advocate's Guide to Metrics and Reporting provides guidance on how to measure and report on the work of developer advocacy. It explains the different types of metrics that can be used, how to build trust in these metrics, and how to ensure that the metrics are connected to trusted metrics that represent the value of the work. It also outlines the importance of proof of impact and how to successfully measure and report on the work.