Axa Assurance Maroc - Insurer Innovation Award 2024
How To Report on Community Connections Without Being Creepy About It
1. How to “report” on community
relationships without being
creepy about itSarah Thiam
DevRel Program Manager
Microsoft
@truckerfling
PRESENTATION WARNING
THERE MAY BE SOME
INTERACTION REQUIRED
Image source: https://www.boredpanda.com
2. DevRel reporting
can be creepyneeds to be sensitive
Image source: https://theloganschool.org
@truckerfling
4. Your take-homes
1x Thought process for building your own
DevRel reporting program
1x My learnings, so be warned!!!
1x What other DevRel professionals think
Enter “sli.do” in your web browser
Key in code #6076 Live Polls
1x 1x 1x
156820
362832
236489
@truckerfling
8. 1. Learn
2. Act on
feedback
3. Optimise
See what others think!
pinned tweet on
@truckerfling
@truckerfling
The not-so-final product
9. Thank you! Happy building
Image source: https://giphy.com/explore/ikea-furniture
Sarah Thiam
DevRel Program Manager
Microsoft
@truckerfling
Editor's Notes
Welcome, day 2 of devrelcon
Here’s my talk about How to Report on Community Connections Without Being Creepy About it
My name is Sarah Thiam, a DevRel Programs Manager and a Singaporean.
More on that in a bit.
Today my talk is going to be about the thought process I encountered when building a reporting program for a devrel team. Hence, the Ikea character over here to kinda be thematic about it.
Firstly, how many of you are speakers here, how many of you edited your slides after seeing all those amazing talks yesterday?
Yeah me, I realized memes and tweetable one-shot slides are the way to go.. So..
To setting some context, let me DISMANTLE my talk’s sentence a litle
Mary Thengvall talked about how devrel faces this reality of needing to show business value and proposed a concept of “devrel qualified leads”
Now we each have our own version of this in DevRel, call it a lead or call it a community connection or call it an influencer
We want to be able to show the impact we’ve made
Let’s double click into the format of reporting and the considerations behind it
Your stakeholders might ask you “do you have a list of top community contacts you keep track of?” “show me some quotes or conversation to prove the improved favorability with our product”
Do you store these names in a database? Do you flash up the twitter DM of a really good quote saying “your devrel team made the technology so much better!”?
However, as a program manager I believe in the importance of programs and process to lend substance to the work we do and to scale it. The important difference is that – as I’ve learnt – devrel is a very different nature of industry from most and therefore devrel reporting NEEDS TO BE SENSITIVE.
A little about me, in case you might wonder what does a Programs addition to the role title mean?
As a program manager, we cover strategy, thinking about scale and adoption of advocates content
We also create processes with intent to streamline and optimize advocates day-to-day work
And one of the processes I was tasked with on our advocates team, was to come up with a process and format to capture community connections and demonstrate our team’s impact
Which had led me to this talk, to share my personal learnings with you on how to design a similar reporting function that works for YOUR team.
3 mins
The first step is to listen.
This goes back what we said earlier about reporting in devrel being tricky because you’re dealing with human connections.
So any process to do with it, needs to have a lot of empathy and open-mindedness
So when there was hesitation for a way to report on devrel, we asked the team “what are your biggest concerns”
And to us, these advocates are out in the field and owning these relationships so if anything, this reporting process needs to prioritize their comfort with it
And what we heard was to prioritize Privacy and Authenticity.
The second step is to Act on Feedback. Take it seriously and show visible action to respond to it.
It’s like the value of product feedback. This creates trust from advocates to see a program built for them, by them and will be something they are more willing to use.
I said more.. Not totally.
So we came up with two baseline boundaries for our reporting process.
The last step is to optimize.
Now that those baselines are in place, how do we grow the reporting program?
How can we make it better now that it’s headed in the right direction?
So for privacy, we shifted towards community altogether
And for being authentic, we shifted towards being more learnings-focused. So reporting’s value is directly tied to improving dev community engagement and helps humanize a reporting process that enables advocates to remain authentic in their outreach to communities.