Taking the next steps in dev rel metrics
summary
Introduces a concrete scoring system called impact hours that weights channels (meetings, live talks, blogs, docs) with a 90‑day time decay, uses issues and pull requests to measure OSS health, and ties impact growth to advocate seniority and ramp time for headcount cases. Demonstrates causal program measurement using the synthetic control method (R package) on time‑series billing/usage: sample shows +55 units per treated user, developer days yield >50% higher conversion likelihood, and CIO engagements produce multi‑hundred‑million USD business impact.
AI-written summary · about
chapters (5)
- 0:00Introductions and overview
- 2:19Measuring developer engagement
- 10:20Open source project health
- 12:48Causal inference and impact
- 30:00Q&A and closing remarks
related talks
41mRethinking Measurement for High-Performing Teams
20mHow to Communicate Metrics to Build Engagement
30mMeasuring the Impact of Community Events
25mRethinking measurement for high-performing teams
06mLightning Talk: Metrics, How To Measure What Is Going On In Your Community
39mDev Team Metrics that Matter
43mMeasuring Developer Productivity: The Good, the Bad and the Data
25mWhich metrics matter