The document outlines a developer relations strategy led by Amir, focusing on the importance of developer relations for effective engagement on the Slack platform. Key areas include partnerships, advocacy, and content, with a successful track record of 17k integrations installed 3.6 million times. Learnings emphasize segmenting developers, valuing key partners, and measuring engagement effectively.

1. Developer Relations strategy

2. Hi! I’m Amir (@ashevat).

3. Agenda:
1. Why Developers
2. How we do DevRel
3. Stats to date
4. Learnings

4. Why Developers

5. Why do Developer Relations?
In more than 90% of the use cases
you do you need Developer
Relations.

6. Why do Developer Relations?
We started out without DevRel
and found out we need one.

11. What can you do with the Slack Platform?

12. How we do DevRel

13. Dev Tools Partnership Advocacy Content & Community
Mission: Best in class developer
tools and experience for the
Slack Platform
Mission: Top partners releasing
quality and popular Slack apps.
Mission: Scale our reach with
content and community
engagement
Slack Developer Relations Team

14. Inspire
Educate
Enable
Feedback
Developer
Engagement Model

15. Have API Key
Building
Published
Installed
Used
Interested
Dev
Funnel
User
Funnel

16. How we do DevRel
70% of our focus is partnerships

17. How we do DevRel
We focus on the funnel of developers and
partners.

18. Stats

19. To date,
17K integrations have been
installed 3.6M times

20. What does a new platform feature usage look like?
Events API - used by more than 400
developers and installed on 30k teams.

21. Review process
Only 2% pass the review the first
time.

22. Lessons Learned

23. ● Segment your developers
● Work the breadth and depth
● Focus on high value developers/partners
● Measure the right thing
● Advocacy Vs. Evangelism
● Where you are in the org matters
● Where the $$ comes from matters
● Always think FIIFM for the developer
Lesson learned

24. https://www.flickr.com/photos/124247024@N07/14090438714/

25. https://www.flickr.com/photos/jdhancock/8671399450/

26. Yeah!
We did it!

27. Botness

28. Thanks!
For more information go to: slack.com/info