Track everything, measure everything, it still won’t be enough
summary
Joined Flutterwave initially tracks everything—blog readers, conference signups, support on Quora/Stack Overflow/Twitter, social sentiment—but six months of raw metrics still fails to prove value. Team pivots: define one-line purpose ("work with engineers on early-stage products to offer delightful developer experiences"), set expectations and tailored metrics, report progress frequently, involve management, and build internal communication and QA loops for APIs. Result: measurable shifts into developer experience work—docs, API performance, and optimizations—that management accepts as business value.
AI-written summary · about
chapters (20)
- 0:00Introduction to talk
- 1:26Why tracking metrics matters
- 3:30Introducing the Flutterwave team
- 4:34Initial developer advocacy activities
- 6:41Realizing tracking alone isn't enough
- 8:05Attempting comprehensive tracking
- 9:31Management's unclear expectations
- 10:56Redefining team purpose and goals
- 12:20Setting clear expectations and goals
- 13:45Establishing meaningful metrics
- 14:48Importance of proactive reporting
- 15:50Key lessons learned at Flutterwave
- 17:13Tailoring solutions to your organization
- 17:56Learning from similar teams
- 18:38Establishing internal communication
- 19:41Prioritizing developer experience
- 21:04Learning on the job
- 21:46Evolution of the team's role
- 22:30Doing what works for your team
- 23:11Q&A session begins
related talks
29mNumbers, because metrics matter
33mBeyond developer productivity: what's next?
41mRethinking Measurement for High-Performing Teams
25mCreating Great Developer Experiences with Metrics and Automation.
06mLightning Talk: Metrics, How To Measure What Is Going On In Your Community
18mFrom developer productivity to engineering impact
34mProving and improving the value of your docs
01h 02mMeasuring Performance in Development Teams