The purpose of this article is for us to surface any thoughts, comments, feedback and potential challenges so we can work through them collectively as a team. These are some recommendations which are all WIP and we can begin piloting some of these ideas and iterate as we go on.
Developer Channel Objectives
Initiative Announcements - As we grow and our initiatives continue to deliver stellar work, we need a platform to surface latest updates from the different initiatives and having them all on the brand channel becomes cluttered and impractical
Focused Community - Building a more focused channel which will cater to both the inner ethereum community and devs outside the ethereum space looking to enter, all of which will appreciate/engage with more technical content
- Important note: Balancing this channel to ensure there is content that is inviting and accessible to a non web3 developer audience will be key
2 way engagement - Allow a channel for not only CC’s to get involved in more technical conversations but also the developer community who are connected to our initiatives to have a channel to ask questions and seek help.
CC Candidates - Have an audience for People Ops to tap into when searching for potential new hires.
Leads for different Initiatives - Creating this focused community could result in future Incubatees or Status Studio enrolments
Bounty contribution - Encourage developers to contribute by working on bounties (both as part of bounty programs and advocacy program)
Community Value Exchange:
Why do I come here and not somewhere else?
What should I walk away from this channel having learned?
Information Content - While the main Status brand channel will still serve up informative content, potentially this could be the source of this content (ie. “StatusDevs” channel tweets out an Embark 3.2 announce and it’s RT’d by EthStatus channel) alternately it could be slightly more detailed announce catering for this more technical audience.
Education Content - With a more technical channel perhaps this is when the shift happens from moving Status Brand education content to be more focused on our values while the Status Dev channel becomes more focused educating you on the technical details of what the different initiatives are doing - ie. a detailed Whisper article
Inspiration - While inspiration around our values and how they are brought to life would be addressed on the main brand channel (EthStatus), this channel could inspire an inner ethereum community to what application of the technology could uncover, also providing community members with inspiration for their own projects ie. a detailed piece on extensions could inspire a DApp developer
Opportunities to contribute - We can post links to specific bounties with enough technical detail to encourage devs to get involved. Devs can work and earn money by following this channel for latest updates on bounties
Moderation and Management of Channel
The practical question of how this channel is moderated, who is responsible for responding/publishing/growing the channel?
- Who is the community manager of this channel? Do we feel we can launch a channel without a singular community manager?
- When people ask questions how do we propose answering them?
- Something to note, that if your response rate (responding from the channel itself) goes below 20% of questions on a post this can impact your reach
- How do we grow this channel?
- Do we want to utilise this channel to identify and tap into existing community conversations to organically grow the channel? Ie. try to engage in conversations related to #clojure or something like that
- Do we feel cross pollination will be sufficient in growing this channel
- Do we want to do promoted posts to a very particular audience with highly technical content to try and grow the community?
As there seems to be quite a few members of the core team that are interested in having this channel there could be a few ways of tackling this challenge
- Rather than having a singular community manager or someone with the specific role, we can pilot with 5-7 volunteers where we have the framework and tools to be able to access and publish to this channel and the management load could be shared. Whether this is a roster or more organic is something that can be decided amongst the group. Marketing can assist in providing any guidelines. The idea would be to run this pilot for 1 month, document any learnings and prepare some kind of documentation/onboarding to the tool for any CC or community member who wants to join and help moderate the channel
- Encouraging Core team members to take it upon themselves to jump into the channel and engage with community members directly from their own channel (ie. Iuri jumping in and providing assistance to a thread about Embark)
Currently we are running into issues of over publishing and being penalised by it. What steps can we take here to ensure that there is a content pipeline and we aren’t just becoming a non stop broadcast channel?
What is the breakdown of content we expect?
- Status Produced - ie. Social Post amplifying blog announcing ENS
- CC contributed (RT) - ie. Tweet from Ben about a new Incubatee
- Community Curated - ie. Video from a community member reviewing Embark 3.2
- Conversational (responses) -ie. a Thread answering questions related to accessing extensions
The question has already been asked by the Embark, Incubate and PeopleOps team of having their own channel. The main challenge in this instance is reach, resource and what will have the most impact, we currently have new channels which we’ve launched who have full-time team members managing and contributing to the channel and yet growth has been slow and even after three months on avg content only reaches 7 people. This is not to say we shouldn’t do it but rather it needs a measured approach.
A potential solution - A two phased approach:
- Begin with one account but build an identity for each initiative within the channel - through hashtags, Tone of Voice, content themes and visual stylings, all of which Marketing can help the different initiatives develop.
- We create project specific hashtags as aggregators of content
- Visual styles, ie. overlays which made it clear this was an embark post or Incubate post
- Content themes - the different projects may have the same content themes but may go into different depth or have different interest areas and people naturally gravitate towards 1 vs the other
- Analysis of the channel and the content - As a community emerges ie. the volume of community contributed content increases and the avg. engagement on an initiative specific piece of content increases we spin off a new channel. The identity moves with it (initiative hashtag and visual style) but now we have a community built up and a resource could be allocated to properly grow this community.
We’d love to have this channel up and running before Devcon so this is what we’ve identified as next steps:
- Provide any feedback/thoughts/comments on the above proposal
- If you’re interested in helping build this channel through content and moderation put your hand up - we will start with 5-7 at first for the pilot (happy to go a bit bigger if there is more interest)
- We will begin working on the identity for the initiatives
- We will map out a few weeks worth of content in order to launch the channel and have a steady stream
- Once the pilot is complete open it up to any CC or community member who wants to help manage the channel and we can provide access and any guidelines or materials to help onboard