Unifying Knowledge and Task Management

Constant context switching this entails leads to substantial hurdles in efficiency and information loss. We can help with that.

Currently, DAOs use many tools within their governance pipeline. This includes community wide Telegram/Discord group chats, smaller group chats for core contributors, governance forums, and voting tools like Snapshot. Essentially, this translates to the fact that for one to be adequately knowledgeable about both the context and content of a proposal, one needs to keep abreast of happenings across multiple channels, withstanding a significant amount of context switching. 

Quite a tall order, especially in the informational barrage that is Web3. 

This is problematic for both new entrants and existing members alike. 

This has to do with the high levels of fragmentation within the essential tools required for project management within Web3. Discussions, voting, payments, project management and information flows are all done  on separate platforms. This poses a particular problem when it comes to DAOs tackling particularly complex and impactful goals, as they need to attract experts from outside the Web3 silo to be able to reach their goals.

For example, DeSci DAOs like VitaDAO, Cannabis Genome DAO and BitDAO all need world class researchers to bring their visions to life. The perceived barrier to entry is greatly increased because of the fragmented nature of DAO workflow tools, thereby making it significantly harder for such DAOs to be able to onboard essential contributors into Web3. 

Context switching is damaging to existing contributors’ participation too, as it can lead to operational inefficiencies such as misunderstandings and communication breakdowns/failures.

DaoLens integrates discussions, forums, and voting into one app; eliminating context switching.

 As anyone that switches through many apps works, it is a boon to be able to link tasks and proposals to discussions. This problem is multiplied when managing a project in a group. Managing multiple projects, each with multiple people, on multiple  tools, is clearly not the most efficient way of execution. Let’s dive into how these functions are implemented on our tool:

Information Flow:

As of now, keeping up with any particular DAO’s calendar/list of announcements is quite cumbersome. This is compounded by the fact that there is no ‘standard’ means of doing so, meaning that one must be acquainted with each particular DAO’s specific way of doing things. For example, some might rely more on Discord-through an announcements channel, pinned messages, or just mere messages from the admins. Others might use Twitter more-either through spaces or simple Tweets. Evidently, this implies that one must either use multiple platforms to keep up to date with whatever number of communities they are a part of. This is both an annoyance and invariably leads to people missing out on sometimes vital information.

DaoLens’ tool solves this issue by using a ‘one stop shop’ including an events feed, discussion forum, governance proposals, and a bounty board. Furthermore, users can create proposals and tasks directly from discussions. The tool also includes the ability to upload certain documents and news pertaining to any bounties, proposals or events, unlocking the ability to contextualise the nature of the action at hand. Contributors no longer need to trawl through Twitter, Discord, individual forums and then Notion and Jira to be able to know the happenings of their DAO and find and execute work.