Measuring your Developer Experience Journey
summary
A repeatable developer journey map breaks onboarding into discovery, evaluate, learn, build and scale, and ties each stage to concrete metrics: SEO hits and GitHub/StackOverflow signals for awareness, registration→integration conversion for activation, API calls or product-specific monthly active user definitions for activity, and referrals/PR for retention. Practical tools include friction logging, surveys, beta tests and CRM funnels (HubSpot/Marketo/Salesforce). A worked example finds registration walls and broken API keys; observed overall conversion rates around 2% conversion, showing where fixes deliver measurable lift.
AI-written summary · about
chapters (13)
- 0:00Introduction and setup
- 1:45Why measure developer journey
- 3:10Developer journey map explained
- 7:05Developer relations playbook
- 10:14Aligning with corporate goals
- 13:19Developer relations goals
- 16:47Friction points in developer journey
- 18:53Friction logging examples
- 24:48Measuring what matters
- 26:51Stages of the funnel
- 28:14Call to action metrics
- 33:12Conversion rate analysis
- 34:33Key takeaways and closing
related talks
25mCreating Great Developer Experiences with Metrics and Automation.
39mDeveloper Experience: How to Conquer the Hearts of Developers
35mBuilding Effective Developer Experience
24mHow to make your API Platform easy for Developers to Adopt
22mA CEO's perspective on dev rel, dev experience and ROI
15mKeynote: Creating a Holistic Developer Experience
50mDevEx on Steroids: 5 Techniques to Scale Developer Experience
30mA Founder's Perspective on Developer Experience: Trends and Data