Why Developer Advocacy programs should consider working with partners

One of the goals of many developer advocacy programs is to reach more new developers. One approach that I leveraged when I was at Appery.io and we leverage even more at IBM Developer is working with partners.  In this blog post I want to share a few reasons why working partners has benefits.

We work with organizations such as Women Who Code, Hacker Dojo, The Den and others. These organizations have their own vibrant developer communities. We also work with developer companies such as Twilio, Slack, Cloudinary, Dashbot, JFrog and others. These companies have their own vibrant developer communities.

There are a number of factors why we like working with partners.

First, and probably the most important – working with partners and external communities allows us to provide developer education to developers who we probably wouldn’t reach otherwise. At the same time, the partner is able to tap in our growing developer community. This has a lot of value to both organizations. A one-off event is probably fine but we like to build a relationship with these organizations. We try to be consistent and host a monthly event. If one event a month is too often, you can try to do once every two month. Event frequency is really up to you.

Second, when we work with developer companies, we like to show developers a solution that shows how technologies from both companies can work together. There are a number of benefits here. First, an application usually consists of many different technologies (open source, various companies, etc). So this shows more of a real world example. If you can show a complimentary solution that leverages both technologies, that’s extra credit. For example, if you are building a chatbot powered by Watson, then you can show how to deploy it to Slack. Second, it shows more credibility and openness. No one wants to see technology from the same company over and over again.

We also work with companies/solutions that can be our competitors.  We are not afraid of this and in fact this is probably one of the best partner events we can host. Every framework, solution or platform is a little bit different and has its pros and cons. We also know that developers are very smart. We want developers to go with a solution that best solves their problem. And if it’s not a solution from us – that’s absolutely fine. When someone tells us they went with a different solution, we always want to know why. This is incredibly important feedback and we take back to the product teams.

Third, we like supporting, sponsoring and giving back to organizations that do a lot of good in the community (for example Women Who Code).

Fourth, hosting an in-person event is hard. There is a lot of pre-event work and of course you need to have a number of people supporting the the actual event. When we work with an organization such as Hacker Dojo, we outsource event management and execution to them (and they do it very well) and we only provide content. It works the other way around too.

Last but no least, partners events are just fun!

The actual type of an event that you do with a partner can be virtually anything. It can be an in-person event, it can be an online event but also a joint blog post or a tutorial. If you want to learn more about content, read my blog post about how content creates content.

We would love to partner with more companies – just let me know!

Photo by Christian Fregnan on Unsplash

One thought on “Why Developer Advocacy programs should consider working with partners

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.