Slide 1

Slide 1 text

Proactive vs Reactive DevRel Strategies @jessicaewest, Algolia

Slide 2

Slide 2 text

“The best offense is a good defense”

Slide 3

Slide 3 text

However, defense is the not necessarily the best offense in DevRel

Slide 4

Slide 4 text

Who am I? Jessica West
 @jessicaewest
 @jesswest
 [email protected]
 jesswe.st

Slide 5

Slide 5 text

The shiny toy effect

Slide 6

Slide 6 text

The game of risk

Slide 7

Slide 7 text

Conferences

Slide 8

Slide 8 text

The game of DevRel

Slide 9

Slide 9 text

You need to: Stay technical Write content Manage events

Slide 10

Slide 10 text

If you aren’t proactive with your strategies, your team will fail.

Slide 11

Slide 11 text

I interviewed a few industry folks…

Slide 12

Slide 12 text

“We focused heavily on reactive work due to a lack of tools and resources to be more proactive.”

Slide 13

Slide 13 text

“… the DevRel team was not specifically being measured. Those were measurements we maintained and reported, but weren’t held accountable to.”

Slide 14

Slide 14 text

What do reactive strategies look like?


Slide 15

Slide 15 text

{re·ac·tive} : acting in response to a situation rather than creating or controlling it

Slide 16

Slide 16 text

Reactive Approach

Slide 17

Slide 17 text

Reactive Approach Engineering / Product … be experts with the API and be able to explain all features … create community projects … create high-quality apps and demos that show off the API … take support shifts once a month … contribute to the documentation …. collect product feedback Marketing … lead the charge on our technical content … review content for developer-friendliness … use their networks to promote content … use their networks to get attendance for our events … go to meetups and conferences in their areas of expertise … go events outside their area of expertise and serve in a mentoring capacity to others who are there … monitor the health of our developer brand and whether we’re creating enough goodwill in the community … know which conferences and hackathons to sponsor … manage and build key individual relationships in the community … help the company reach and win over developer influencers … get community members to share their projects … create and moderate places for the community to gather Sales / SE … create sales collateral … help outbound strategic accounts … participate in pre-sales activities … create upsell opportunities to customers they know Culture … own and enforce the code of conduct … help us hire a more diverse team Industry / External … know everything about their company’s API and their vertical(s) … be publicly visible, accessible and available (online and offline) … share what they’re learning back to the DevRel community …. do technical support for their API … have a firm grasp of emerging technologies … be embedded in communities other than their own … hold their company accountable to the community and the industry … speak to journalists and analysts

Slide 18

Slide 18 text

The problem: Oooo, shiny!

Slide 19

Slide 19 text

Evangelism? Advocacy? Community? Clown Juggling?

Slide 20

Slide 20 text

What if your company wants it all? Too much!

Slide 21

Slide 21 text

Budget cuts are real

Slide 22

Slide 22 text

What do proactive strategies look like?

Slide 23

Slide 23 text

{pro·ac·tive} : creating or controlling a situation by causing something to happen rather than responding to it after it has happened

Slide 24

Slide 24 text

You must define what DevRel means for your company

Slide 25

Slide 25 text

What is DevRel to you? Drop Ship Evangelism Code Advocate Community Champion All the above

Slide 26

Slide 26 text

Drop Ship Evangelism*

Slide 27

Slide 27 text

“Drop ship evangelism is a sign of a new team, one that may not know where to focus yet.”

Slide 28

Slide 28 text

“Many evangelism programs are still trying to prove themselves; its hard to have those 6-8 touch points with a drop ship way of running the program.”

Slide 29

Slide 29 text

“…only works when you have a big team that allows one person to focus on that travel and follow up. You need different functions of engagement (multiple touch points), email with blog post link”

Slide 30

Slide 30 text

Evangelism is a triangle In Words In Person In Code

Slide 31

Slide 31 text

3 C’s “If you don’t have a way to reach developers, your Developer Relations program isn’t worth much.” Community ◎ Code ◎ Content

Slide 32

Slide 32 text

Create code and content, the community will come.

Slide 33

Slide 33 text

“It’s the repetition [the multiple touch points] that gets developers to understand your product.”

Slide 34

Slide 34 text

Proactive Approach Define team quarterly objectives and deliverables Define individual contributor objectives and deliverables Retrospective on deliverables and metrics seen Iterate on approaches

Slide 35

Slide 35 text

Retrospectives

Slide 36

Slide 36 text

Iteration and Adaptation

Slide 37

Slide 37 text

We are failing each other and our companies without a proactive approach

Slide 38

Slide 38 text

Strategize your approach

Slide 39

Slide 39 text

{strat·e·gy} : a plan of action or policy designed to achieve a major or overall aim

Slide 40

Slide 40 text

DevRel Bill of Rights A clear set of business goals A well-defined place in the organization A structured way to impact product or platform Open lines of communication to marketing The right tools specifically designed for the job Explicit ethical and social guidelines Support for building inclusive communities Clear distinction from sales engineering Ongoing resources for professional development Connection to a community of peers

Slide 41

Slide 41 text

Get buy-in or support from an executive

Slide 42

Slide 42 text

“For 6 months, the developer advocacy program reported into the CTO. They saw the value in travel, but had other primary concerns.”

Slide 43

Slide 43 text

“Due to the lack of realization in the hierarchy of needs, we weren’t able to address their chief concerns as they related to community engagement.”

Slide 44

Slide 44 text

Metrics vs impact * metrics don’t always tell the story of impact * impact is not necessarily a function of time or effort

Slide 45

Slide 45 text

+ + = Email Hack: sent to an email with a budget in subject line; receive the best value from the Taco Bell menu! Massive success!

Slide 46

Slide 46 text

+ + =

Slide 47

Slide 47 text

We must be militant in our strategies in order to succeed

Slide 48

Slide 48 text

British general Wellington: "I used to say of him (Napoleon) that his presence on the field made the difference of 40,000 men.”

Slide 49

Slide 49 text

“One must change one's tactics every 10 years if one wishes to maintain one's superiority …”

Slide 50

Slide 50 text

Napoleon would’ve killed it in DevRel

Slide 51

Slide 51 text

Taking calculated risks in DevRel can be strategic

Slide 52

Slide 52 text

Tech-Napoleans Strategies Early Twilio and SendGrid Hackathon Presence SendGrid accelerator support program Clarifai Champions GitHub Student Pack Algolia donations instead of swag Glitch pioneering different way of collaborative coding

Slide 53

Slide 53 text

The French Army recognizes three principles to be applied to operation of land forces at the tactical level

Slide 54

Slide 54 text

Freedom of Action

Slide 55

Slide 55 text

Unity of Effort

Slide 56

Slide 56 text

Economy of Means

Slide 57

Slide 57 text

TL;DR

Slide 58

Slide 58 text

Step 1: Proactive Approach Step 2: ??? Step 3: Profit (we keep our jobs!)

Slide 59

Slide 59 text

Summary Multiple customer touch points for success
 Buy in from at least one executive 
 Clearly defined strategy
 Iteration and Adaptaion
 Surround yourself with SMTP *Smart Motivated Talented Persons

Slide 60

Slide 60 text

Come hang at Karaoke with me later! Thank you!