- Problem: A core DAO value is transparency but the BanklessDAO is losing transparency as it grows in size and complexity
- Proposal: This proposal introduces the role of DAO Cartographer to mitigate this trend
- Benefit: The DAO Cartographer would create and maintain a map of the DAO to support transparency, enhance accountability, improve onboarding, and reduce communication overhead.
- Create a graphical map of the Bankless DAO to increase membership & organization visibility of our current (and ever-changing) structure and goals.
- Train guild and project representatives to easily maintain their own local maps to aid in keeping things up to date.
- Dramatically increase transparency and accountability across the entire community supporting the DAO’s goal of improving coordination efficiency and higher quality collective decisions.
The newly minted ops-guild role of ‘DAO Cartographer’ seeks to create this program with the accountabilities of:
- Seeding and maintaining this graphical map of the DAO,
- Training guild and project representatives to help manage accurate records of membership and participation; and
- Facilitate maximum visibility for the evolving and growing BanklessDAO organizational graph.
“Cartography is the study and practice of making and using maps. Combining science, aesthetics, and technique, cartography builds on the premise that reality can be modeled in ways that communicate spatial information effectively.” - Wiki
- Improved transparency – clear map of who does what and how they’re compensated
- Enhanced accountability – commitments to each other made clear and progress towards shared goals tracked
- Self-serve Onboarding – browse what’s happening in the DAO; find the spot that matches your passions and skills with DAO needs.
- Monthly Active Users (MAU) of the Map
- #of Map Edits/Updates per month.
- #of Feedback & feature request tickets
A number of interesting opportunities for improvement have emerged as our vibrant DAO has evolved and grown that the DAOCartography program seeks to tackle:
In Season 1 we rapidly decentralized the DAO. Autonomy was granted to guilds via their own seasonal funding and multi-sigs. Guilds were encouraged to create localized role and governance structures. The grants committee (GC) was formed with delegated powers to make ongoing fund distribution decisions. Additionally, some projects also matured to a state of local multi-sig, roles, and rewards models.
This has made the DAO quite nimble and things evolved quickly, but if you weren’t a member of the local team it became hard to see how things were changing. Emerging org patterns were shared mostly by chat in Discord by members who actively participated in multiple guilds. This word of mouth sharing impeded learning and borrowing from one another quickly. Some artifacts exist outlining who has been elected to do what, how they got into those positions, and what they’re accountable for… but it isn’t easy to piece the resulting picture together across disparate Discord chatter, Sesh polls, Discourse proposals, Snapshot votes, google docs, and Notion pages.
We are upholding the DAO value of being transparent, but it isn’t fulfilling the intended benefit. How might we make it easier to quickly get a clear picture of what’s going on and who’s helping to make that happen?
A benefit of the decentralized approach to treasury management, 20 multi-sigs at time of writing, is that local patterns of rewards and rewards distribution have emerged. This allows each guild and project to experiment and find optimal patterns of talent engagement and coordination. A diversity of patterns emerged but it is not easy to get a sense of how compensation works across the DAO. Guidance was provided early in Season 1 of an approx. 1,000 BANK per hour of work; but this is only a guide and many remuneration patterns have emerged:
- Roles with stable responsibilities have a “seasonal salary” elected in by Team (e.g. Ops Guild)
- Local Coordinape Epoch at the end of a season or when project Milestones are achieved (e.g. DesignGuild, BountyBoard)
- Bounty or tip culture layered in for well defined recurring work (Writers Guild, Design Guild)
- Some have discussed a ‘basic income’ for those deemed ‘core contributors’ (BountyBoard)
- Most are likely a hybrid of all of the above and other patterns the authors have not observed directly
This diversity and experimentation is a feature, not a bug. How might we make it easier to:
- Keep track of the local customs?
- Calibrate for ‘relative fairness’ across teams/guilds?
- Easily borrow from the patterns of other teams?
When new members join, aside from bounties, it’s not very easy to take a self-directed approach to finding ways to meaningfully contribute. Recently there’s both guild select and project select as a means of discovering at a high level what’s happening --unlocking the channels to attempt to uncover more. Correspondingly, it’s hard for projects to signal that they need help. What results is a very conversationally intensive (and slow) approach to coordination. New members introduce themselves, select channels, introduce themselves again in ‘start-here’, DM with peeps, then attend some calls if they can align to the standing call time, and only then possibly are they able to carve out a first task.
How might we make it easier to:
- See a catalogue of open ‘roles’ like an internal job hiring board?
- Search for members with specific skills who are open to DAO work?
In the corporate world there’s an org-chart; that notoriously nasty thing that’s a clear reminder of who has been given ‘power over’ you. DAOs delightfully flip this model on its head, but the absence of an org-chart and employee directory can make it hard to picture how a DAO is organized. Visualizations, maps, pictograms, and infographics are powerful communication tools that help the human mind embrace complicated and complex domains.
In the early days of a DAO ‘Discord as OrgChart’ was more or less fine. It has a simple structure of categories and channels arranged as an indented list. Enter Season1 and that indented list is absolutely huge and few can ‘drink from the firehose’ and actually build a picture of the DAO in their mind’s eye. Which leaves you with two bad choices: turn on the firehouse and be overwhelmed or turn it off and miss something.
Notion is even more flexible and unbounded which makes it great as a Wiki and guild or project knowledge repository but it doesn’t create a quick-to-understand picture of the DAO, it’s instead more of a rich knowledge repository of meeting notes, project and guild resources, etc. But only if you know which page to go to and/or win the Notion global search lottery.
How might we create:
- A visualization of the DAO that acts as a place to get a high-level picture?
- A better jumping off point into the richer knowledge repositories and coordination tools like Notion?
- The ability to guild- and project-select in Discord with better up-front context?
Discord and Notion aren’t scaling well. Especially as we rapidly grow and further decentralize ops and governance. The DAOCartographers recommend experimenting with augmenting our current tooling with a more purpose-built mapping and visualization solution. Discord is excellent for real-time communication and Notion is an extremely flexible Wiki / KnowledgeBase; but neither gives an easy to digest picture of the DAO’s structure and membership.
Sobol is a purpose-built tool for creating and editing maps of decentralized organizations. First introduced and utilized by Consensys and more recently adopted by DAOs. The stated aim is to give these types of vibrant and dynamic communities an easy to navigate and maintain map of how teams and members have agreed to work together. (Kinda like GitHub for your DAO-DNA)
Disclosure: @Bpetes is a founding member of the Sobol team in addition to participating in BanklessDAO since Season0 in ps-guild, design-guild, and bounty-board-project. Sobol has been offered up free to use for the DAO for Season 2 in exchange for feedback. If there’s interest after S2 and the DAO feels the tool was useful, a modest token stream of BANK to Sobol, commensurate with value discovered would be a welcomed discussion for Season3+.
The following features are listed in proposed relative order of recommended adoption:
- Visual DAO Structure Maps
- Team & Role Profiles w/ treasury management, governance, and comp summary info. and links out to Notion/Gnosis/Snapshot etc. where helpful
- Member Directory
- Discord based automated User Provisioning & Login (no emails required)
- User profiles with skill tags
- Project ‘Heartbeat’ (cc: @Kouros @tommyolofsson we saw your awesome recent post related)
- Milestone and KPI tracking dashboard for projects
- Project Update ‘posts’ prompted automatically by DiscordBOT
- OrgMap Widget
- No login required interactive map of the DAO embedded on our bankless.community site
- Set up an initial map of structure that can be used as a base to build from
- Enable Discord integration to automatically provision members into Sobol directory
- Install SobolBot
- Create new Discord role tags ‘Sobol Admin’ and ‘Sobol Editor’
- Proposed permission mapping is as follows:
- Sobol Admin = Administrator access in Sobol
- Level2 = Editor access in Sobol
- Sobol Editor = Ability to give non-Level2s editor access in Sobol where needed
- Level1 = Added to Member Directory in Sobol (can edit profile); otherwise, View Only access
- All others can log in with Discord and browse Sobol in ‘guest mode’ but don’t have a member profile.
- Setup member profile templates and encourage folks to log in and fill out.
- Training material (sessions for guild/project reps who want to be editors)
- How-to guides and vids (Notion)
- Recruit from current guild reps and project rep roles
- Set up a way to gather feedback on the program
- DAOCartography Biweekly mapping AMAs (open to all and recorded)
- Work with ‘first quests’ to get a link into the map in advance of guild/project select step so folks can select with more context
- Work with Grant Committee and Project Leads to form agreement to experiment with milestone tracking and project updates in Sobol
- Periodic (end of Season?) DAOwide feedback surveys with users and KPI share-out to continually evaluate the solution approach and adjust course
The Bankless community has been and continues to be the pioneer in Defi education, DAO innovation, and Web3 promotion and awareness. The community has consistently front-run the opportunity and this proposal is in keeping with this pattern.
While this proposition has an immediate benefit to the BanklessDAO, the implications of its approach and mindest have far reaching consequences. The challenges we face today relating to DAO visibility and scaling are being faced by all DAOs across the ecosystem. The timing could not be more critical as we have the chance to build and develop solution patterns and primitives that will be leveraged across all of Web3 in the years to come.
This includes advancing the cause and vision behind things like:
- Self-sovereign identity: The power to define your identity(s) and its connections.
- Web3 social networks: The opportunity to turn today’s vicious circle of digital feudalism into a virtuous circle of collaboration and cooperation.
- Digital Citizenry: If DAOs are the next evolution of digital nations, then its graph of members is the directory for the new world’s citizenry.
If Etherscan is the standard in on-chain transactional transparency, consider the potential power and value of a “Etherscan for layer zero”. By experimenting with @TeamSobol on this, Bankless is in a strong position to play ‘navigator’ on Sobol’s roadmap and pitch collaborations with bDAO tooling projects to make this possible. Such is the expansive vision and potential impact behind this proposal.
If you believe in the vision and power of Web3, then you know these things are inevitable, not just possible. The only question is whether we will play a significant part in building this vision and have the boldness to be a first mover.
This all starts with having a map of our own DAO. BanklessDAO cannot make precise decisions without a clear picture of how we operate, so we urge you to vote yes on the proposal.
- YES - Let’s execute the program roadmap
- NOT YET - Wrong timing or needs more definition
- NO - Wrong solution defined