September 10, 2020
Roundup of Self-Serve GTM Resources
In this post, Atlassian PMM Blake Thorne shares his required reading, listening, and watching list of self-serve go-to-market resources for ...
Has your technical developer content playbook gone stale? Are you pouring meaningful time and resources into technical content that goes unused or unnoticed? In a recent session with Heavybit members, GitHub Staff Developer Advocate and JAMstack Radio host Brian Douglas shared how he’s leveraged new platforms and new formats to help GitHub reach larger and more diverse developer audiences, and how to implement some of his tactics in your own developer content strategies.
Watch the recording of the session below, and read on to learn our key takeaways from the session:
Brian started GitHub Craftwork, which he calls the “minor league” of his content and curriculum ideas. He brainstorms and iterates on the substance of the content in the repo until it’s in a state where he’s ready to turn it into a talk or a Youtube video.
Having a pool of ideas that all live in one place makes it easier for you when an opportunity to lead a workshop or run a demo arises. Even better if it’s public; it makes it easier for others to approach you about generating content.
Since February of last year, Brian has been experimenting with or doubling down on:
You have to reinvent yourself, you have to reinvent what your properties look like, and you have to be able to adjust. So if you’re doing guest posts on other blogs and you’re not getting a lot of engagement, you have to take that and learn from it.
The one thing Brian loves about dev rel at GitHub is that his goal isn’t necessarily to get you to sign up for GitHub. His approach to dev rel is built on an assumption that you probably already have a GitHub account so instead he focuses on features and making sure that people are getting the most out of what GitHub has to offer.
When you’re an early-stage startup and yet to have a community, it’s still important to encourage folks to sign up. But that doesn’t mean you can’t adopt Brian’s approach. You want a healthy mix of pitches, and activities and content that are purely engaging or educational. Your intentions should always be to make the lives of developers easier, and that should carry out through all functions of your org, from product to marketing.
Brian’s job isn’t about him or increasing his follower count on Twitter. It’s not about the breadth of his reach but the depth of his impact. The more he engages existing community members, the more engaged they become, and eventually they’re lifted to a position where they’re creating content for him.
To help him be a better advocate, he sends people DMs and has a TweetDeck setup to follow conversations about different GitHub features so that he can jump in with helpful answers. He gives them all the information they need to become better than him at understanding GitHub.
GitHub already has a large number of users so there’s no need for Brian to chase after new leads but adopting this approach can also be helpful for teams that can only dedicate so much to GTM efforts. You’re likely to reap more from building stronger relationships with your existing users than you are from trying to get new people in.
Brian has a wealth of resources and content out there for you to learn more about his work at GitHub and journey as a dev advocate. Be sure to check out his Twitter, Youtube, and Twitch, and subscribe to updates from us to receive content like this!