About a week ago, we published this tweet and received a flood of responses:
Documentation and team knowledge management is a sore spot for DAOs. There are no web3-native solutions available, so we’re stuck clobbering together tech stacks made up of the usual web2 suspects: Notion, Google Docs, Roam.
In this article, we lay out what we think DAOs need in collaboration tools to get our work done. We then evaluate the current tools on the market to see how they stack up, including our own tech stack. Finally, we present our CabinDAO dream feature set — a Frankenstein doc tool that takes the most DAO-friendly features of a number of web2 tools.
We pulled from our experience writing docs and managing projects for CabinDAO. We asked other folks in the web3 ecosystem who are building DAOs and protocols to share their experience and team workflow, as well.
Finally, we didn’t differentiate between writing and collaboration tools (ex. Google Docs) and knowledge management tools (ex. Notion). For a DAO, informal notetaking, documentation, and publishing all fall under the team communication umbrella. We want a tool that takes us from meeting notes and brainstorming all the way to the approval process for final changes.
And with that, let’s dive in.
Enabling multiplayer access is the hardest problem DAOs face in knowledge management, specifically per seat pricing and access.
This is because traditional companies have a very clear line between employee and non-employee. As a result, enterprise software pricing charges per employee onboarded onto the product and designed with this structure in mind.
In contrast, DAOs have a gradient of engagement. At any point in time, a DAO will have a handful of major contributors and concentric circles of participants, members, Discord lurkers, and the public.
This naturally touches on the problem of access. Traditional companies with over 300 workers have entire IT departments who give, revoke, and manage each user’s access. Most DAOs have one or up to a handful of people who manage permissions for a group of similar size.
Enterprise apps generally do a decent job at multiplayer access. Google Docs has the ability to manage individual document permissions. Notion also has a function to set pages as public or private. But paying per seat for non-contributors, just for them to be able to view and comment on shared documents, doesn’t make sense for DAOs.
The ideal scenario for access in a DAO is the permeable Wikipedia contribution model. Wikipedia has a power law distribution amongst contributors and editors. It remains an open source movement that doesn’t distinguish between an employee or a non-employee, but also has various gating mechanisms that outputs quality information over time.
Enterprise knowledge management apps that cater to traditional companies expect a top-down structure. Projects and assignments are then assigned to individuals and groups from upper management.
In contrast, DAOs are more like a network of independent contractors interacting with each other than a company of employees. They have a bottoms-up structure where contributors write their own job description and propose projects for approval to the broader community.
Github, for example, encourages open source contributions and allows a built-in review process that ensures the quality of the contribution. It also allows developers to add issues for features they would like to work on and assign it to themselves. Github encourages decentralized project management.
When a would-be contributor submits a proposal, the ideal knowledge management software should be able to pull the DAO’s governance or approval process, match that with the project’s specs and scope, and estimate compensation.
Most DAOs, CabinDAO included, clobber together web2 apps to collaborate and disseminate knowledge. But these duct tape measures won’t cut for long.
With web3-native apps, DAOs can manage permissions on the doc as a group, rather than relying on a single member to gatekeep access. Instead of constantly adding new users and removing ones who leave, web3 assigns permissions programmatically. This means that DAO membership — usually signified by the existence or lack of a token or NFT — dictates access, not a fallible individual.
“When I sign into a web3-native tool with my address, the tool can look up my status in the DAO. It then shows me what I have access to while simultaneously hiding what I don’t. This programmatic feature works the same way for deciding whether to give editing or viewing permissions to an individual.”
A more advanced web3-native feature would be the ability to tie projects to bounties. And maybe even embed payment structures within the projects to pay guild members out, based on a DAO-determined contribution level.
Knowledge management is a pain point for CabinDAO across the board. We're using Roam, Google Docs, Notion, and Discord all at once because none of them do exactly what we need.
We use Notion for sharing general knowledge about the DAO and our long-term vision. We love Notion’s WYSIWYG (versus Markdown) and its ability to manage permissions on a contributor and page level.
We admit it: Notion solves at least half of the problems we need for documentation and knowledge management, However, as an enterprise tool, Notion costs $8 – $20 per user per month. Without workarounds, onboarding the over 300 members of CabinDAO’s Discord server would be exorbitant and unwieldy.
We use Roam Research for project management and internal knowledge management.
Roam’s multiplayer user structure fits us. Anybody can contribute to our Roam server, without being able to delete what anyone else wrote. In this way, it’s better than Google Docs or Notion for access. Its bidirectional linking structure also makes it excellent for bottoms-up project management.
From our experience, however, Roam’s bullet-based interface isn’t a great fit for longer form writing. For folks who aren’t familiar with its block-and-bullet point structure or with Markdown, Roam has a steeper learning curve.
There’s a similar notetaking application called Obsidian that some folks use, but unlike Roam, it lacks multiplayer functionality.
We use Google Docs for collaborative writing. It’s nice because the commenting and multiplayer features are strong. However, Docs doesn’t have interlinking capabilities. And it still has the obsolete Microsoft Word-like writing experience even after all these years.
(We know –- if it’s not broken, don’t fix it. But c’mon we’re in the web3 era, here).
We’ve never used HackMD, but it was a tool that was recommended quite a few times in the thread so we spoke to a couple web3 teams who do.
One cool thing about Hackmd is that it integrates with Github. This way, document edits can go through a formal pull request review process before they get pushed live.
Clarity is the only app on this list aiming for DAOs as their target audience.
Our team just started testing Clarity so we turned to outside input for in-depth insight.
Foster — a writing community that isn’t a DAO but functions like one — switched from Notion to Clarity for their team’s knowledge and project management. They found that Notion got bloated quickly. Customizing their tasks began taking up too much time.
The Foster team likes Clarity for how it handles both tasks and knowledge. Foster co-founder Stew Fortier says, “Clarity is excellent because it's low-maintenance. If you're up late writing something brilliant, you can easily spin up a couple of tasks and assign them directly in the document so that your brilliant vision has a higher likelihood of seeing the light of day.”
Our initial tests of Clarity found that bidirectional linking is a challenge. While its current pricing model is still on a per-user basis and stores data on a traditional web2 architecture, the Clarity team has shared their plans with us to tweak their model to serve DAOs better.
According to founder Richie Bonilla, Clarity wanted to solve the problem of human coordination first. They’re actively working with their users to find the best way to approach decentralizing the app.
DAOs need a way to create, edit, and disseminate knowledge in a way that's web3 native. The current tools available are mostly web2 tools. They just aren't built for a DAO’s bottom-up, multiplayer needs.
At CabinDAO, we dream of a knowledge management tool that combines the most web3-like features of the best web2 collaboration tools on the market. We want …
We’d love to hear from you. What does documentation and knowledge management look like for your web3 org?