I recently participated in a series of design challenges geared towards training designers on the intricacies of designing for Web 3. It was one of the challenges that prompted this project.
<aside> ❓ Newbies face difficulties before making their first meaningful contribution to a DAO: finding DAOs to join, understanding what they stand for, and how to make their first meaningful contribution. How would you solve these problems?
</aside>
https://twitter.com/druids01/status/1552835708586434560?ref_src=twsrc%5Etfw">July
UX designer - Favour
UX writer - Zainab
A DAO is a decentralized autonomous organization. It is an association of people that come together but without the shortcomings of regular communities and organizations. This means that things like problems with hierarchy, problems with decision making, and fund management are alleviated because the organization is now “decentralized” and “autonomous”.
Because it’s a new concept, greater importance is placed majorly on it being functional for the average Web 3 contributor but not on users new to the Web 3 space. This makes it difficult for the DAO to onboard new members that might be interested in these communities.
We started by scouring the internet for information about DAOs and how they’re currently being run.
We discovered that there are sites like Boardroom, DAOstack, and DAOHaus that provide users with access to different DAOs which they can choose from.
This was when we realized we could use a tech community we were both a part of as a case study. RoadTrip Community is a tech community consisting of designers, developers, and product managers who help each other in their tech journey. Initial research showed not many members were familiar with DAOs, so we dove deeper with usability testing on these DAO explorers to see how easy it was for members of the community to navigate and make a contribution using the current market offerings. It would also provide an essential foundation for design strategy, data to back up our design decisions and identify early adopters who would be interested in using this product.
My goals for the session were to find out: