Developer Relations in 2022 - Where I'm focusing
Published: 2022-01-21 15:32:54

---
title: Developer Relations in 2022 - Where I'm focusing
published: true
date: 2022-01-21 14:00:00 UTC
tags: 
canonical_url: https://cdoyle.me/posts/2022/01/devrel-in-2022-my-focus
---

![Three lego minifigs. They are wearing Slack logo tops, and holding mobile phones.](https://cdoyle.me/static/6a497616fa3384b45f7c2e4b26307b76/6a068/minifig.jpg "Three lego minifigs. They are wearing Slack logo tops, and holding mobile phones.")

Like many SaaS companies, the planning year at Slack runs from February to January, so we’re coming to the end of our planning process for the next 12 months.

One part of that process which is important in my role as Head of Developer Advocacy at Slack is [recruiting](https://slack.com/intl/en-ie/careers#openings) and headcount planning. I need to make an ask for a specific number of hires, justify that, start working with recruiting to hire those people, etc etc.

As part of that, I’ve been thinking a lot about what it is that I want the team to achieve.

Obviously I need to consider what we’re doing through the lens of the company, but like any good leader, I try to consider what each individual on my team will get out of it. What skills will they learn to advance in their career, what will be transferable to other roles, other teams and more.

I think these skills could serve as a good blueprint for many small DevRel teams, so wanted to share them.

So with that, let me talk about what Slack’s Developer Advocates will be doing this year.

## [<svg aria-hidden="true" focusable="false" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg>](#its-all-about-the-content)It’s all about the content

A big focus for us next year is _massively_ upping our content game. More video, more blog posts, maybe some other mediums we haven’t considered yet.

Towards the latter half of 2021, we started to spin up what we’d consider mid-length videos, that is longer than 5 minutes, but less than 15.

Here’s a great example by [Sandra](https://twitter.com/s_illiv), the most recent member of the team, who was speaking about using our App Home feature.

 <iframe src="https://www.youtube-nocookie.com/embed/wo2uyhk62eM" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" style=" position: absolute; top: 0; left: 0; width: 100%; height: 100%; "></iframe> 

Then there’s also blog posts like [this one](https://slack.com/intl/en-ie/blog/developers/socket-to-me) from [Jim Ray](https://twitter.com/jimray).

Whilst both of those example are very ”_you already know and have bought into the idea of Slack_”, we also want to start producing content which is more reflective of our amazing community of developers. At the end of the day, our platform exists to help people get things done more easily in Slack, whether that’s [responding to incidents](https://incident.io), [managing their projects](https://workstreams.ai), or most importantly [bragging about your wordle score](https://twitter.com/chrishutchinson/status/1484230130465751043?s=20), so we want to talk about the interesting things that our community are making, and even things that _aren’t_ related to our APIs, but can still make your life easier, like offering a look at how we plan content, or build product, or launch features.

Here’s just a few of the things we want to tackle soon.

![A screenshot of a Figjam board, containing virtual stickies with ideas for content](https://cdoyle.me/static/a0c754476b8b8093abe349efc77cced1/6a068/devrelcontentplan.jpg "A screenshot of a Figjam board, containing virtual stickies with ideas for content")

## [<svg aria-hidden="true" focusable="false" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg>](#once-more-unto-the-in-person-events-dear-friends)Once more unto the in-person events, dear friends

I still think 2022 will be very heavy on digital content, but like other organisations, we’re keeping a close eye on what a return to in-person looks like, so there’ll likely be some hybrid events too.

We already have at least one major event on the books in the form of [TrailblazerDX 2022 this April](https://www.salesforce.com/form/event/tdx22-save-the-date/), but as with everything, it will depend on COVID-19 and how safely we can run an event at the multiple thousands scale.

As I say though, I don’t know that any large event will _ever_ be 100% in-person again. Hybrid is here to stay.

## [<svg aria-hidden="true" focusable="false" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg>](#one-message-many-mediums)One message, many mediums

But fundamentally, COVID or otherwise, I think DevRel is a multimedia discipline now, so DevRel teams should have experience / an interest in generating content across all sorts of mediums.

There are so many ways to help your community, and make your content accessible to a wide range of folks, regardless of where they’re based, or their style of learning. We’re not there yet, but we want to be a team that generates content for our whole community.

In a practical sense, I think that knowledge of how to produce content in multiple formats is a table stakes skill for a DevRel professional today. You don’t have to be a world class video editor, but the idea of learning to slice together some video content in iMovie/Premiere Pro etc shouldn’t terrify you. The same can be said of audio. Voiceovers, podcasts, virtual workshops all require you to be confident speaking into a microphone.

Similarly, you need to be confident in your writing. Blog posts, tutorials, even tweets. The written word is still important, no matter how much video or audio you pump out.

I think what’s going to be interesting is how much we could leverage short form video for technical content. If you look at the success other industries are having with the likes of Instagram Reels, YouTube Shorts and TikTok, I can’t believe that it’s not going to be a useful way to get developer facing content to a new audience.

For some examples of folks who I think are doing this well, I always look at what [GitHub](https://www.youtube.com/c/GitHub) and [Stripe](https://www.youtube.com/c/StripeDevelopers) are doing. [Michelle Mannering](https://twitter.com/MishManners), [BDougie](https://twitter.com/bdougieYO) and [Chris Trag](https://twitter.com/chris_trag) in particular from those teams are doing great stuff.

## [<svg aria-hidden="true" focusable="false" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg>](#staying-close-to-the-product)Staying close to the product

In a post last year, [Getting better at Developer Relations](https://cdoyle.me/posts/2021/04/getting-better-at-devrel), I spoke about the importance of being Developer Zero and working closely with Product Managers. I definitely still believe that to be true, and I’ve started to think more about how our team should balance that work with the content creation work.

![A circular flow chart describing what I consider the Advocate product life cycle](https://cdoyle.me/static/b2d27cfcd2b66153a795b6e4fd271528/d9199/content-and-feedback-cycle.png "A circular flow chart describing what I consider the Advocate product life cycle")

When I do, I envisage it as a circular thing, because each part of a Developer Advocate’s job is wholly dependent on the other. You cannot create value for your community if you’re not pushing your product team to build things that solve their problems, and you cannot get valuable feedback to bring to your product team if you’re not sharing ideas, sharing information and ultimately building a relationship with your community.

If you’re only ever pitching your product, then congratulations, you work in Sales and Marketing, and I wish you well.

If you’re only ever having interesting technical conversations with people that don’t teach you more about how people use your platform, then congratulations, you’re a well funded distinguished engineer, and I wish you well.

Developer Relations / Advocacy sits somewhere in the messy middle. We are neither engineers who talk in the abstract and write fancy algorithms all day, nor are we marketing/sales people. You need to be comfortable living in that grey area.

At Slack, we sit inside the Product Organisation, alongside the Platform Product Managers, so it’s easy for us to build and maintain these relationships. Wherever your team sits though, you should put in the effort, as they’re one of the most important partners you have.

## [<svg aria-hidden="true" focusable="false" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg>](#always-tighten-the-feedback-loop)Always tighten the feedback loop

So what is 2022 at Slack Developer Advocacy? It’s about iterating on the loop I mention above, making it **faster**. Ship **more** content, ship **better** content, ship platform improvements, ship ever increasing **value for our community** , because ultimately, it’s them we’re here to serve, not the other way around.

If you’re as passionate about these things as I am, and want to [join us](https://slack.com/intl/en-ie/careers#openings), I’m always looking to talk with great people. As I write this post, I’m actively looking for people in Europe, and hope to soon be looking for people in North America. So drop me a [DM on twitter](http://twitter.com/colmisainmdom), and let’s talk.