Proposal co-authored by Shpadoinkal and Z33
Introduction: We, the community members of OlympusDAO, recognize the importance of transparent and effective communication with external parties and the broader community. Clear and timely communication plays a vital role in building trust, fostering collaboration, and ensuring the long-term success of our decentralized autonomous organization. With this proposal, we seek to formalize the responsibility of the Olympus Governance Council (OGC) for ongoing communications, while allowing for delegation to functional counterparts when necessary to actually broadcast messaging. We’d implore the community as well as the DAO to consider the spirit of this proposal primarily and work with us in improving the text of the proposal, we are open to suggestions and edits and don’t intend for this to be bogged down by minutiae. Considering the whole fiasco around Cooler Loans we think improving and formalizing DAO to Community communications and assigning responsibility for it can help prevent a repeat.
Objective: The objective of this proposal is to ensure that the Olympus Governance Council (OGC, as established by OIP-91) takes primary responsibility for all communications surrounding Governance and proposals. By doing so, we aim to establish a clear point of contact for stakeholders, enhance consistency in messaging, and streamline decision-making processes related to communications. We understand the OGC is not ultimately responsible for final decisions and that authority rests with the OHM token holders, but we consider timely communications around OIPs/TAPs etc to be part of OGC’s role as an overseer.
Proposal Details:
OGC Responsibility: The OGC shall be formally responsible for all ongoing communications around OIPs, serving as the voice of the DAO. This responsibility includes but is not limited to:
a. Canvassing and summarizing the view of Olympus DAO around every proposal that makes it to snapshot. Such summary should cover important context such as feasibility in terms of resources, timelines, interaction with other components. This will serve to avoid a repeat of recent series of unfortunate events surrounding TAP-28, where important background information needed for arriving at an informed decision hadn’t been finalized and was still in flux at the tail end of the voting period and timelines mentioned in the TAP were found to be totally unreasonable from the DAO’s perspective. We mandate that the OGC provide a link to this summary in the snapshot itself, as well as with the announcement for the snapshot on discord and twitter. This should be done in no more than 1 week from the day informal voting ends.
b. Crafting and disseminating announcements, updates, and important information to the broader community surrounding these votes.
c. Engaging with community members through official communication channels. Community calls should be held when any proposal makes it to snapshot, with at least 3 days left to vote. At least 1 OGC member should be available for these community calls .
d. Responding to queries, feedback, and concerns from community members and external parties in a timely and professional manner on an ongoing basis
Note: If the above is too much to ask, we propose that the DAO hire a dedicated Communications person(s), and pay them similar to what is currently paid monthly to the Community Manager. We suggest a number around $3000 to $4000/month, and this compensation should come by lowering the compensation of all the OGC members proportionally.
Delegation to Functional Counterparts: While the primary responsibility for communications lies with the OGC, they are encouraged to delegate specific communication tasks to functional counterparts within the organization. This delegation should be based on the expertise, availability, and workload of individuals or teams. Functional counterparts should work closely with the OGC to ensure alignment and consistency in messaging. Examples of these functional counterparts include:
- Learn team members, or the paid Community Manager(s), for disseminating timely information on the Discord
- Marketing team members, for disseminating timely information on the official Twitter.
Collaboration and Coordination: The OGC should establish clear channels of communication and collaboration with functional counterparts to facilitate efficient information sharing and decision-making. Regular meetings, designated communication channels, and collaborative tools should be utilized to ensure smooth coordination and avoid any communication gaps.
Guidelines and Best Practices: The Leadership Council, in consultation with the community, should develop clear guidelines and best practices for effective communication. These guidelines should cover topics such as tone, language, responsiveness, and transparency. Regular reviews and updates to these guidelines should be conducted to adapt to evolving needs and community expectations.
Reporting and Accountability: The OGC should provide quarterly reports to the community regarding communication efforts, initiatives, and key outcomes. These reports should be accessible to all community members and serve as a means of accountability and transparency. Each failure to provide these quarterly reports as well the summary along with the snapshot votes should result in monetary deduction from any bonus the OGC may be entitled to at the end of the year. We suggest a deduction of 5% for each snapshot summary missed, and a deduction of 10% for each quarterly report missed/delayed from the final bonus amount.
Implementation and Timeline: Upon final approval of this proposal (through snapshot), the OGC shall begin the implementation process immediately. The following timeline is suggested:
Within one month: The OGC shall define roles, responsibilities, and channels of communication for functional counterparts.
Within two months: Clear communication guidelines, cadence and best practices should be established and shared with the community.
Ongoing: The OGC should provide regular updates and reports to the community regarding communication efforts.
Conclusion: By formalizing the responsibility of the OGC for ongoing communications, OlympusDAO can establish a solid foundation for transparent and effective communication. This proposal emphasizes the importance of clear lines of accountability while allowing for delegation to functional counterparts. We believe that this approach will strengthen community engagement, foster trust, and contribute to the long-term success of OlympusDAO. We invite all community members to support this proposal and actively participate in shaping the future of our decentralized organization. We request the community to provide feedback to this RFC, based on community feedback we will add appropriate polling options. For now the community is encouraged to vote on whether it considers the general thrust of this proposal something that is required or not.