Why do a post-mortem of a vote that passed?
There is plenty of room for improvement. There were many valuable lessons and datapoints provided in past week for the CWG. After the vote closed on Monday, we spent the following 5 hours on calls with Jupiter community members who had eschewed both positive and critical feedback towards the process.
Here are our key takeaways from the 4 hour town hall during the vote, on twitter, as well as conversations with intelligent and measured key opinion leaders who put meaningful time into their critiques.
What went right:
- We collected immensely valuable feedback, as well as attained a massive influx of talented, intelligent and passionate members to the DAO.
- Jupiter received a massive amount of attention and inspired multiple days of conversation around DAO dynamics.
- We stress tested the system and the CWG members themselves, and now have several means to make improvements to various systems based on real world feedback rather than presupposed assumptions.
- We had a very intimate, multi-day back and forth with the community which culminated in a 4 hour Twitter Spaces where everyone was given the chance to speak and be listened to.
What could have gone better & how to improve
ββββββββββββββββββββββββββββββββββββ
Accountability Measures for working groups are something we are tasked with developing; with the cliff serving as the first and most powerful.
The conditions that the DAO could hold a working group accountable could have been communicated much better, and some members felt like they were in some sort of limbo with no recourse possible in the event that the CWG failed to deliver.
-
In 6 months, to ensure full community buy-in and to serve as a stopgap while we develop more measures, Meow has vowed to hold an accountability vote.
-
In the meantime, we will construct a formalized and explicit system for WGβs to be held accountable without burdening them in DAO process β so that the DAO can scale.
ββββββββββββββββββββββββββββββββββββ
The participation rate across Jupiterβs interfaces with the community (Uplink calls, town halls, discord, twitter, the forum) was not representative of every group in the entire holderbase of 250,000 and ended up missing input and perspective from people who do not regularly attend these things.
We have 3 solutions for dealing with this:
- Increasing the accessibility of information through the co-creation of Jup.eco, a website which hosts every piece of DAO relevant information, built in collaboration with multiple cadets.
- For major votes, the addition of a Twitter Spaces to the Discord Townhall and Zoom Uplink Calls.
- Looking into branching comms into telegram.
ββββββββββββββββββββββββββββββββββββ
Proposal Etiquette was missing some items including the CWGβs time commitment, effective budget allocation explanations, and in-depth breakdown of their task scope. While it did cover high level goals, it could have been much more granular.
-
In terms of task scope, as an individual answer: Quarterly reports will be implemented as a standard for all Working Groups which detail out what theyβve achieved in the prior quarter.
-
In terms of proposals going forward, we posit the creation of a βproposal review boardβ made up of catdets to serve as a resource for people who are creating a proposal to give comprehensive and targeted feedback. This could be as simple as creating templates or standards to create consistency across proposals, and to also serve as a sounding board.
TLDR:
- Formalizing more accountability measures as per our task scope, with a 6 month accountability vote βstop-gapβ in the meantime
- Increasing information accessibility, voting UX, and propagation.
- Creating more proposal resources for all work groups.
Thank you to all the Catdets who voted and gave valuable feedback on the very first JWG DAO vote. Let us know what you think!
Additionally, we will have more concrete items to address at the Working Group Townhall which we host after each LFG cycle.
There, we will have answers to questions such as βWhen will the first quarterly report come outβ, and an announcement about an update to the vesting period based on community feedback.
Update on vesting: