Thanks for this perspective. I used to manage a DevRel team at AWS that was part of Product. As you rightly said, it has its advantages and disadvantages. When our group's budget was slashed, they could not justify keeping us on. There were too many places where our role overlapped with other roles and our metrics no longer aligned with Product's metrics, e.g. velocity of feature releases and product revenue.
Great example. And I'm sorry about that - it's too bad this story is so familiar. We have an upcoming piece on community that might be an interesting addition, our speaker covers goal + metric alignment to keep the community (often devrel related) effort funded + valued.
Thanks for this perspective. I used to manage a DevRel team at AWS that was part of Product. As you rightly said, it has its advantages and disadvantages. When our group's budget was slashed, they could not justify keeping us on. There were too many places where our role overlapped with other roles and our metrics no longer aligned with Product's metrics, e.g. velocity of feature releases and product revenue.
Great example. And I'm sorry about that - it's too bad this story is so familiar. We have an upcoming piece on community that might be an interesting addition, our speaker covers goal + metric alignment to keep the community (often devrel related) effort funded + valued.