Motivation(s) for this role

<aside> 💡 Explanation of what leads to this role being created

</aside>

• Our Notion Architecture (naming, order, and organisation of pages) could benefit from many improvements, most of which are small and reversible changes. For making many small changes and quickly iterating to refine them, our decision-making process has too much friction. As such, it's more effective to create a role and appoint 1-3 people who can quickly make changes, receive feedback, and improve our Notion Architecture in an agile manner.

Thoughts and Deliberation

• I (Drea) had thought that Notion was open. Anyone could make a page, anyone could edit and comment. And that some people felt empowered to do big moves (e.g. you and me a few months ago), but that most people just didn’t do that because they didn’t feel like they should.
• My preferred approach has us lock down the top level, but let anyone add and edit pages within their own areas, without needing to ask for permission.
• Adding a page or category at the top 1-2 levels would be a request to the Architect
• The architect could theoretically go down to sub-sections and clean things up, especially if topics get split into different pages in different places.

What I’m worried about:

• people avoiding putting rough stuff in Notion because they need to get permission
• That rough stuff ending up in Discord, where it’s an even worse mess
• what happens at scale, how do we keep it tidy if we have 300 people adding stuff?
  • Maybe scale is when we need Clarity, so we can token gate different sections. Otherwise we need some permission management process

Agreements

Role Agreements:

• Purpose: 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).
• Accountabilities: specific tasks or responsibilities for which the role is accountable in its Unit or in RnDAO. If the Role has no specific commitments towards RnDAO/its Unit for any accountabilities, leave empty.
• Domains: areas over which the role has exclusive decision-making authority. Domains are used to transfer authority from RnDAO global or the Unit where the Role sits towards the exclusive domain of the Role (i.e. the role decides on behalf of the Unit and on behalf of RnDAO).