<aside> 💡 about this doc: This document is designed to be a comprehensive template that can be used for a proposal and then have ongoing use to define the Units functioning (useful to clarify the rules and functioning for contributors, clarify any doubts from those external to the Unit, avoid conflicts and misunderstandings by ensuring alignment upfront on key issues, etc).

Related documents: Research Project Strategy Canvas

RnDAO

</aside>

Purpose

<aside> 💡 the guiding question, purpose or reason for the Role or Units to exist. This is often defined as who+why (who is the unit serving and what needs or aspirations does it seek to address for them).

The purpose might change as per: How much decision autonomy this Unit has?

</aside>

We’re concerned with two pain points in the DAO ecosystem:

  1. DAOs struggle with a lot of archaic practices in spite of the existence of tools. The use of spreadsheets instead of treasury management & comp tools. Using web2 tools instead of web3 project management tools.
  2. And even if there’s a discernable interest to explore web3 tools, there’s a lack of educational content around them with proper comparative analysis & demos. This hampers adoption. Poor profiling makes it difficult for customers to enter a long-term relationship with new tools. Vendor profiling factors include startup runway, roadmap, features & competitive analysis. What happens when you’ve developed a relationship with a tool only to find out that they’re broke & may shut down quickly, creating a mess of a transition for the concerned team?

To address these pain points, this project unit, a collaboration between the Clique Podcast, RnDAO & DAOMasters, aims to deliver a deep dive series for the DAO tooling ecosystem.

RnDAO Agreements (RnDAO level guidelines that the unit follows or not)

Unit Agreements

How much decision autonomy this Unit has?

Role Agreements

Unit2Unit and Unit2Role Agreements