Avoiding the DevRel ROI Trap with Better Strategic Alignment

What’s the first question when a developer advocate meets a developer advocate?
What’s the first question when a developer advocate meets a developer advocate?

The endless search for the holy metric

What if KPIs are not *always* the answer?

In order to successfully prove the value of our work in a way that the company understands and sees as beneficial, we need to attach the main goals of the Developer Relations department to the goals that are shared by the company as a whole.
Source: https://www.marythengvall.com/blog/2020/12/14/first-understand-the-company-goals

The first rule of measuring DevRel ROI is tying DevRel goals to company goals. This may sound like common sense, but you wouldn’t believe how often people get this wrong. If your DevRel goals are not aligned with larger company goals, people will be hard pressed to recognize the value of DevRel activities. Without context, they won’t be able to connect the dots between what you’re doing and ultimate business outcomes. This makes it hard for other functions to get behind DevRel. And if the DevRel team doesn’t understand the importance of their role within the organization, they can get off course pretty quickly.
Source: https://openviewpartners.com/blog/measuring-the-impact-of-your-developer-relations-team/
@Ashley, if, by any chance you are reading this — Thank you!

A recipe for a perfect strategy

DevRel strategy = Company Strategy ∩ Developers’ Needs ∩ What developer avocados are good at
A perfect DevRel strategy recipe that’s strikingly reminiscent of Ikigai

One of the big dangers to any developer relations program is that it is so easy to try and do it all. The problem though with trying to do it all is that you end up being busy and doing nothing well.
Source: https://devrel.net/dev-rel/meet-cristiano-betta

DevRel strategy != Other people’s jobs, not advocating for devs’ needs, things not aligned with company strategy

Strategic alignment tools

OKRs helped us pick our battles and become active participants in the broader company strategy.

Real-world implementation of OKRs for DevRel

The order of steps during the planning session is essential. We first take into consideration the company strategy, and only then we try to map our skills and our knowledge about developers to it in order to come up with the right mix of activities.

Regular updates close the gap between the executives and teams.

How strategic alignment helped our DevRel

If culture eats strategy for breakfast, then strategy eats metrics for brunch.
If culture eats strategy for breakfast, then strategy eats metrics for dinner the night before. 😀

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store