How can we decide if we should introduce DevRel? The desicion is actually very easy to make.
** If the developer is a stakeholder **
Then you should incorporate DevRel. If not, then it isn’t necessary.
Stakeholders are entities that share interests directly or indirectly. If the establishment of good relationships with developers results in an interest in your company and your products, you can say that they are stakeholders.
For example, the following relationship may be considered.
We tend to think that product adoption is carried out rationally in businesses, but in reality, that is not necessarily the case. There are cases where products are chosen without careful examination and in a quantitative (emotional) manner such as because it is de facto, or it’s frequently seen, or it’s been recommended by friends. In other words, if a developer has a negative impression of a product, there are many cases where the product will not get adopted no matter how good the product is.
Nevertheless, it doesn’t mean that even useless products are good if you have a good relationship. We are talking about a good relationship on the assumption that the product is good. A good relationship relieves negative emotions and amplifies positive ones.
There was a time when Microsoft was considered a bad company. Currently, Microsoft’s reputation has improved significantly. However, there is still a portion of people that responds negatively to Microsoft’s actions. Twitter has restricted the use of their API many times, and got negative responses from developers each time. They have declared several times to improve their relationships with developers. However, it is not easy to improve the relationship that’s been damaged in the past.
On the other hand, there are companies that have successfully built good relationships with developers such as Apple, Google, AWS, GitHub and Unity. Their relationship with developers is built based on an already-existing, long standing relationship, and not something that was made just yesterday. Given that Twitter once had a good relationship with developers, we can say that DevRel is something easy to break but hard to built. This can be compared to trust. Just as you can not completely trust the people you met today, it’s difficult for companies and services to build DevRel.
However, the trust built up overtime will be beneficial in terms of awareness and recognition of service, share and community. It may be obvious how DevRel works as an advantage for companies in terms of differentiation from competition.
DevRel works well not only for services, but for companies as well. There are companies that are chosen even if people are presented with similar salaries and jobs. Further, there are companies that are selected even if their salary is less than that of other similar jobs. Conversely, there are companies that has to increase the salary posted in order to be picked. Where does this difference come from?
Outsiders know very little about the company’s inner workings. There are forums and sites that discuss this, but not many people trust it 100%. So what it comes down to, is the company’s branding towards developers. By becoming a successful brand , you will be able to enhance the recruitment process.
The foremost thing will be GAFA. Of course, the increase in salary is attractive, but if we’re simply talking about just salary, there could be other companies that can offer more. It is the power of branding that helps a company be chosen amongst all its competitors. It can be said that there is no reason for people to choose a Japanese company that does not brandoffer enough pay
It can be said that there is no reason to choose a Japanese company that does not have enough pay and branding.
Recently, it has become commonplace to publish APIs for any web services. This means that simply publishing the API has made it impossible to attract the developers. We’ve already gone beyond that phase. Documentation, tutorials, SDKs, and demo apps are the kind of things required today. Without such an environment, there would be no developers testing out the service.
Similarly, setting up a developer blog has become commonplace. In order to stand out, it is important to create content that meets the trend in time as well as company needs. It is not only ineffective when done halfheartedly, but also a complete waste of time. If you’re going to do it, do it properly.
If you believe that developers are stakeholders for your company, then DevRel is a must. That being said, if it’s done halfheartedly and not properly, then it adds extra cost and becomes a negative factor. If you’re going to do it, you should have a medium to long-term perspective and goal.
At MOONGIFT, we do consulting and outsourcing of DevRel. We will discuss DevRel work and strategies that works for your company specifically, and implement it. For any inquires regarding DevRel, please contact us.
You will receive news and updates about DevRel via email.