Developer Relations (DevRel) is commonly tasked to drive growth and success of developers using their company's product. Of course, coming up with reasons why developers should adopt their product is necessary to deliver an effective message. But wouldn't it also be healthy to put attention on why they may NOT adopt?
I am just brainstorming here, but the following list captures reasons I believe developers may not adopt a product.
It is not possible for a developer to adopt or use a service if they have never even heard of the company or product.
Different from being unaware, this means the developer has only a vague or misinformed idea of company or product.
The developer does not perceive the relevance of company or product.
The developer's perception is that there is too much risk to engage with company or product. This could be due to not trusting the overall industry the company represents, or company/product too new in market.
The developer had (or heard of) a bad experience with product or company.
The developer may had initial interest, but the process to adopt or get engaged was too complex or confusing.
The developer has interest but considers cost of product or investment in time/resources a barrier to continue. Competitors appear (or are) less expensive.
Despite possibly being the right fit for a developer, how the developer learns about the company or product did not impress enough to invoke active interest.
While the developer may personally like the company or product, the perception (or reality) is that no adoption could take place due to constraints/policies of organization developer works for.
I do not claim the above is an exhaustive list, but is it a good starting point for discussion? Imagine if each DevRel carefully considered each reason not to, and came up with a plan to turn things around?
If you have other reasons why developers may not adopt, please share!
Photo by Anna Shvets: https://www.pexels.com/photo/woman-with-hands-on-her-face-in-front-of-a-laptop-4226215/