Developer Relations as Developer Success

Freshness Warning
This blog post is over 2 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

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.
Tyranny of Outcomes (Aug 19)
An extreme focus on outcomes can have an undesired effect on product teams.
The Trap of The Sales-Led Product (Dec 10)
It’s not a winning way to build a product company.
The Hidden Cost of Custom Customer Features (Dec 7)
One-off features will cost you more than you think and make your customers unhappy.
Domain expertise in Product Management (Nov 16)
When you're hiring software product managers, hire for product management skills. Looking for domain experts will reduce the pool of people you can hire and might just be worse for your product.
Strategy Means Saying No (Oct 27)
An oft-overlooked aspect of strategy is to define what you are not doing. There are lots of adjacent problems you can attack. Strategy means defining which ones you will ignore.
Understanding vision, strategy, and execution (Oct 24)
Vision is what you're trying to do. Strategy is broad strokes on how you'll get there. Execution is the tasks you complete to complete the strategy.


What I'm Reading


Adam Kalsey

+1 916 600 2497


Public Key

© 1999-2023 Adam Kalsey.