<p>  <strong>Please see comments for details on the 2nd July expansion and revision to content and budget of this proposal</strong> </p>
<h2>
<a name="proposal-for-the-creation-of-the-people-organization-and-community-wg-1" href="#proposal-for-the-creation-of-the-people-organization-and-community-wg-1"></a>Proposal for the creation of the People, Organization and Community WG</h2>
<h3>
<a name="situation-2" href="#situation-2"></a>Situation</h3>
<p>I am proposing the funding of a People, Organization and Community Working Group (POC) for 3 months ending on October 1st, 2021.</p>
<h3>
<a name="what-is-the-core-problems-you-want-to-solve-3" href="#what-is-the-core-problems-you-want-to-solve-3"></a>What is the core problem(s) you want to solve?</h3>
<p>As the Coop grows, our ability to operate efficiently and utilize the skills within our DAO will be challenged.</p>
<p>This will manifest through:</p>
<ul>
<li>Disconnect with our <strong>community</strong> and a failure to leverage this group as a motivated, passionate and engaged foundation to champion our products</li>
<li>Inefficiencies within our <strong>organizational</strong> processes which impact our ability to plan, waste time and decrease the effectiveness of Index Coop contributors and Working Groups</li>
<li>Ineffective identification, utilization and retention of top <strong>people</strong> talent will restrict long term growth</li>
</ul>
<h3>
<a name="why-is-this-worth-addressing-today-4" href="#why-is-this-worth-addressing-today-4"></a>Why is this worth addressing today?</h3>
<p><strong>People are the most important driver of organizational success.</strong> If Index Coop can recruit the right people, focusing them on the right things and enable them to work in the right way - we will create an environment where we can become a market leading billion dollar DAO.</p>
<p>Recently, the Coop has experienced a period of rapid growth. As such, there is a pressing need to ensure contributors can be engaged and channeled in a way that drives meaningful results.</p>
<p>A dedicated People, Organization and Community (POC) team will help ensure the Coop is made up of <strong>top global talent</strong> working within a <strong>streamlined organization structure</strong>. The POC will act as an <strong>enabler</strong> for the wider Index Coop.</p>
<p><em>For example, we are currently facing a bottleneck with dev resources. Establishing a Community, Organization and People WG could help preempt future bottlenecks and support the identification and recruitment of capability in key strategic areas.</em></p>
<h3>
<a name="how-will-you-address-it-5" href="#how-will-you-address-it-5"></a>How will you address it?</h3>
<p>There are three interconnected pillars of the POC Working Group. The approach and activity within each of these pillar will evolve, but will likely cover:</p>
<ul>
<li>
<p>People</p>
<ul>
<li><strong>Identification of “People Needs” at the Coop and support filling vacancies to ensure we have the right people in the right jobs (high priority)</strong></li>
<li>Anonymous Owl Pulse survey to identify pain points and opportunities for things we can do differently as a DAO.</li>
<li>Launch of the internship program, establishing Index Coop as a leader in talent development and equal opportunities within DeFi</li>
<li>Design and distribution of payment for Bronze Owls Quest focused on promoting key behaviours</li>
<li>Work with key community members to reimagine “Owl Levels” and the associated benefit packages required to attract and retain top talent. (<a href="https://gov.indexcoop.com/t/trust-and-impact-in-the-index-coop/1661">Trust and impact in the Index Coop <span>4</span></a>)</li>
<li>Defining and analyzing community health as understanding/measuring community health is essential to establishing long-term strategic vision at the Coop.</li>
<li>Research articles establishing Index Coop as a thought leader in the space on all things DAO community, organization and people</li>
</ul>
</li>
<li>
<p>Organization</p>
<ul>
<li>Development of planning and forecasting structures and processes to increase visibility of key milestones and priorities within the Coop</li>
<li>Continuous improvement of our meeting cadence, working rhythm and organizational structure</li>
<li>Index Coop process design and improvement (i.e. treasury process automation)</li>
<li>Explore and maintain operational assets that empower productivity. Improve the effectiveness of our existing collaboration tools.</li>
</ul>
</li>
</ul>
<p><em>Note governance responsibility, such as the handover from Set (i.e. Gov 2.0: <a href="https://gov.indexcoop.com/t/index-gov-2-0-introduction-to-delegated-governance/1733/2">Index Gov 2.0 - Introduction to Delegated Governance - #2 by cedrick <span>1</span></a>) is not covered within the POC WGs remit.</em></p>
<ul>
<li>Community
<ul>
<li>Hosting of weekly community webinars and AMAs content to build an engaged, informed and educated community base</li>
<li>Managing BAU for New joiners call to provide context, knowledge sharing and a sense of community for new contributors</li>
<li>Iteration and streamlining of the WG specific onboarding process to identify and funnel top talent to WGs requiring support</li>
<li>Setting up opportunities for us to connect as individuals and socialize as a community</li>
<li>Moderation of Discord and expanding the functionality offered by this platform (i.e. bot &amp; roles)</li>
<li>Maintenance of internal learning resources and reference guides i.e. the Community Handbook</li>
</ul>
</li>
</ul>
<h3>
<a name="what-impact-will-this-project-have-6" href="#what-impact-will-this-project-have-6"></a>What impact will this project have?</h3>
<p>The POC is here to support all other Working Groups in their attainment of overarching KPIs.</p>
<p>This will be achieved through an engaged community made of high calibre talent working together in an effective way. They will be enabled by an organizational system which supports the identification, planning and accountability of strategic opportunities and objectives.</p>
<p>Thus, the POC will help Index Coop scale up to become a high performing team able to achieve its <a href="https://gov.indexcoop.com/t/north-stars-core-kpis-v1/973">North Stars &amp; Core KPIs</a>.</p>
<p><strong>Working Group Leader(s)</strong></p>
<p>Joe McKenzie (<a href="https://gov.indexcoop.com/u/jdcook">@</a>Pepperoni_Joe)</p>
<ul>
<li>Index Coop Community Manager since May 1st.</li>
<li>Master in Occupational Psychology, PwC consulting alumni specializing in People and Organization.</li>
</ul>
<p>POC WGL will determine contributions rewards for activity relating to Community, Organization and People.</p>
<p>Contributors who will be involved POC WG activity may include:</p>
<ul>
<li>Discord automation - Defi Jesus</li>
<li>Webinar &amp; AMA lead - Crypto Texan</li>
<li>Social &amp; Analysis - Helmass</li>
<li>Internship - JMT NFT / oneski</li>
<li>Learning resources &amp; Gitbook - Mel / DOC</li>
<li>New Joiner call - Cormac</li>
</ul>
<h3>
<a name="request-for-funding-7" href="#request-for-funding-7"></a>Request for Funding</h3>
<p><strong>Contributor Rewards</strong></p>
<p>Requesting a fixed fee of:</p>
<ul>
<li>
<strong>Leader Stipend</strong> - 430 Index [$8,700/month - as per June 20 day moving average]</li>
</ul>
<p>The 430 Index [approx $8.7k] is set to cover <s> [all my contributions across the Coop for the next 3 months, including activity spanning Growth, BD etc] </s> all activity undertake to lead the POC WG and deliver on the defined objectives and KPIs.</p>
<p>This sits between the reward level of part-time non-technical WG leads (i.e. Dev - $6,000) and full time technical WG lead salaries (i.e. JD Cook - $10,000).</p>
<ul>
<li>
<strong>Contributor Rewards</strong> - approx $10,993 /month</li>
</ul>
<p>Estimated budget required to attract and retain consistent POC talent and achieve the outlined objectives.  A detailed breakdown of contributor rewards allocation is show below.</p>
<p></p><div><a href="https://global.discourse-cdn.com/standard10/uploads/theindexdao/original/2X/d/dbc178d2a745526e225698e4a508c2e1b1688ec2.png"><div>
<span>image</span><span>455×536 16.1 KB</span>
</div></a></div><p></p>
<ul>
<li>
<strong>Licenses &amp; Subscriptions</strong> - approx $727 /month</li>
</ul>
<p>To acquire required technology and licenses needed to support POC activity. These licenses would be used across the Coop - for example <a href="https://home.webinarjam.com/index">webinar jam</a> will support BD webinar activity.</p>
<ul>
<li>
<strong>Ad Hoc cont. rewards</strong> - approx $3,045 /month</li>
</ul>
<p>We have <s>~$4,350</s> $3,045/month budgeted for ad hoc contribution awards (outside of core duties) and to cover unexpected subscription needs. This extra budget has been included as “leg room” to enable the POC to fund any costs arising from “unknown unknowns”</p>
<p><s>* <strong>Bronze Owl Quest</strong> - approx $10,000 /month</s></p><s>
</s><p><s>Finally we have budgeted $10,000 for the Bronze Owl quests which will support payment to ~20 new joiners for their first month of reward. Payment for first month rewards is budget from and allocated by the POC. However, activity undertaken as part of the “Bronze Owl Quest” will likely span across multiple WGs.</s></p>
<h3>
<a name="total-request-for-funding-8" href="#total-request-for-funding-8"></a>Total Request for funding</h3>
<p>Based on the breakdown provided above, we request monthly funding of $14,707 + 430 Index per month for 3 months - equaling a total requested budget of $44,121 and 1290 Index.</p>
<p></p>
<h3>
<a name="organization-9" href="#organization-9"></a>Organization</h3>
<p>How will it work? / What will you be doing?</p>
<ul>
<li>See section “how will you address it”</li>
</ul>
<p>How will you interface with the community?</p>
<ul>
<li>Governance Forum Posts</li>
<li>Weekly Community, Organization and People call</li>
<li>Publication of all expenses and contributor rewards</li>
<li>
<span>#Community</span> Channel on Discord</li>
<li>Community, Organization and People update in Monthly and Quarterly report</li>
</ul>
<h3>
<a name="commitments-10" href="#commitments-10"></a>Commitments</h3>
<p>I am committed to <a href="https://docs.indexcoop.com/our-guiding-principles">Index Coop principles <span>2</span></a></p>
<p>I am committed to serving the entire Index Coop with my work.</p>
<p>I know that clear, constant, public communication lifts up the entire Index Coop community. I am committed to this style of communication.</p>
<p>I will share my progress, learnings with the entire community. I will ensure that anything I create is accessible beyond my own tenure for future generations of Indexers to access &amp; build on.</p>
<p>I am committed to growth and improvement. I am open to feedback and will use feedback to improve my work for the benefit of the community.</p>
<p>I am committed to making Index Coop a welcoming, fun, and engaging community to work in!</p>
<div><div><ul><li> <span><strong>For</strong> initiating the POC WG from 1st July to October 1st</span></li><li> <span><strong>Against</strong> initiating the POC WG from 1st July to October 1st</span></li></ul></div><div><div><div><span>27</span><span>voters</span></div></div><ul></ul></div><div><span>Vote now!</span><span>Results</span></div></div>

Proposal for the creation of the People, Organization and Community (POC) WG - **UPDATED**

<p>Status: Proposed<br />
Author(s): <a href="/u/lavi">@Lavi</a>, <a href="/u/mel.eth">@Mel.eth</a>, <a href="/u/sixtykeys">@sixtykeys</a><br />
Reviewed by: <a href="/u/mringz">@Mringz</a><br />
Created: 27th September 2021</p>
<h1>
<a name="situation-1" href="#situation-1"></a>Situation</h1>
<p>We are proposing the creation and Q4 funding of the Governance Operations Working Group [term ending 14th January 2022].</p>
<p>At present, governance operations are fragmented and not centralized into a specific function in the Coop. Operations are executed under the purview of a few individuals and the POC WG mainly, drawing focus from the funded initiatives tied to that WG. There is no holistic monitoring of the process or a clear avenue for iterative improvement or accountability. The desired outcome is providing greater focus and accountability related to governance operations, inspiring a greater sense of execution ease, importance, and protocol ownership. This ensures that contributors responsible for executing governance-related functions are well-trained, accountable and remunerated, providing a clear funding path for governance operations.</p>
<p>It is time to build out the resource-planning, accountability, process-improvement, and reporting functions that a dedicated WG can incentivize and coordinate. Coordinating and executing fair and successful votes, timely reporting, and tracking implementation are essential functions of any operational and autonomous DAO. Given that all executive functions currently flow directly from our governance processes, the importance of ensuring operational continuity in this regard cannot be overstated.</p>
<p>The DeFi Pulse Index also gives the Index Coop access to its underlying components, which are held in its smart contracts. This provides the Coop with Meta Governance power in protocols such as Aave, Compound and Yearn. Therefore, we need to ensure that this process is running smoothly and efficiently by enabling contributors to manage it and make improvements where needed.</p>
<p><strong>Disclaimer:</strong> <em>In recognition of the ongoing Index 2.0 discussions and potential near-term impacts on governance operations: This WG, if formed, will defer in whole or part to any resultant organized bodies that may overlap with (or obviate the need for) this WG as envisioned below, or endeavour to supplement and support the Index 2.0 efforts as appropriate. Nonetheless, the WG term is set to the conventional 3-months. A structural / efficacy review will take place within the first two weeks of the final month of the first term to inform a request for renewal or deprecation of the WG as appropriate.</em></p>
<h1>
<a name="what-is-the-core-problems-you-want-to-solve-2" href="#what-is-the-core-problems-you-want-to-solve-2"></a>What is the core problem(s) you want to solve?</h1>
<ul>
<li>Currently, governance operations and meta-governance operations are done by different people who do not organically coordinate with each other.</li>
<li>Some governance operations tasks are done by just one person, without a fall-back option should that person become unavailable for any reason.</li>
<li>Governance Ops is a vital part of the community. It includes IIP management, setting up Snapshot votes, keeping the community informed on multiple channels, ensuring quality assurance on IIPs, and more. However, most of these tasks are done in isolation which leaves room for efficiency gains and improvements.</li>
<li>Our governance process keeps changing and improving. However, most of it is done by the WG or person that needs to change something (e.g. general IIP template improvements, PWG improving the product IIP template, the meta-governance election process, autonomy group election, etc.). These examples happen organically within the community. However, a Governance Operations working group could support creating such a process, plus maintaining recurring things like the MGC election.</li>
<li>Index Coop is in the midst of rapid growth; with the increased number of contributors joining and the increasing number of working groups, we expect the number of proposals to grow exponentially. Our Meta Governance powers are also increasing day by day. Thus we expect to attract even more outside parties to go through our governance process. This is a time-consuming process for the contributors who currently manage this process, allowing little time to focus on other initiatives. A working group structure would enable us to focus our time and effort solely on ensuring smooth governance operations and reporting and improvement of the process.</li>
<li>Given that passed IIPs generally require that defined action occur, tracking of implementation is currently happening in an ad-hoc manner and generally removed from community awareness.</li>
</ul>
<h1>
<a name="why-is-this-worth-addressing-today-3" href="#why-is-this-worth-addressing-today-3"></a>Why is this worth addressing today?</h1>
<ul>
<li>Most processes focusing on Governance are already quite established and operated by capable people. This proposal is a means to bring the contributors under one umbrella to increase efficiency, improve coordination and streamline daily operations.</li>
<li>There needs to be an accountability and feedback mechanism for governance operations to inspire greater confidence from token-holders that voting operations are occurring as planned and implementation status is clearly communicated. This creates a problem as contributors who make these proposals have to spend extra time following up on previous IIPs and, as a result, prevents them from focusing on the work at hand (examples <a href="https://gov.indexcoop.com/t/iip-73-fli-economic-model-upgrade-past-gas-costs/2355/17">here</a> and <a href="https://gov.indexcoop.com/t/iip-72-redirect-fli-revenue-to-operations-account/2368/14">here</a>).</li>
<li>The current system of governance operations is executed and funded in an ad-hoc manner that is susceptible to coordination inefficiencies.</li>
<li>The governance process can be made more transparent and accessible.</li>
<li>There is good reporting coming from contributors; however, it is not regular communication that the community can rely on.</li>
<li>As seen in <a href="https://gov.indexcoop.com/t/iip-67-delegate-uni-to-flipside-for-community-enabled-analytics/2242">IIP-67</a> and <a href="https://gov.indexcoop.com/t/iip-82-use-indexcoops-aave-holdings-to-list-fei-on-aave-v2/2573">IIP-82</a>, several third parties wish to use the Index Coop’s Meta Governance powers. But due to the failure of <a href="https://gov.indexcoop.com/t/iip-80-meta-governance-proposals-mgp-process/2492">IIP-80 <span>2</span></a>, external parties do not have a clear path, orientation, or point of contact when coming to the Coop to request Meta Governance.</li>
<li>There is currently a lack of knowledge around Index Improvement Proposals, with many community members not aware of how to go about the process and, even if they do decide to make a proposal, not sure of the correct steps or format in which to present their proposals and take them to Snapshot. This group can be of support and guide contributors.</li>
</ul>
<h1>
<a name="how-will-you-address-it-4" href="#how-will-you-address-it-4"></a>How will you address it?</h1>
<p>This proposal, if enacted, would empower the resultant WG to:</p>
<ul>
<li>Ensure that governance operations are being attended to in a transparent and accountable manner (i.e. IIP review and editing, Meta-Governance Operations, Snapshot posting and elections).</li>
<li>Provide robust tracking and reporting on governance.</li>
<li>Provide coordinated process improvement recommendations.</li>
<li>Provide risk, failure, and near-miss assessments requested by the community.</li>
<li>Recommend and draft ‘clean-up’ IIPs that fill in gaps or may be required for ongoing DAO operations (i.e. setting advance reminders and facilitating coordination of quarterly funding requests in a timely manner).</li>
<li>Provide feedback and education to community members active in governance re proper procedures and required discussion periods.</li>
</ul>
<h1>
<a name="what-impact-will-this-project-have-5" href="#what-impact-will-this-project-have-5"></a>What impact will this project have?</h1>
<p>This WG will aid in fostering the Guiding Principles (<a href="https://docs.indexcoop.com/our-guiding-principles">Our Guiding Principles - Index Coop Community Handbook <span>2</span></a>) of:</p>
<ul>
<li>Innovation</li>
<li>Data-Driven, Community Governed
<ul>
<li>Reporting</li>
<li>Recommend and implement improvements to the process</li>
</ul>
</li>
<li>Community
<ul>
<li>In keeping with the ‘people-first’ approach of Index Coop</li>
<li>Improved transparency, fairness, communication, organization, autonomy, and accountability</li>
</ul>
</li>
</ul>
<p>This working group will also create a clear and distinct framework to be followed and carried forward by any contributors who may take up these roles in the future.</p>
<h1>
<a name="working-group-leaders-6" href="#working-group-leaders-6"></a>Working Group Leader(s)</h1>
<ul>
<li>Lead: Simon Lavi (<a href="/u/lavi">@Lavi</a>)</li>
<li>Co-Leads: Brian Adam (<a href="/u/sixtykeys">@sixtykeys</a>) &amp; Mel Oxenreider (<a href="/u/mel.eth">@mel.eth</a>)</li>
<li>Core contributors: Michael Mtenga (<a href="/u/mringz">@Mringz</a>)</li>
</ul>
<p>Three people currently manage different verticals of the governance process; therefore, we feel this WG is best served by having three leads, one to focus on each work area: <a href="/u/lavi">@Lavi</a> → Meta Governance Ops, <a href="/u/sixtykeys">@sixtykeys</a> → IIP/Governance Ops and <a href="/u/mel.eth">@mel.eth</a> → Meta Governance Proposals (e.g. using Aave to list tokens) and Elections. <a href="/u/mringz">@Mringz</a> will serve as a core contributor for the WG by continuing to serve as the point person for product related IIP’s while continuing to build out the protocol ambassador program.</p>
<h1>
<a name="request-for-funding-7" href="#request-for-funding-7"></a>Request for funding</h1>
<h2>
<a name="proposed-budget-8" href="#proposed-budget-8"></a>Proposed Budget</h2>
<ul>
<li>We are requesting a budget of $30,000 plus 1800 INDEX over the next three months.</li>
</ul>
<h2>
<a name="use-of-funds-9" href="#use-of-funds-9"></a>Use of funds</h2>
<p>Working Group Leader Compensation: 1,800 INDEX (200 INDEX per leader/co-leader per month).</p>
<p>Additional contributor rewards: We have budgeted for $10,000 per month (This is under the expectation of 2 or 3 additional contributors to this working group during Q4).</p>
<p>Unused contributor rewards will be returned at the end of term or discounted from future WG funding requests.</p>
<p>Note: The Meta-Governance Committee is funded via <a href="https://gov.indexcoop.com/t/iip-51-form-a-meta-governance-committee/1792">IIP-51 <span>3</span></a> at $7,500/mo in total. No proposed change to amount or process; however, this WG will provide operational support upon request.</p>
<h1>
<a name="what-will-you-be-doing-10" href="#what-will-you-be-doing-10"></a>What will you be doing?</h1>
<p>The proposed GOWG, if implemented, would be an operations and reporting function within the larger Index Coop organization to facilitate coordination and feedback relating to Governance, Meta-Governance, and Elections.</p>
<p>Over the three month term the GOWG will seek to solve the Core Problems outlined above by:</p>
<ul>
<li>
<p>Operations:</p>
<ul>
<li>Review, coordinate, and execute the governance operations required by passed IIPs and available guidance.</li>
<li>Full ownership of Operations tasks related to the process of creating IIPs as well as Meta Governance votes.</li>
</ul>
</li>
<li>
<p>Improvement:</p>
<ul>
<li>Improve the governance process to the extent possible within the current execution guidelines.</li>
<li>Suggest experience-informed improvements to the governance process that may rise to the level of an IIP, as appropriate.</li>
<li>Launching and further development of governance and metagovernance related initiatives (i.e <a href="https://gov.indexcoop.com/t/launching-the-index-coop-protocol-ambassador-program/1836">Protocol Ambassador Program</a>)</li>
</ul>
</li>
<li>
<p>Outreach:</p>
<ul>
<li>Host a weekly WG meeting (will go to bi-weekly if interest or content is not sufficient to warrant) to review the governance operations and outcomes subsequent to the previous meeting.</li>
<li>Meet weekly among WG contributors to ensure that governance operations are well-coordinated and executed efficiently. We will also use this meeting to brainstorm any new ideas to improve governance operations, as well as discuss strategies for implementing new and existing governance initiatives.</li>
<li>Ensure that key stakeholders i.e VC’s, contributors, community are actively informed about governance proposals</li>
</ul>
</li>
<li>
<p>Gitbook Updates:</p>
<ul>
<li>Keep the Community Handbook updated with the latest governance information.</li>
</ul>
</li>
<li>
<p>Governance Content:</p>
<ul>
<li>Ideate and build resources to make voting easier to understand and execute.</li>
</ul>
</li>
<li>
<p>Tracking &amp; Reporting:</p>
<ul>
<li>Keep IIP tracking logs updated and accessible.</li>
<li>Create and maintain logs of IIP execution post-vote, along with periodic reports, to ensure that IIPs are being implemented according to design.</li>
<li>Coordinate with AWG to generate reports outlining voter participation etc.</li>
</ul>
</li>
<li>
<p>Comprehension:</p>
<ul>
<li>Review governance-related proposals in the forum and provide timely feedback as to:
<ul>
<li>Ease of execution.</li>
<li>Necessary integrations and changes to existing processes.</li>
<li>Highlight available governance mechanisms that may improve the process.</li>
</ul>
</li>
<li>Endeavour to encourage discussion, foster an environment of innovation and support thought-leaders around the subject of governance.</li>
<li>Supplement and create resources to build a comprehensive set of ‘bylaws’ out of the passed IIPs.</li>
</ul>
</li>
</ul>
<h1>
<a name="how-will-you-interface-with-the-community-11" href="#how-will-you-interface-with-the-community-11"></a>How will you interface with the community?</h1>
<ul>
<li>As outlined above, WG meetings will initially be held weekly and timeboxed to 1-hour, adjusted based on utility but not less than bi-weekly.</li>
<li>Group leads will ensure that the governance forum and governance-related discord channels are monitored with timely responses to all queries.</li>
<li>Regular updates and announcements via the governance forum as well as relevant discord channels.</li>
<li>Weekly report on governance proposals that need community attention and votes that are currently live or pending on Snapshot.</li>
<li>Monthly report on the number of IIPs passed and failed, participation, the progress of implementation etc.</li>
</ul>
<h1>
<a name="commitments-12" href="#commitments-12"></a>Commitments</h1>
<p>We are committed to the <a href="https://docs.indexcoop.com/our-guiding-principles">Index Coop principles <span>2</span></a></p>
<p>We are committed to serving the entire Index Coop with our work.</p>
<p>We are committed to open, rapid communication: We know that clear, constant, public communication lifts up the entire Index Coop community. We are committed to this style of communication.</p>
<p>Shared learnings: We will share our progress and learnings with the entire community. We will ensure that anything we create is accessible beyond our tenure for future generations of Indexers to access &amp; build on.</p>
<p>Intellectual honesty: We are committed to growth and improvement. We are open to feedback and will use feedback to improve our work for the benefit of the entire Index Coop community.</p>
<p>We are committed to making Index Coop a welcoming, fun, and engaging community to work in!</p>
<div><div><div>Fund a Governance Operations Working Group for Q4 2021</div><ul><li><div><p><span>100%</span><span>FOR</span></p></div><div><div></div></div></li><li><div><p><span>0%</span><span>AGAINST</span></p></div><div><div></div></div></li></ul></div><div><div><div><span>20</span><span>voters</span></div></div><ul><li>
                    
                    <span>Closed <strong>Oct '21</strong></span>
                   </li><li>
                
                <span>Results will be shown on <strong>vote</strong>.</span>
               </li></ul></div><div></div></div>

[FINAL POLL CLOSED] Proposal: Governance Operations Working Group

<p><strong>Title: Engineering Working Group Request for Funding</strong></p>
<p><strong>Authors: <a href="/u/edwardk">@edwardk</a>, <a href="/u/dylan">@dylan</a></strong></p>
<h3>
<a name="situation-1" href="#situation-1"></a>Situation</h3>
<p>We are proposing funding for the Engineering Working Group for 3 months ending on December 31st.</p>
<p><strong>What is the core problem(s) you want to solve?</strong></p>
<p>As described in <a href="https://gov.indexcoop.com/t/deciding-how-to-prioritize-engineering-work-poll/2685">Deciding How to Prioritize Engineering Work</a> the in-house engineering team at Index Coop is relatively new. With the launch of DATA in Q3 we’ve proven that we can do most (but not all) of the work to launch a Simple Index product without relying on Set’s engineers. That’s a huge accomplishment! </p>
<p>However, there are many more products that we would like to launch which are much more technically complex. In order to build these effectively, we need better alignment between Set Labs and Index Coop’s Product and Engineering teams. At the same time, we have to get creative and intentional about increasing our in-house engineering ability.</p>
<p>The core problems we want to solve today are:</p>
<ol>
<li>Lack of visibility into product priorities, making it difficult to plan engineering work.</li>
<li>Poor coordination between Set Labs and Index Coop when it comes to R&amp;D efforts. This is in part due to Problem <span>#1</span>.</li>
<li>There aren’t enough experienced smart contract developers to go around and hiring them has proven difficult.</li>
<li>Lack of documentation, processes, and training infrastructure make it difficult to onboard even skilled developers.</li>
</ol>
<p><strong>Why is this worth addressing today?</strong></p>
<p>The range and quantity of new products we can launch are constrained as much by coordination problems as by limited engineering talent.</p>
<p><strong>How will you address it?</strong></p>
<ul>
<li>Seeking guidance from PWG for larger R&amp;D efforts, in accordance with expected future launches.</li>
<li>Improving coordination between Set Labs and Index Coop’s engineering teams.</li>
<li>Leveling up existing contributors’ expertise in smart contract programming by investing in mentorship, developer education, pair programming and other means.</li>
<li>Recruiting and onboarding additional engineering talent through our Wizardry channel.</li>
<li>Starting to build Index Coop’s brand in the developer community.</li>
</ul>
<p><strong>What impact will this project have?</strong></p>
<ul>
<li>Greater in-house financial product smart contract capabilities.</li>
<li>Integrations with at least 4 new protocols (CREAM, Curve, etc.)</li>
<li>Better tools for the community around calculating liquidity requirements and making multisig transactions.</li>
<li>Increased contributor participation in terms of commits to our Github project repositories.</li>
<li>2 additional full-time hires or the equivalent in contributors.</li>
</ul>
<p><strong>Working Group Leader(s)</strong><br />
Co-lead: Edward (<a href="/u/edwardk">@edwardk</a>)<br />
Co-lead:  Dylan (<a href="/u/dylan">@dylan</a>)</p>
<h3>
<a name="request-for-funding-2" href="#request-for-funding-2"></a>Request for Funding</h3>
<p><strong>Proposed Budget:</strong></p>
<p>$180,000 USD in INDEX ($60,000 per month) and 1,275 INDEX.</p>
<p>This compares to the Q3 budget of $120,000 USD in INDEX which did not include a gas budget.</p>
<p><strong>Use of Funds:</strong></p>
<p>425 INDEX per month for <a href="/u/edwardk">@edwardk</a> as working group co-lead.</p>
<p><a href="/u/dylan">@dylan</a> is a full-time employee of Set Labs and is not included in this budget.</p>
<p>$19,500 in INDEX per month is for full-time contributors <a href="/u/0xmodene">@0xModene</a> and <a href="/u/ncitron">@ncitron</a>. Their compensation packages were passed via <a href="https://gov.indexcoop.com/t/iip-66-smart-contract-engineer-offer/2279">IIP-66 <span>5</span></a> and <a href="https://gov.indexcoop.com/t/iip-75-web3-engineer-full-time-offer/2463">IIP-75 <span>4</span></a>.</p>
<p>We also request $45,000 in gas costs for the quarter to deploy new contracts and make transactions. It cost approximately $17,000 in gas to launch DATA, for example. We also need some budget for deploying other contracts (e.g. for OTC 3rd Close), technical operations (contributor rewards, methodologist reward payouts), and testing Web3 functionality on <a href="http://indexcoop.com">indexcoop.com</a>. Gas costs are difficult to predict and will depend in part on how many products are launched. It’s quite possible that we are underestimating future gas costs and may need to request additional funding.</p>
<p>The remaining $25,500 in INDEX per month will mainly be used to grow our contributor base. Recent highly talented contributors include <a href="/u/flattestwhite">@Flattestwhite</a>, <a href="/u/rootulp">@rootulp</a>, and <a href="/u/blockdev">@blockdev</a>, among others. We believe that with proper onboarding and incentives in place, contributors will increase their tenure and time allocated to Index Coop, and some will choose to join as full-time contributors.</p>
<p>Other uses of funds may include one-off bounties, recruiting costs, software/services, and smart contract audits (when deemed necessary).</p>
<p></p><div><a href="https://global.discourse-cdn.com/standard10/uploads/theindexdao/original/2X/c/c10b553354b7be162cd7657f9adbbe5df2d3a86f.png"><div>
<span></span><span>1556×424 54.1 KB</span>
</div></a></div><p></p>
<h3>
<a name="organization-how-will-it-work-3" href="#organization-how-will-it-work-3"></a>Organization - How will it work?</h3>
<p><strong>What will you be doing?</strong></p>
<ul>
<li>Product R&amp;D performed in conjunction with Set Labs</li>
<li>Keeping backlog and sprint boards up to date</li>
<li>Weekly sprint planning meetings</li>
<li>Testing &amp; deploying code</li>
<li>Assisting Set Labs with rebalancing</li>
<li>Recruiting</li>
<li>Developer community outreach and participation (e.g. conferences, hackathons)</li>
<li>Regular knowledge sharing and collaborative code reviews</li>
</ul>
<p>Generally speaking Edward will lead on engineering culture, strategy, and planning. Dylan will be in charge of operations and coordinating execution of deployments and transactions.</p>
<p><strong>How will you interface with the community?</strong></p>
<ul>
<li>Forum posts and discord.</li>
<li>Product launch retrospectives.</li>
<li>Cross functional groups where required.</li>
<li>
<span>#Wizardry</span> channel for onboarding technical contributors.</li>
<li>Community updates via Monday morning meetings + an end of quarter retrospective.</li>
</ul>
<h3>
<a name="commitments-4" href="#commitments-4"></a>Commitments</h3>
<p>I am committed to <a href="https://docs.indexcoop.com/our-guiding-principles">Index Coop principles</a></p>
<p>I am committed to serving the entire Index Coop with my work.</p>
<p>I am committed to open, rapid communication: I know that clear, constant, public communication lifts up the entire Index Coop community. I am committed to this style of communication.</p>
<p>Shared learnings: I will share my progress, learnings with the entire community. I will ensure that anything I create is accessible beyond my own tenure for future generations of Indexers to access &amp; build on.</p>
<p>Intellectual honesty: I am committed to growth and improvement. I am open to feedback and will use feedback to improve my work for the benefit of the entire Coop community.</p>
<p>I am committed to making Index Coop a welcoming, fun, and engaging community to work in!</p>
<div><div><div>Poll to vote to approve and fund the EWG as described in this post</div><ul><li><div><p><span>100%</span><span>FOR</span></p></div><div><div></div></div></li><li><div><p><span>0%</span><span>AGAINST</span></p></div><div><div></div></div></li></ul></div><div><div><div><span>22</span><span>voters</span></div></div><ul><li>
                    
                    <span>Closed <strong>Oct '21</strong></span>
                   </li><li>
                
                <span>Results will be shown on <strong>vote</strong>.</span>
               </li></ul></div><div></div></div>

**POLL ADDED** Proposal: Engineering Working Group Request for Funding

<p><strong>Situation</strong></p>
<p>I am proposing the funding of a Language Operations Working Group (LOWG) for 3 months ending December 31st, 2021. This will be the second iteration of the working group and will address continued and growing interest in Index Coop (IC) products outside English speaking markets through the translation of core content. Contributions in Q4 will also cover immediate operational needs in relation to the new Index Coop website and also support expansion into new markets.</p>
<p><strong>What is the core problem(s) you want to solve?</strong></p>
<p>By facilitating content in several languages the LOWG has grown interest in IC products and supported the efforts of contributors in various regions.</p>
<p>In line with the IC’s <a href="https://gov.indexcoop.com/t/growth-north-stars-core-kpis-v1/973">North Stars and Core KPIs</a>, the LOWG seeks to increase the number of holders of IC products by reaching and communicating with audiences in languages other than English.</p>
<p>The first iteration of the LOWG has helped grow audiences in the key target languages of CN, DE, and ES, as well as several others with promise. Now, with the soon-to-be-released website unifying IC content, there exists an opportunity to further increase engagement and reach because of the visitor-trust and SEO effects of having an authoritative site for our content.</p>
<p>We wish to build on the product knowledge of the group, their demonstrated commitment, and their results to ensure the language facilities of the new site are a great value-add to the customer journey and sales funnel of the IC.</p>
<p>The LOWG also seeks to maintain its open door for newcomers to the IC by having the facility to fund promising opportunities for content in languages that we currently do not serve. To date, we have played a part in supporting the introduction of several now well-established IC contributors, especially in the APAC region.</p>
<p>The LOWG wishes to continue its program of targeted, results focussed activities to serve the growth of the Coop’s North Star’s and KPIs outside of the anglosphere.</p>
<p><strong>Why is this worth addressing today?</strong></p>
<p>It is important to address this problem today because:</p>
<ul>
<li>We should retain and develop the great team already familiar with Coop content,</li>
<li>We have the opportunity to translate present Coop’s successes into new regions,</li>
<li>Strengthening linguistic and regional foundations will create new opportunities,</li>
<li>The Coop should have a go-to team when language expertise is required,</li>
<li>Maintaining a formal structure for translation contributions,</li>
<li>To not work in languages other than English is to leave business on the table and risk trust and credibility</li>
</ul>
<p><strong>How will you address it?</strong></p>
<p>This working group will focus on two main initiatives:</p>
<ol>
<li>Translating and promoting core IC content in key languages.</li>
<li>Prospecting and nurturing opportunities in other languages as we build audiences around the globe.</li>
</ol>
<p>While the LOWG establishes itself, all contributions are pro-rata.</p>
<p>For the proposed three month period, the LOWG will continue its focus on Chinese (Mainland), German, and Spanish for its key languages. These languages will feature on the new website and fit current Index Coop capacity. Each language will build on last period’s successes:</p>
<p><strong>Chinese</strong>: <a href="/u/tudou">@Tudou</a> has done a phenomenal job of maintaining platforms for IC content (WeChat, Weibo, and Yuque), translating content in a contextually aware manner, and growing impressions - growing blog impressions 518% in the last two months to 3645 and increasing social media impressions 694% to 71,491 over the same two months. Additionally, new contributors have been introduced. Tudou has built on LOWG activities and is now a key part of the APAC IC community and its activities.</p>
<p>Met content targets of 4-12 blogs per month and exceeded 4x impressions target with 7x for social media and 5x for blog.</p>
<p>To maintain blog cadence and 2x impressions target for both social and blog content.</p>
<p><strong>German</strong>: <a href="/u/ela">@ela</a> and <span>@metigoit</span> both contributed to German content over the two-month initial LOWG period. Though held back due to unforeseen circumstances during the first month, DE content and social media has increased impressions and followers and also featured a new-joiner contribution.</p>
<p>Met content targets overall with 9 for the two months from a minimum required of 8. Started a Twitter channel with a follower target of 50. Almost met with 46 - most added in last month.</p>
<p>To target increased rates of blogging and social activity. Targeting 100 Twitter followers in October.</p>
<p><strong>Spanish</strong>: <a href="/u/sver">@sver</a> has followed <span>@cryptotexan</span>’s playbook on Twitter and has more than doubled followers in two months to 107. Tweeting multiple times per day we are now expecting a breakout. Blogs were posted at the maximum of 12 per month for both months.</p>
<p>Targeting full coverage of key IC content and 250 Twitter followers.</p>
<p>The three languages above will report engagement statistics and seek growth in impressions and followers. Longer term, as we move to the unified IC website, there will be efforts to attribute sales and other conversions, such as content engagement.</p>
<p>During the last two months, the LOWG rewarded consistent contributions in <a href="https://cryptoouf.com/index-coop">French <span>1</span></a>, <a href="https://crypto-sova.blogspot.com/">Russian</a>, <a href="https://nakamomo.substack.com/">Swedish</a>, and Turkish. All met and at least slightly exceeded their blog count target of 4 per month. In the case of the French blog, many more articles were added and they are circulated with a newsletter. For the Turkish content, <a href="/u/insidetrader">@insidetrader</a> moved IC content from his personal blog to a dedicated <a href="https://indexcooptr.substack.com/">Index Coop TR substack</a>.</p>
<p>Japanese and Portuguese contributions joined the LOWG during August and September. Both languages are promising in terms of their demographic coverage and crypto involvement. The LOWG will continue support for both. Notably, <span>@larisaldanha</span> has set up a dedicated <a href="https://lari.substack.com/">substack </a>and <a href="https://twitter.com/indexcoopPT">Twitter for PT</a>. In light of this, Portuguese will be rewarded as an established channel at $1500 per month if the target of 4 blogs a month is met and with an expectation to increase impressions and content engagement.</p>
<p>The LOWG wishes to remain a place for the Coop to find talented and promising DAO contributors. In the previous budget there was little scope for additional funding of contributions. This budget proposal requests funding for 18 blogs in the 3 month period. Recently APAC members have signalled interest in Hindi and there is also Italian as a prospect. It will be the LOWGs task to choose and guide these contributions to evaluate their potential for the Coop.</p>
<p><strong>What impact will this project have?</strong></p>
<p>The LOWG is a supportive group, assisting all other working groups when called upon. Its independence as a discrete working group creates a focused environment for its contributors and acts as a clear point of contact for translation requests.</p>
<p>The LOWG works closely with the Growth Working Group and the Creative and Design Working Group. Often taking its lead from them, the LOWG seeks to further the impact of their work and maximise returns on content without creating additional overhead.</p>
<p>Though currently difficult to attribute, we want to measure the impact of the LOWG by it’s addition to growth and the Coop’s North Star &amp; KPIs. We seek increased content engagement, impressions, and followers across all our channels. We will continue to assess the promise of other languages that currently have Coop content and work to identify where best to expend resources.</p>
<p>As in the last round, key languages (Chinese, German, Spanish) will produce 1 or more IC blogs per week and engage daily on social media. They will deliver statistics relevant to their platforms and channels.</p>
<p>Regular contributors should produce at least 2 pieces of content each month and provide supporting statistics appropriate to their platforms, such as impressions, subscribers, link click-through rates.</p>
<p>The IC should expect to see increased engagement with people from each language worked on by the LOWG. This may manifest as more people in Discord, more attributed purchases, the head of investment at Binance reading our content, or successes such as the group’s members going on to form other groups and business partnerships.</p>
<p><strong>Working Group Lead(s)</strong></p>
<p>Gavin (mrvls_brkfst), stipend - $5000/month</p>
<p><strong>Request for Funding</strong></p>
<p><strong>Proposed Budget</strong></p>
<p>Q4 maximum $80,700. If every language fulfils every possibility and we have three new languages trialling three blogs each. Funds do not need moving from FC because they are contributor rewards.</p>
<p><strong>Use of Funds</strong></p>
<p></p>
<p>Current contributors: ela , sver , Tudou , <a href="/u/blurb">@blurb</a> (nakamomo), Crypto_sova , <a href="/u/cryptouf">@Cryptouf</a> , insidetrader , laridsaldanha  <a href="/u/etsuran">@Etsuran</a> 閲覧用</p>
<p>Note: Social media activity might be covered by impression mining but currently the program is geared to EN content and LOWG contributors are in the early stages of establishing their profiles so some compensation is offered while they gain traction. If a channel transfers to impression mining, it will no longer receive LOWG remuneration for social posts.</p>
<p>By the end of the working group period, we aim to have completed the transfer of key languages to the new site and for the blogs to reside there.</p>
<p><strong>Organization</strong></p>
<p><strong>How will it work?</strong></p>
<p><strong>What will you be doing?</strong></p>
<p><strong>How will you interface with the community?</strong></p>
<p>The LOWG will be managed by mrvls_brkfst (myself). Through Q4, I am keen to mentor contributors as well as help with admin and coordination. I will aim to provide more workshops (similar to this <a href="https://drive.google.com/file/d/1YXFW1F16hvIyoj6PzGzcclsL3y9QBHAN/view?usp=sharing">quick SEO workshop</a>) and to find new ways to leverage our content.</p>
<p>Contributors will manage their tasks independently and as they see appropriate for their language. Contributions will be tracked in the <a href="https://docs.google.com/spreadsheets/d/1RwnvyzR710EDy8J9l-yXST9v-esuoaYaUkc5N_f4KbU/">Index Coop Content spreadsheet <span>1</span></a>. Feedback and reviews will take place. Contributors will be asked to provide statistics relevant to the platforms they use.</p>
<p>Due to time zone challenges, the whole group rarely meets. Communication is via 1:1 calls, chat, and the Discord <a href="https://discord.gg/6wMcCzPG">#language-ops channel</a>. Meetings do take place and are recorded for those who cannot attend. Should a weekly meeting become necessary, it will be facilitated.</p>
<p>Direct requests for translation assistance have so far been manageable and requests may continue via the language-ops discord channel or via myself.</p>
<p><strong>Commitments</strong></p>
<p>I am committed to Index Coop principles.</p>
<p>I am committed to serving the entire Index Coop with my work.</p>
<p>I am committed to open, rapid communication: I know that clear, constant, public communication lifts up the entire Index Coop community. I am highly aware and resolutely committed to this style of communication.</p>
<p>Shared learnings: I will share my progress, learnings with the entire community. I will ensure that anything I create is accessible beyond my own tenure for future generations of Indexers to access &amp; build on.</p>
<p>Intellectual honesty: I am committed to growth and improvement. I am open to feedback and will use feedback to improve my work for the benefit of the entire Coop community.</p>
<p>I am committed to making Index Coop a welcoming, fun, and engaging community to work in!</p>
<p><strong>The Language Operations Working Group opportunity</strong></p>
<p>I believe the value of communication in a person’s native tongue is essential for understanding and trust. For me, Language-Ops and its contributors exemplify what is possible when people work together. The Index Coop is a magnificent recent creation that embodies the great elemental possibilities offered by the Internet and the Cryptosphere - it is a global coordinated effort to build a better future. The Index Coop is best summed up best in its guiding principles and it is with these principles and thoughts in mind that I will continue working to make the LOWG a valuable asset to the Index Coop.</p>
<div><div><div>Final Vote - Approve and fund LOWG for Q4 2021</div><ul><li><div><p><span>96%</span><span>FOR</span></p></div><div><div></div></div></li><li><div><p><span>4%</span><span>AGAINST</span></p></div><div><div></div></div></li></ul></div><div><div><div><span>26</span><span>voters</span></div></div><ul><li>
                    
                    <span>Closed <strong>Oct '21</strong></span>
                   </li><li>
                
                <span>Results will be shown on <strong>vote</strong>.</span>
               </li></ul></div><div></div></div>

**POLL ADDED!**Proposal: Language Operations Working Group (LOWG) Q4 2021

<h2>
<a name="growth-working-group-1" href="#growth-working-group-1"></a>Growth Working Group</h2>
<p>Lemonade and myself are proposing the creation of a temporary Growth Working Group (GWG), responsible for driving usage of DPI (and any other Index Coop products that may arise). While we propose a temporary working group, we’re in favor of eventually transitioning it into a permanent growth committee.</p>
<p>The GWG will streamline current discussions around growth into a single forum and be responsible for approving, funding, and evaluating growth experiments. The overarching goal of the GWG is to increase AUM by increasing awareness of DPI, driving new customers to DPI, and retaining existing DPI customers.</p>
<p><strong>Context</strong></p>
<p>-The Set team is becoming a blocker for growth and BD initiatives to get done<br />
-We’re currently defaulting to inaction and decision by consensus<br />
-Leaders in the community do not feel enabled<br />
-Need to encourage people taking the initiative and setting up meetings w/o needing the Set Team</p>
<p><strong>Why a temporary committee?</strong></p>
<p>-It lets us move quicker, knowing that nothing here is permanent. It will also make us more informed when we set up a permanent growth committee.<br />
-The structure of the treasury committee, which will ultimately fund the growth committee, is still not finalized and so it seems premature to propose a permanent committee without a defined source of funding.</p>
<p><strong>Details</strong></p>
<p>Proposed budget: $100,000 (~20,000 INDEX)</p>
<p>Proposed timeline:</p>
<ul>
<li>First meeting: Jan 5</li>
<li>Initial grants approved: Jan 12</li>
<li>Final meeting: April 5</li>
</ul>
<h2>
<a name="gwg-organization-2" href="#gwg-organization-2"></a>GWG Organization</h2>
<p>The GWG will be managed by a council of three members, with one member coming from Set and two from the Index Coop community. The role of council members is to evaluate and prioritize growth experiments over the three months. There will be a council chair, elected by the members, who is responsible for running meetings, but otherwise has no special power.</p>
<p>The GWG will increase AUM by streamlining the process for driving growth initiatives The council will allocate resources to current growth initiatives and solicit new ones from the community.</p>
<p>The council will evaluate all proposals on the following criteria:</p>
<ul>
<li>Impact: What scale of impact could this experiment have?</li>
<li>Confidence: How confident are we that the experiment will be effective?</li>
<li>Effort: What amount of effort/resources will it take to run this experiment?</li>
<li>Measurable: Are the impacts of this experiment measurable?</li>
</ul>
<p>Every proposal must have a DRI (directly responsible individual) who submits it and takes responsibility for its execution. If the committee is not confident that the quarterback can execute the proposed experiment, they should reject it.</p>
<h2>
<a name="submitting-a-proposal-3" href="#submitting-a-proposal-3"></a>Submitting a proposal</h2>
<p>Ideas should be submitted to the idea pipeline in the form of a memo which details the idea behind the experiment: hypothesis, resources, time to payoff, how to measure, what part of the funnel will this seek to impact, what level of confidence is there, etc?</p>
<p>Example Memo Template:</p>
<ul>
<li>Idea Name: CoinGecko Ads</li>
<li>Hypothesis: Running ads on Coingecko could generate a high ROI in terms of DPI AUM + volume growth</li>
<li>Idea Description: Contact Goingecko in order to understand rates for an introductory package. Gather creative, optimize targeting if possible. Run ads for set amount of time (2 weeks?). Gather data, evaluate.</li>
<li>Metrics to be Measured: CTR (could we set up tracking analytics?), purchase rate, purchase stickiness vs non-ads buyers (longer term analysis), LTV analysis</li>
<li>Use of funds: $2000 for A/B testing of paid ads, $500 for design help</li>
</ul>
<h2>
<a name="growth-dashboard-4" href="#growth-dashboard-4"></a>Growth Dashboard</h2>
<p>Memos will be added to a public Kanban board which organizes growth experiments into various phases based on the prioritization from the council including Unreviewed, Backlog, Queue, Experiments, Analysis, Ongoing, and Discarded.</p>
<h2>
<a name="gwg-operations-5" href="#gwg-operations-5"></a>GWG Operations</h2>
<p>Every week, the growth council would meet and run through the following process:</p>
<h3>
<a name="data-analysisinsight-gathering-6" href="#data-analysisinsight-gathering-6"></a>Data analysis/Insight Gathering</h3>
<ul>
<li>Review the past week’s experiments</li>
<li>How do we impact our growth levers (growth equation)?</li>
</ul>
<h3>
<a name="idea-generation-7" href="#idea-generation-7"></a>Idea Generation</h3>
<ul>
<li>Solicit new memos on a rolling basis. Growth council reviews and prioritizes from kanban board weekly.</li>
</ul>
<h3>
<a name="experiment-prioritization-8" href="#experiment-prioritization-8"></a>Experiment Prioritization</h3>
<ul>
<li>The growth council will prioritize experiments based on an ICE Score:
<ul>
<li>Impact: What scale of impact could this experiment have</li>
<li>Confidence: How confident are we that the experiment will be effective</li>
<li>Effort: What amount of effort/resources will it take to run this experiment</li>
</ul>
</li>
</ul>
<h3>
<a name="running-experiments-9" href="#running-experiments-9"></a>Running Experiments</h3>
<ul>
<li>Prioritized Experiments moved to queue</li>
<li>Test Design: 99% confidence level, control always wins</li>
</ul>
<h2>
<a name="use-of-funds-10" href="#use-of-funds-10"></a>Use of Funds</h2>
<p>The committee is funded with the intention of passing those funds along to growth experiments, and so the vast majority of committee funding is set aside for experiments</p>
<ul>
<li>
<p>Each experiment will have a standard grant size of $2500 to simplify the distribution process. If experiments are showing initial progress and more resources, the committee can allocate up to an additional $7500.</p>
</li>
<li>
<p>There is a $1000 reward for each community member that submits a proposal that is chosen. Committee members are not eligible for this reward, but are eligible for GWG grants.</p>
</li>
<li>
<p>The committee is able to spend 10% of funds ($10,000) at its discretion to further its stated goals. All disbursements will be covered in the committee’s monthly report to the committee.</p>
</li>
</ul>
<p>Committee members will not be compensated out of this initial grant. We believe that they should be paid out of the monthly rewards distribution.</p>
<h2>
<a name="transparency-commitment-11" href="#transparency-commitment-11"></a>Transparency Commitment</h2>
<p>Each month the treasury will share a report with the community that provides updates including</p>
<ul>
<li>Summary of funds spent</li>
<li>Updates on funded experiments</li>
</ul>
<h2>
<a name="faq-12" href="#faq-12"></a>FAQ</h2>
<ul>
<li>Will GWG committee members create and lead ideas?</li>
</ul>
<p>The primary focus of committee members is on delegating and/or working with regular contributors to see the experiments through. However, they are not excluded from ideating/executing ideas.</p>
<ul>
<li>Do the leaders of the GWG need to be incentivized with a fixed income?</li>
</ul>
<p>We believe that the committee members should be paid a fixed income out of the monthly rewards distribution.</p>
<ul>
<li>Should the GWG leaders have a role outside of vetting ideas and distributing capital? (I.E. operational, hosting meetings, etc.)</li>
</ul>
<p>Yes - The GWG leaders are the quarterbacks here and are responsible for holding people to what they commit to.</p>
<h2>
<a name="next-steps-13" href="#next-steps-13"></a>Next Steps</h2>
<p>If the community is supportive of the idea, we’ll solicit candidates from the community and organize voting such that the council will be ready for its first meeting on January 5th.</p>
<h2>
<a name="vote-14" href="#vote-14"></a>Vote</h2>
<div><div><div>Are you in favor of launching a Growth Working Group as Described?</div><ul><li> <span>Yes</span></li><li> <span>No</span></li></ul></div><div><div><div><span>26</span><span>voters</span></div></div><ul></ul></div><div><span>Results</span></div></div>

Launching a Growth Working Group

<p><strong>Proposal to form an Investment Committee</strong></p>
<p><strong>Summary:</strong></p>
<p>In simple terms, Index Coop is an asset management platform with a mission to create widely used crypto structured products. This means that over time, Index Coop will hold a growing number of underlying tokens while managing people’s investments in these tokens.</p>
<p>Just like Vanguard, BlackRock and others, we should aim to provide educational resources and investment insights to investors in our products. Whether it’s a macro piece of research on crypto or an investment thesis for a particular project.</p>
<p>This is a job for an Investment Committee (IC). To analyse and understand the underlying tokens and create investment insights for our investors. This further serves to cement our place in the centre of crypto investing, not just as a product provider, but also as an education and trusted resource.</p>
<p><strong>Abstract:</strong></p>
<p>The role of the IC is to really understand the underlying tokens held in the Index Coop products. Understand their tokenomics, roadmap, governance initiatives, etc. We can think of it as our own internal investment team.</p>
<p>In TradFi, every asset manager has investment analysts, portfolio managers, maybe a CIO and an IC. Published investment research adds to their credibility and helps investors to understand some of the underlying trends and portfolio positions.</p>
<p>I think we need to do the same. There’s an incredible value add opportunity from providing high quality information and research to crypto index investors. Think of it as Messari within the Index Coop.</p>
<p>If approved, the IC would have the following mandate:</p>
<ul>
<li>Cover and analyse the underlying tokens held in the Index Coop products;</li>
<li>Produce “investment insights” style content for internal and external distribution;</li>
<li>Cultivate relationships with crypto &amp; macro investors to challenge and guide our thinking.</li>
</ul>
<p><strong>Motivation:</strong></p>
<p>Simple:</p>
<ol>
<li>It would be beneficial for the Index Coop to have a group of community members who really understand the underlying tokens. This could help for some of the intrinsic productivity analysis, governance proposals, etc.</li>
<li>Adding high quality “investment insights” content will give us further credibility as a structured products platform and create a sort-of educational moat around Index Coop.</li>
<li>Expanding our contacts and building relationships with crypto investors could lead to positive second-order effects. An example would be <a href="/u/lemonadealpha">@LemonadeAlpha</a> getting the Maker whale to abstain on the governance proposal to add DPI as collateral.</li>
</ol>
<p><strong>Specification:</strong></p>
<p>At this stage I propose that the IC has 4 members, meeting weekly. Each member will be responsible for covering individual tokens as the primary analyst and producing “investment insights” content for their respective token.</p>
<p>The IC will also seek out industry experts and crypto investors as guest speakers. This will help the IC to form macro views and create macro content, while raising the profile of the Index Coop in the crypto community.</p>
<p><strong>For:</strong><br />
Form the Investment Committee as per the above proposal.</p>
<p><strong>Against:</strong><br />
The Investment Committee is not necessary at this point.</p>
<p>Thanks <a href="/u/darkforestcapital">@DarkForestCapital</a>, <a href="/u/overanalyser">@overanalyser</a> , <a href="/u/thomas_hepner">@Thomas_Hepner</a> and <a href="/u/devondefi">@DevOnDeFi</a> for reviewing this proposal.</p>
<div><div><div>Investment Committee Proposal</div><ul><li> <span>FOR: Form the Investment Committee as per the above proposal.</span></li><li> <span>AGAINST: The Investment Committee is not necessary at this point.</span></li></ul></div><div><div><div><span>24</span><span>voters</span></div></div><ul><li>
                
                <span>Results will be shown on <strong>vote</strong>.</span>
               </li><li>
                   
                  <span>Votes are <strong>public</strong>.</span>
                 </li></ul></div><div><span>Vote now!</span></div></div>

Proposal to create an Investment Committee

<h2>
<a name="proposal-growth-working-group-ii-1" href="#proposal-growth-working-group-ii-1"></a>Proposal: Growth Working Group II</h2>
<h3>
<a name="situation-2" href="#situation-2"></a>Situation</h3>
<p>I, Lemonade, along with <a href="/u/reganbozman">@reganbozman</a>, am proposing the funding of Growth Working Group II for 3 months, ending on June 15th, 2021.</p>
<h3>
<a name="what-is-the-core-problems-you-want-to-solve-3" href="#what-is-the-core-problems-you-want-to-solve-3"></a>What is the core problem(s) you want to solve?</h3>
<p>GWG I was formed to address inefficiencies in small project funding for growth initiatives. While successes were had in the first iteration, we have identified a number of opportunities for improvement.</p>
<p>The core problem we want to tackle now is: the Coop is not guided by a holistic growth strategy</p>
<h3>
<a name="gwg-i-4" href="#gwg-i-4"></a>GWG I</h3>
<p><strong>What happened:</strong><br />
-Unincentivized AUM from $9m to $90m<br />
-PoolTogether Program<br />
-Analytics Infra<br />
-Loopring Liquidity Mining<br />
-Research/Content Arm<br />
-AMAs with Exchanges<br />
-Paid programs in motion<br />
-User survey funded<br />
-Bitmart listing</p>
<p><strong>What we liked:</strong><br />
-Bias towards action, quick allocation of funds<br />
-Attempts at reporting transparency<br />
-Venue to get involved<br />
-Growth of unincentivized AUM &amp; supply was strong</p>
<p><strong>What we didn’t like or could do better:</strong><br />
-Too focused on experiment solicitation, not holistically owning growth strategy<br />
-Focused too much on top level metric out of our control (AUM &gt; Impressions)<br />
-Memo solicitation wrong model &gt; needs to skew more top down<br />
-Splitting payments w/ treasury<br />
-More substantial updates from us</p>
<h3>
<a name="why-is-this-worth-addressing-today-5" href="#why-is-this-worth-addressing-today-5"></a>Why is this worth addressing today?</h3>
<p>Growth is necessary for survival and success of the Coop. Growth means we are successfully continuing our mission of evangelizing and making our products available to customers who can benefit from them.</p>
<p>Without a clear growth strategy, it makes it hard to know what efforts to focus on.</p>
<h3>
<a name="how-will-you-address-it-6" href="#how-will-you-address-it-6"></a>How will you address it?</h3>
<p>The GWG’s overarching goal will be:</p>
<ul>
<li>Executing the following growth strategy to guide the Coop through at least the end of Q2-21
<ul>
<li>Distilling our core value into the right message</li>
<li>Prioritizing channels to meet our customers where they congregate (en masse)</li>
<li>Making our products widely available when customers decide to buy</li>
<li>Maximizing productive opportunities to assist with retention</li>
</ul>
</li>
</ul>
<p><strong>Activities the GWG will oversee:</strong></p>
<ul>
<li>Product Launch marketing</li>
<li>Awareness/Acquisition (Impressions):
<ul>
<li>Paid/Sponsorship</li>
<li>Content</li>
<li>Social</li>
<li>Viral (Referral, etc)</li>
</ul>
</li>
<li>Activation (Conversions)</li>
<li>Exchange Listings // Wallet Integrations</li>
<li>DeFi Partnerships</li>
</ul>
<h3>
<a name="what-impact-will-this-project-have-7" href="#what-impact-will-this-project-have-7"></a>What impact will this project have?</h3>
<ul>
<li>Impressions (across Twitter, Content, Paid/Sponsorship)</li>
<li>Unincentivized Supply Growth // Unincentivized AUM</li>
<li>Exchange Listings</li>
<li>Productive Integrations</li>
<li>Secondary KPIs:
<ul>
<li>CAC/LTV</li>
<li>Supply locked in secondary (non-LM) contracts</li>
<li>DEX Liquidity</li>
<li>CEX Availability</li>
<li>Retention</li>
<li>Unit Retention</li>
<li>Holders</li>
<li>Avg Holdings</li>
</ul>
</li>
</ul>
<p>Working Group Leader(s)</p>
<ul>
<li>Lemonade (Peter): <a href="/u/lemonadealpha">@lemonadealpha</a>
</li>
<li>Regan Bozman: <a href="/u/reganbozman">@reganbozman</a>
</li>
</ul>
<h3>
<a name="request-for-funding-8" href="#request-for-funding-8"></a>Request for funding</h3>
<p><strong>Proposed Budget:</strong></p>
<p>$450k over 3 mos + $6,000/mo per Leader</p>
<p><strong>Use of Funds:</strong></p>
<p>Funds will be allocated toward contributor stipends and both known and unknown programs.</p>
<p>Estimates:</p>
<p>-Contributor Stipends ($100-150k)<br />
-Contributor ad hoc rewards<br />
-Zerion Partnership ($100k)<br />
-Referral Program ($35k)<br />
-Ad Programs ($60-90k)<br />
-Impression Mining ($20-50k)<br />
-PoolTogether ($25k)<br />
-Exchange Listings ($100k)</p>
<h3>
<a name="organization-how-will-it-work-9" href="#organization-how-will-it-work-9"></a>Organization - How will it work?</h3>
<p>The GWG will be managed by a council of four members, with two members coming from Set, and two from the Index Coop community. The role of council members is to prioritize and execute against growth programs which are sourced from members within.</p>
<p>The GWG leaders will have leeway to assign stipends for regular contributors—both full-time and part time—and will have discretionary funds to reward and incentivize activities (I.e. impression mining).</p>
<p>The GWG will continue to use an experiment-based approach with a key difference being that the generation of ideas will be sourced from regular contributors and leaders themselves. With GWG II, there will be little to no reward for idea submissions. Instead, the operating structure will have a heavy focus on rewarding execution of the prioritized initiatives.</p>
<p>GWG Leaders will meet weekly to discuss the progress of initiatives and strategize on how to allocate funds to best serve growth functions. New experiments will be sourced from each leader from conversations around the coop and individual brainstorming.</p>
<h3>
<a name="how-will-you-interface-with-the-community-10" href="#how-will-you-interface-with-the-community-10"></a>How will you interface with the community?</h3>
<p>Weekly Reports. GWG will generate a weekly update on their progress and publish to the Index Coop governance forum. Reports will include:</p>
<ul>
<li>High Level Metrics per product (w/ trends): TVL, uTVL, Holder Count, Impressions</li>
<li>New initiatives</li>
<li>New Content Pieces</li>
<li>GWG Financial position</li>
</ul>
<h3>
<a name="commitments-11" href="#commitments-11"></a>Commitments</h3>
<p>I am committed to <a href="https://docs.indexcoop.com/our-guiding-principles">Index Coop principles <span>4</span></a></p>
<p>I am committed to serving the entire Index Coop with my work.</p>
<p>I am committed to open, rapid communication: I know that clear, constant, public communication lifts up the entire Index Coop community. I am committed to this style of communication.</p>
<p>Shared learnings: I will share my progress, learnings with the entire community. I will ensure that anything I create is accessible beyond my own tenure for future generations of Indexers to access &amp; build on.</p>
<p>Intellectual honesty: I am committed to growth and improvement. I am open to feedback and will use feedback to improve my work for the benefit of the entire Coop community.</p>
<p>I am committed to making Index Coop a welcoming, fun, and engaging community to work in!</p>
<div><div><div>Approve GWG II</div><ul><li><div><p><span>91%</span><span>FOR</span></p></div><div><div></div></div></li><li><div><p><span>9%</span><span>AGAINST</span></p></div><div><div></div></div></li></ul></div><div><div><div><span>22</span><span>voters</span></div></div><ul></ul></div><div></div></div>

Proposing a Growth Working Group (Pt. II)

<p><strong>Title:</strong> Proposal to form a MetaGovernance Committee<br />
<strong>Contributors &amp; Feedback:</strong> <a href="/u/lavi">@Lavi</a>, <a href="/u/cedrick">@cedrick</a>, <a href="/u/ncitron">@ncitron</a>, <a href="/u/kiba">@Kiba</a> &amp; <a href="/u/anon10525910">@anon10525910</a><br />
<strong>Date:</strong> May 28, 2021</p>
<p><strong>UPDATE: Please see addendum at the bottom for updates to this proposal.</strong></p>
<p><strong>Summary</strong></p>
<ul>
<li>We don’t reach quorum on a majority of meta-governance votes. There appears to be voter fatigue around meta-gov related votes, which are increasing in frequency.</li>
<li>By not engaging in meta-governance for most votes, we are missing an opportunity to further build trust and rapport with the protocols within DPI and build value for Index Coop.</li>
<li>
<strong>UDPATE:</strong> <em>We propose to continue community MetaGov voting as is, and delegate all DPI-related meta-governance votes to a dedicated, elected committee, in case we do not reach quorum on the regular vote.</em>
</li>
<li>This committee will consist of well-informed governors that cast their votes on behalf of Index Coop. This is a change from the current meta-governance process as detailed here: <a href="https://docs.indexcoop.com/governance/meta-governance">Meta-Governance <span>6</span></a>
</li>
<li>Members of the committee are voted in for a 3 month period, with a backstop to recall or replace members in case needed.</li>
</ul>
<p><strong>Problem</strong><br />
While the current meta-governance process is not generating major problems, it’s not ideal either. Some issues are highlighted below:</p>
<ul>
<li>
<strong>High manual effort</strong> - The current voting process requires a few hours of work from Greg, Cedrick and others, each time a new vote is live or a vote ends. This effort exists, whether we reach quorum or not (which we often don’t). Further, most of the effort is done by the Set team and we see a potential to hand over some tasks to the community.</li>
<li>
<strong>We hardly reach quorum</strong> - An analysis of the most recent meta-governance votes shows a clear picture:</li>
</ul>
<p></p><div><a href="https://global.discourse-cdn.com/standard10/uploads/theindexdao/original/2X/9/94af2835e290bf64fec9be7cca7aff2a9e048968.png"><div>
<span></span><span>1229×623 141 KB</span>
</div></a></div><p></p>
<p><strong>Finding:</strong> Looking at the last 15 votes, we only reached quorum 4 times. That’s only 27%, meaning the Index Coop has <strong>not participated in 73%</strong> of the most recent meta-gov votes.</p>
<p>Often, even when IIPs and meta-gov votes are added to Snapshot at roughly the same time, the meta-gov vote has dramatically lower engagement.</p>
<p><strong>Why?</strong> While we haven’t done a thorough analysis, we can make a few educated guesses.<br />
First of all, the frequency of meta-gov votes has increased quite a bit over the last two months. We can assume that we already witness voter fatigue, as there is a declining voting participation. The voting frequency will only increase more, now that Balancer and Yearn are live and others may come online in the future.</p>
<p>Another reason might be the nature of these votes. Most of them are “house-keeping votes” that are not met with great interest or cause much debate. The only time we saw disagreeing votes was for “Adding renFIL to Aave” and “Add TUSD to COMP”.<br />
Even though most of the votes are “just” housekeeping, it still takes time and brain juice to get properly informed about the Pros and Cons of each vote. Hence, we conclude that meta-governance is becoming less important (or even a burden) for most INDEX holders.</p>
<p><strong>Proposed Solution</strong></p>
<p>We propose to form a Meta-Governance Committee (MGC) that is given full delegation of all meta-governance votes. The MGC is inspired by the Spartan Council implemented by Synthetix. The MGC will become a subset of a larger Meta-Governance Working Group (to be proposed separately) to house all meta-gov efforts, including the MGC, the Protocol Ambassador Program, voting operations and execution (to the extent not addressed by this proposal), and further designing, expanding and experimenting with meta-governance at Index Coop.</p>
<p>Below is a break-down of how this committee will be structured:</p>
<ul>
<li>All meta-gov votes held by INDEX holders are delegated fully to this committee</li>
<li>Committee members are voted in by the IC for a 3 month period</li>
<li>It is the MGC’s responsibility to thoroughly review, analyze and execute votes to fulfill Index Coop’s meta-governance duty and privilege</li>
<li>The committee initially will consist of 5 people
<ul>
<li>We want to ensure we reach the right balance of agreement, security and efficiency</li>
<li>This number should hold, even if more protocols are added, as the MGC will be supported by the advice of the protocol ambassadors</li>
<li>The number can be adjusted later if needed</li>
</ul>
</li>
<li>A 3 of 5 majority is required for the MGC to vote on meta-gov proposals
<ul>
<li>Votes will then be executed directly by the Set team or by the committee itself via multi-sig [to be discussed with the Set team]</li>
</ul>
</li>
<li>The committee will adhere to our meta-governance principles
<ul>
<li>These are general guidelines for voting that will be published in a separate forum post</li>
</ul>
</li>
<li>The committee is supported by the protocol <a href="https://gov.indexcoop.com/t/calling-potential-protocol-ambassadors/1485">ambassadors <span>3</span></a>
<ul>
<li>Each ambassador is a “protocol-specialist”, ideally with some experience or social capital within the underlying protocol and who is actively keeping up with each protocol’s latest developments</li>
<li>Each protocol ambassador will serve as an advisor to the MGC should there be a vote that isn’t getting clear consensus or needs to be better understood</li>
</ul>
</li>
<li>Each MGC member monitors all new meta-governance votes, each with a focus on a particular protocol(s):
<ul>
<li>The MGC members collectively discuss new proposals and analyze them on their merits and against the meta-governance principles</li>
<li>The MGC connects with the ambassador for that protocol to discuss the vote, if it is non-routine housekeeping or to get a sense of community sentiment</li>
<li>The MGC executes the vote</li>
<li>The MGC reports back to Index Coop as to how the MGC has voted, providing an explanation of the decision in case there was a notable reason to do so</li>
</ul>
</li>
<li>INDEX holders can call for any or all MGC members to be replaced at any time via IIP and Snapshot vote as a backstop in the unlikely case of major MGC / Index Coop disagreement</li>
<li>The MGC will report all decisions/votes back to Index Coop in a transparent way (e.g., at minimum, announcing each vote to Index Coop and, for any votes which are more controversial or disagree with the majority, providing an explanation for why MGC voted in the way it did.</li>
</ul>
<p><strong>Motivation - Why a Meta-Gov Committee</strong></p>
<ul>
<li>With all meta-gov votes delegated to the MGC, INDEX holders are relieved from having to participate in the growing number of meta-gov votes, freeing time and energy for other tasks, including voting on IIPs</li>
<li>We believe that this will ensure informed decision-making (which is not solved with lowering quorum or rewarding votes as described above). There are generally no discussion on Discord or the forum regarding live meta-governance votes, so it appears most votes are either (i) cast without much research about the topic, (ii) are obvious, such as with simple housekeeping proposals, or (iii) are not cast, and we don’t reach quorum.</li>
<li>Technical implementation is very simple and fast, as it only requires turning off Snapshot support for meta-governance and delegating the votes to 5 addresses (one multisig, and 2 EOAs)</li>
<li>This solution is a first initiative to solve the current problems, and does not exclude any other ideas from being explored or implemented (e.g. governance mining or staked meta-gov Index)</li>
<li>Consistent, thoughtful and well-informed meta-governance participation is key to building trust with each of the protocols underlying DPI.
<ul>
<li>When it becomes clear that Index Coop is going to show up to each meta-gov vote with the millions of dollars of votes of each protocol held by DPI, and there being a specific group in charge of executing those votes, each protocol will be encouraged to reach out and work with us, especially as DPI grows.</li>
<li>When there are proposals at underlying protocols which bring direct value to Index Coop (e.g., listing of DPI as collateral, etc.), we know that we will be able to adeptly vote DPI’s tokens in support.</li>
<li>This fits within our greater meta-governance framework and is key to building an unforkable moat around our products and DAO.</li>
</ul>
</li>
</ul>
<p><strong>Who is the MGC?</strong></p>
<p>We believe that the MGC should consist of dedicated Index Coop community contributors (silver and gold owls, or people from Set and DFP).</p>
<p>First of all, we want to ensure that votes are cast with the best intent for the IC and the DeFi ecosystem in general. And secondly, while we still rely on specialist knowledge, we want to keep a certain neutrality and prevent too much bias towards one single protocol. This is very important as we do have competing protocols among the underlyings.</p>
<p>Below sets forth our proposed initial make up of the MGC:</p>
<div>
<table>
<thead>
<tr>
<th>IC MGC Member</th>
<th>Background</th>
</tr>
</thead>
<tbody>
<tr>
<td>Cedrick</td>
<td>Core contributor to Index Coop meta-governance efforts</td>
</tr>
<tr>
<td>Lavi</td>
<td>Core contributor to Index Coop meta-governance efforts</td>
</tr>
<tr>
<td>Greg</td>
<td>Core contributor to Index Coop meta-governance efforts, member of the Set team</td>
</tr>
<tr>
<td>Kiba</td>
<td>Long-standing Index Coop contributor with strong ties to many protocols underlying DPI</td>
</tr>
<tr>
<td>Noah (Ncitron)</td>
<td>Long-standing Index Coop contributor who has built and been deeply involved with IC’s technical meta-governance execution</td>
</tr>
</tbody>
</table>
</div><p><strong>Rewards</strong></p>
<p>We believe that MGC members should be compensated for their involvement, and will detail rewards if/when this proposal converts to an IIP based on community feedback.</p>
<p><strong>Conclusion</strong></p>
<p>The MGC is our solution for meta-governance as both Index Coop and meta-governance scale. By having the MGC, Index Coop will be able to participate in every meta-governance vote. As a consistent, thoughtful participant in meta-governance with tens of millions of dollars worth of votes per protocol, we will be able to strengthen our ties with each protocol, expand our influence in the DeFi ecosystem, and support those proposals which are most important to Index Coop.</p>
<p>The delegated meta-governance voting committee proposed here is obviously a departure from how Index Coop currently conducts meta-governance, so please provide any feedback or concerns (and apologies for the long post).</p>
<p><strong>Sentiment Check</strong></p>
<div><div><ul><li><div><p><span>73%</span><span>Yes let’s proceed with this proposal</span></p></div><div><div></div></div></li><li><div><p><span>27%</span><span>No, we want to keep our voting power</span></p></div><div><div></div></div></li></ul></div><div><div><div><span>15</span><span>voters</span></div></div><ul><li>
                
                <span>Results will be shown on <strong>vote</strong>.</span>
               </li></ul></div><div></div></div>
<p><strong>UPDATE June 7th 2021</strong><br />
After a great discussion in the weekly planning call on Monday and taking into consideration the forum discussion, we recognize that part of the community is not fully comfortable with the approach we proposed in this post. Main concerns are:</p>
<ul>
<li>Meta Governance is part of the value proposition of the $INDEX token</li>
<li>Some people like to vote and want to participate</li>
<li>There should be a way to opt-in / -out of delegation to the MGC</li>
</ul>
<p>While we recognize these valid concerns around HOW we solve this, it seems that everybody is aligned with the goal about WHAT we want to achieve: That is, to vote on every meta-governance vote and doing so in an informed way.</p>
<p>Taking into account the inputs from the community, we would like to iterate on the above approach by proposing a new solution, where delegation of voting power only occurs, if quorum is <strong>not</strong> reached via the regular community vote. In summary:</p>
<ul>
<li>
<p>If we reach quorum on a MetaGovernance vote, the vote is executed accordingly (as done today)</p>
</li>
<li>
<p>If quorum is not reached, however, we propose that the MGC has full discretion to decide on the vote, as described above</p>
</li>
</ul>
<p>This iteration will ensure that the community keeps its full voting power. And at the same time, this also ensures that the MGC is able to step in on the votes that the community does not care enough to participate. We think that this should strike the right balance between community voting power and IC participation in meta governance.</p>

COLLECTIVE DAO CATALOG

Proposal for the creation of the People, Organization and Community (POC) WG - UPDATED

[FINAL POLL CLOSED] Proposal: Governance Operations Working Group

POLL ADDED Proposal: Engineering Working Group Request for Funding

POLL ADDED!Proposal: Language Operations Working Group (LOWG) Q4 2021

Launching a Growth Working Group

Proposal to create an Investment Committee

Proposing a Growth Working Group (Pt. II)

Updated Proposal to form a MetaGovernance Committee

Got something to add?