Creating the DevRel identity for your company
summary
Build a world-class developer offering by defining inputs (leadership structure, position in org, community surface) and outputs tied to business metrics: create content first to grow community, align OKRs across product/marketing/engineering, use friction logging to surface and remove blockers, and track how many subscriptions directly trace back to DevRel work. Claims come from two years scaling a program at Envision, include spotting developer qualified leads, relieving product thresholds (thousands blocked by one missing feature), and measuring DX by time from no exposure to something meaningful on screen.
AI-written summary · about
chapters (8)
- 0:00Introduction to DevRel identity
- 2:06Bootstrapping a DevRel program
- 3:32Understanding leadership dynamics
- 7:08Developer persona and inputs
- 9:33Balancing shared value and competition
- 12:00Output frameworks for DevRel
- 16:15Principles for solid DevRel output
- 19:03Measuring DevRel success
related talks
26mWhy you need a DevRel team for your API
29mIntroducing the Developer Relations Foundation
50mDevEx on Steroids: 5 Techniques to Scale Developer Experience
42mBuilding DevX Teams, my story
47mTransforming Developer Experience: A Tale of Recovery & Innovation
41mDevX & Product-Led Growth: how they enable each other & your dev community seamlessly
26mScaling Better Software Delivery: A Framework for Dev Enablement Through DevRel and Outreach
30mA Founder's Perspective on Developer Experience: Trends and Data