An API that nobody knows about might as well not exist. I believe every API operation needs someone actively evangelizing its work, telling the story of what the APIs do and why they matter to the consumers who could benefit from them. Evangelism is not marketing fluff; it is the sustained, honest communication that connects the technical reality of an API to the humans who need it. I have built my whole career on the idea that APIs need advocates, because the best API in the world will fail if it is launched into silence. Investing in evangelism, content, and outreach is how an operation turns a catalog of endpoints into an adopted, valued part of the business. This is the work that keeps APIs from dying quietly on a shelf.
APIs Are Actively Evangelized
Policies
Developer Relations Program
Require that any API meant for real adoption is backed by a developer relations function responsible for supporting, advocating for, and growing its community of consumers. Endpoints and documentat...
API Outreach and Content
Require that an API is actively communicated through ongoing content and outreach, including blog posts, changelogs, and updates that tell the story of what it does and why it matters. An API launc...
Experiences
Advocacy
Advocacy is the experience of an API having someone in its corner, speaking up for its consumers and carrying their needs back into the operation. Developer relations, evangelism, and outreach are ...
Communication
Consistent communication about the production and consumption of APIs is critical for effective enterprise governance. APIs are inherently difficult to visualize, making it essential to invest in m...
Community
Community is the experience of an API having a living network of people who use it, support each other, and shape where it goes. A forum, a Slack, a set of active contributors, or just consumers wh...
