Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

Developer Relations as Developer Success

Freshness Warning
This blog post is over 3 years old. It's possible that the information you read below isn't current and the links no longer work.

Most companies see Developer Relations as a marketing role. The job is to build awareness, recruit developers, and get product feedback.

Instead, the most important part of Developer Relations is to treat them like you do your Customer Success teams.

The primary role of your DevRel team is to enable customer outcomes. They are there to make the customer successful.

Creating developer tools, tutorials, and documentation are "one-to-many" enablers for customer outcomes. They are not targeted at a specific customer or specific outcome. These tools help developers discover self-success with your product.

One on one deep consulting with customers is another DevRel tool for customer success. By helping your customer understand what outcomes they are after and the best way to use your product to reach those, you’re enabling your customer to succeed.

Look at how you do customer success elsewhere in the company. What do you focus on? Onboarding? Adoption? Building competencies with your product? Do those same things as part of your developer relations.

Outreach, marketing, and developer evangelism are a part of Developer Relations. But the companies that are most successful with developers aren’t spending most of their time at events and doing content marketing. They’re spending most of their time making sure their developer customers are successful.

Recently Written

Mastery doesn’t come from perfect planning (Dec 21)
In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.
The Dark Side of Input Metrics (Nov 27)
Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.
Reframe How You Think About Users of your Internal Platform (Nov 13)
Changing from "Customers" to "Partners" will give you a better perspective on internal product development.
Measuring Feature success (Oct 17)
You're building features to solve problems. If you don't know what success looks like, how did you decide on that feature at all?
How I use OKRs (Oct 13)
A description of how I use OKRs to guide a team, written so I can send to future teams.
Build the whole product (Oct 6)
Your code is only part of the product
Input metrics lead to outcomes (Sep 1)
An easy to understand example of using input metrics to track progress toward an outcome.
Lagging Outcomes (Aug 22)
Long-term things often end up off a team's goals because they can't see how to define measurable outcomes for them. Here's how to solve that.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2024 Adam Kalsey.