# Note 1: Title - The Developer Advocate's Guide to Addressing Product Friction - - - ## 📚 Metadata: - Author: theworst. Dev - Source: The Developer Advocate's Guide to Addressing Product Friction - Reference: [Link](https://theworst.dev/developer-advocates-guide-to-addressing-product-friction) - Tags: #productfriction #DXAudits #DX #developeradvocacy #feedback #frictionlogs #contextgathering #collaboration #consistency #valuedelivery #usecases #DevRel #ApolloPlatform - - - ## 📝 Summary: The article discusses the development of the DX Audits framework at Apollo to address product friction. The initial version of DX Audits faced challenges such as slow feedback loops, workload bottlenecks, and excessive reporting. However, it also brought benefits such as consistency, structure, and proof of impact through friction logs. The epiphany was realizing the wrong separation of concerns and modifying DX Audits for v 2, where audits are scoped to individual use cases. The four steps of DX Audits are Discover, Build, Report, and Follow Up. The process emphasizes context gathering, empathy, and consistent friction logging. DX Audits have positively impacted developer advocacy work at Apollo and become a standard collaboration tool. ## 📖 Main Content: The article details the journey of developing the DX Audits framework at Apollo, aiming to address product friction and enhance developer advocacy. The first version of DX Audits encountered challenges, including slow feedback loops, workload bottlenecks, and excessive reporting. Despite these hurdles, the framework demonstrated its value by introducing consistency, structure, and proof of impact through friction logs. The significant breakthrough came when the team realized that the initial version's separation of concerns was not optimal. This realization led to the evolution of DX Audits v 2, where audits are scoped to individual use cases. This modification allowed developer advocates to deliver value faster and surface actionable steps more efficiently. The four-step process of DX Audits comprises Discover, Build, Report, and Follow Up. During Discovery, developer advocates gather context about the use case they're auditing from various sources, ensuring a comprehensive understanding. In the Build phase, advocates experience the workflow and record their findings in friction logs, aiming to be empathetic and minimize assumptions. Reporting involves delivering feedback to relevant decision-makers promptly and proposing actionable steps to address friction points. In the Follow Up step, advocates work on action items and track progress, ensuring effective cross-team collaboration and tangible results. The article emphasizes the importance of context gathering, empathy, and consistent friction logging in the DX Audit process. These elements contribute to better understanding developer pain points and delivering valuable feedback to other teams. Overall, DX Audits have proven to be a valuable collaboration tool, positively impacting developer advocacy work at Apollo and benefiting multiple teams within the organization. ## 🔮 Future Research: - Explore the long-term impact of DX Audits on product development and user satisfaction. - Investigate the potential integration of AI and machine learning in automating the DX Audit process. - Conduct a comparative study of different feedback frameworks to identify the most effective approach. - Examine the role of empathy in reducing product friction and enhancing the developer experience. - Investigate the scalability of DX Audits for larger organizations and open-source communities. - Analyze the correlation between friction logs and customer retention and acquisition. - Explore the challenges and benefits of implementing DX Audits in different technology domains and industries. ## 🧪 Hypotheses: 1. A streamlined and scoped DX Audits process will lead to more efficient and timely resolution of product friction. 2. Developer advocates who embrace empathy during friction logging will produce feedback with higher impact and resonance. ## 💡 Implications: The research on DX Audits and its impact on developer advocacy and product development has several implications: 1. DX Audits offer a structured and efficient approach to understanding developer pain points and delivering feedback to other teams. 2. The v 2 modification of DX Audits, scoping audits to individual use cases, enables faster value delivery and enhances collaboration. 3. Emphasizing context gathering and empathy in the DX Audit process improves the quality and relevance of feedback. 4. DX Audits can be used as a valuable collaboration tool, benefiting multiple teams and contributing to product improvement. 5. The integration of DX Audits in developer advocacy practices can lead to enhanced user satisfaction and retention. ## 📖 References: 1. [The Developer Advocate's Guide to Addressing Product Friction](https://theworst.dev/developer-advocates-guide-to-addressing-product-friction) # Note 2: Title - Summary of DX Audits Framework - - - ## 📚 Metadata: - Author: theworst. Dev - Source: The Developer Advocate's Guide to Addressing Product Friction - Reference: [Link](https://theworst.dev/developer-advocates-guide-to-addressing-product-friction) - Tags: #DXAudits #productfriction #feedback #frictionlogs #contextgathering #collaboration #empathy #efficiency #DevRel #ApolloPlatform - - - ## 📝 Summary: The DX Audits framework was developed at Apollo to address product friction and enhance the developer advocacy process. The first version encountered challenges like slow feedback loops and excessive reporting, but it also brought benefits such as consistency, structure, and proof of impact through friction logs. The framework evolved into DX Audits v 2, where audits are scoped to individual use cases, leading to faster value delivery and improved collaboration. The four steps of DX Audits include Discover, Build, Report, and Follow Up, emphasizing context gathering, empathy, and consistent friction logging. DX Audits have positively impacted developer advocacy work at Apollo and become a valuable collaboration tool. ## 📖 Main Content: The DX Audits framework, developed at Apollo, was designed to tackle product friction and enhance the developer advocacy process. The first version of DX Audits faced challenges such as slow feedback loops, workload bottlenecks, and excessive reporting. Despite these hurdles, the framework demonstrated its value by introducing consistency, structure, and proof of impact through friction logs. The friction logs allowed advocates to track accomplishments and provide valuable insights to other teams. The framework underwent a significant improvement when the team realized the suboptimal separation of concerns in the initial version. This realization led to the development of DX Audits v 2, where audits are now scoped to individual use cases. This change allowed developer advocates to work independently, providing value in a much shorter timeframe. The DX Audits process involves four steps: Discover, Build, Report, and Follow Up. During Discovery, advocates gather context about the use case they're auditing from various sources, ensuring a comprehensive understanding. In the Build phase, advocates experience the workflow and record their findings in friction logs, aiming to be empathetic and minimize assumptions. Reporting involves delivering feedback to relevant decision-makers promptly and proposing actionable steps to address friction points. In the Follow Up step, advocates work on action items and track progress, ensuring effective cross-team collaboration and tangible results. The ## Links - [[Friction Logging Is the DevRel Equivalent of Code Review]] — the Discover-Build-Report-Follow Up audit turns observed developer friction into reproducible product feedback. - [[Repeated Workarounds Are Unfiled Bug Reports]] — contrasts an advocate-led audit with the passive friction evidence users leave behind in configuration. - [[The DevRel Show Episode 53 — Chris DeMars from TuxCare]] — supplies the same build-with-your-own-product ritual as a practical definition of internal advocacy. - [[3. Resources/MOCs/DevRel MOC]] — places friction discovery, reproduction, reporting, and follow-up inside the advocate's product-feedback role.