Thanks to everyone who attended the workshop and discussion in the leadership forum! Acknowledging there was still a fair amount of concern around transparency. I’ve updated the roadmap at the bottom of the post with an additional step to check-in next week with everyone. If the majority votes yes to creating a new server for contributors, we won’t delete or archive anything. We’ll create the new Server, and then share a more detailed roadmap on how we plan to modify the main community server to ensure transparency and ensure we’re prioritising the community first.
Please vote If you’re unsure, please read the information below and/or watch the replay of the leadership forum.
Should we create a separate contributor Discord server?
- Yes. Create a separate contributor Discord Server
- No. I would like us to maintain the single server
Please note: We (Community Nest) were initially against separating the Discord server into two separate servers, but after more careful consideration most of us now agree it’s in the best interests of our community to divide the server. Please read the document below and attend the leadership forum (Wednesday, Feb 9, 2022) where we’ll be requesting community feedback. After the forum, we’ll add a poll to this forum post to collect feedback from everyone and make a decision.
Over the past two months we’ve had several conversations regarding branching the Index Coop Discord server into two separate servers. From brief pulse checks/conversations, the sentiment appears to be leaning towards the separation, but there is some hesitation (understandable) which we hope to address.
We think this should be a group decision made by the broader community.
We haven’t placed enough effort into engaging, supporting and growing our community of non-contributors. Products can be forked, the community cannot. As we enter Season One, Community Nest’s main focus will be exactly this, serving and growing our community.
As it currently stands, our Discord Server is attempting to serve two different audiences and not doing a great job of either. New non-contributors are often met with a poor and overwhelming user experience with numerous channels and conversations dedicated to contributor work and collaboration, while our contributors are struggling to effectively collaborate and maintain productive conversations due to the noise in the server.
While there are some obvious drawbacks, we believe that branching the server into two will ultimately best serve our community and contributors. Toward the end of last year, we did implement changes to limit the views that new contributors would see through emoji role selection options. But it’s becoming more apparent that a clear separation is the best path forward if we are truly going to serve and engage our community.
Up until now, the Coop has focused primarily on its contributors. We’ve reached a threshold where flooding the DAO with more contributors is no longer productive or sustainable. Our contributor recruitment will be much more proactive and strategic, while our main focus will pivot toward onboarding and serving engaged community members (non-contributors). There will still be ample opportunity for new contributor onboarding.
We also find ourselves in an incredibly unique and challenging position where we’re not just growing a single community of $INDEX token holders, we are also growing a number of sub-communities for each of our products. We need to ensure that our product holders are prioritized, supported, engaged and given an all round exceptional experience within the Index COOP server. As our product range expands, managing the both contributor and community within the one server will become increasingly challenging.
This will also give us the chance to identify, acknowledge and reward our community legends who aren’t necessarily core contributors, but support and champion our products relentlessly.
- Create an environment which most effectively engages, supports and grows a vibrant community of $INDEX holders and Index Product Holders
- Support our core contributors to work efficiently and effectively together, and get shit done
- Branching the server could lead to fragmentation of the community. Some of our core contributors are also our most lively, engaged and supportive community members. It’s possible they would be less likely to engage with our community if the servers were separated
- Could potentially create a rift between core contributors and community and reduce transparency
- We might lose some potential talent by pivoting toward community focused onboarding
- Clearly delineating the purpose of our main server as community servant will allow us to focus our efforts and create a better UX for our non-contributor community
- Managing roles, responsibilities and access is a nightmare at the moment. Cleaning out all of the contributor focused roles and notifications will allow more effective communication and notification
- As we launch more products, some of which have active components, we need to ensure new/potential product holders are quickly and easily able to receive the support they need. A separate server would make this much easier
- A separate server for core contributor collaboration will significantly reduce the noise/notifications and enable more efficient work
- Measuring contributor vs community engagement metrics will be easier with two servers
- Increase coordination efficiency for contributors
- Reducing the need for us create private chats to coordinate and execute on product launches
- We can further explore using channel hide role selection to clean our server and improve the UX within Discord before we make the branch.
The existing server would remain the community focused server. We would create a new server which would serve the core contributing owls listed in each of the proposals.
- Duplicate server, creating a new streamlined contributor space specifically for core contributor coordination and work. Once the migration is complete, archive the contributor focused channels, leaving one public channel for each Nest to connect with the community, advertise bounties and answer questions from those still wanting to get involved. We will encourage each pod to have it’s own channel, with threads for projects
- Identify Discord ‘Allstars’ and ensure increased community engagement in the community Discord and still encourage all our contributors to remain active in both servers
2.5 Check-in with each Nest in Leadership forum February 16, 21 to share updated roadmap.
- Audit and revise all roles and permissions in the existing community server, delete non-active community members, remove redundant roles and simplify the role access/permissions. Clean up wording to focus on community engagement. Design new product/community specific projects.
- Build out better categories/channels for each of our products, increase product support. Create more intuitive areas in Community Discord for our different investment personas and products
- Create systems to identify key sub-community managers to increase our support and horizontal growth
- Speak with Discord Allstars
- Post the request for feedback to the forum
- Schedule and host Discord workshop during leadership forum
- Add poll within this forum post (after workshop).
- If in favour, commence the branch (with aim to complete by the end of February)
- If largely against, revise the project to focus on improving community UX with role selection
Sending massive amounts of gratitude to all of our existing contributors and community members who have been the lifeblood of our Discord thus far. We are aiming to use this opportunity to work more closely with you and give more resources to ensure we have the most vibrant community in the Web3 space! We’d love your feedback and look forward to speaking with you soon.