Web3 has a marshmallow problem | #5
Web3 has a marshmallow problem. In the 1970s Stanford conducted a well known experiment that tested the correlation of delayed gratification with long term success. In brief, a set of children were put in a room alone with a marshmallow. They were told that if they didn’t eat the marshmallow before the adult returned they would get two marshmallows. Majority of the kids stuffed themselves. However, the minority that waited for the adult to return were better able to deal with frustration and ...

Designing web3 for wonder | #1
Have you ever been curious, neigh - wondered, why the word ‘wonder’ is used so frequently in the web3 space? WonderFi Wonderland Protocol Wonderverse The Alice in Wonderland theme seems to be a strong metaphor for web3. But what does that mean? That we’re all just Alice on an uncontrollable rollercoaster ride of bunnies, mushrooms and morally ambiguous characters? I hope not. I mean, if we truly want to share the magic of web3 with the rest of the world - replying to the emotions that come wi...

Right Actions = Appropriate Context | #51
This anecdote is often overlooked, yet vital in web3 communities. The acts of observing, contributing and participating are fundamentally separate acts with different desired outcomes. If we don’t create the appropriate context for these acts to be performed, the fundamental structure we build the community and culture on will be unaligned. Unaligned foundations never stood the test of time. This unalignment happens because if we do not present a desired action to a human within a context tha...
Community Architect for web3 startups 🏰 DAO Strategic process development consultant 🔮 Building at pubDAO & mClub 🎉 https://daoxd.xyz/
Web3 has a marshmallow problem | #5
Web3 has a marshmallow problem. In the 1970s Stanford conducted a well known experiment that tested the correlation of delayed gratification with long term success. In brief, a set of children were put in a room alone with a marshmallow. They were told that if they didn’t eat the marshmallow before the adult returned they would get two marshmallows. Majority of the kids stuffed themselves. However, the minority that waited for the adult to return were better able to deal with frustration and ...

Designing web3 for wonder | #1
Have you ever been curious, neigh - wondered, why the word ‘wonder’ is used so frequently in the web3 space? WonderFi Wonderland Protocol Wonderverse The Alice in Wonderland theme seems to be a strong metaphor for web3. But what does that mean? That we’re all just Alice on an uncontrollable rollercoaster ride of bunnies, mushrooms and morally ambiguous characters? I hope not. I mean, if we truly want to share the magic of web3 with the rest of the world - replying to the emotions that come wi...

Right Actions = Appropriate Context | #51
This anecdote is often overlooked, yet vital in web3 communities. The acts of observing, contributing and participating are fundamentally separate acts with different desired outcomes. If we don’t create the appropriate context for these acts to be performed, the fundamental structure we build the community and culture on will be unaligned. Unaligned foundations never stood the test of time. This unalignment happens because if we do not present a desired action to a human within a context tha...
Community Architect for web3 startups 🏰 DAO Strategic process development consultant 🔮 Building at pubDAO & mClub 🎉 https://daoxd.xyz/
Share Dialog
Share Dialog

Subscribe to DAO Experience Design | by Brownrygg

Subscribe to DAO Experience Design | by Brownrygg
<100 subscribers
<100 subscribers


Whenever we design anything, we are designing it for someone. If we don’t understand the context of who this someone is, and what their intent is while using our design, chances are it will not work as well as it could.
The same principle applies when we design DAOs. We are not (our shouldn’t be) designing just to design, but for the benefit of making someone’s life better.
The key question is; who is ‘someone’ and what is their intent?
Before we spend hundreds of hours on member interviews and testing, we can make some assertions on what all ‘someones’ have in common within the context of joining a DAO.
Here are some traits of someone looking to join a community that I have seen from my experience. I have phrased them in the intent form ‘someone wants to.’
Someone wants to Observe.
Someone wants to Participate.
Someone wants to Contribute.
These three intents follow a very basic structure that aligns with the Polyvagal Theory also known as the science of safety and belonging. It’s likely that you have followed the same structure before you joined your first DAO or community.
In the context of a DAO, I have found it beneficial to frame these three intents as basic roles that can be used to design meaningful member experiences.
Observer role.
Participant role.
Contributor role.
Each role comes with its own context, expectations and appropriate actions; and if we can make those easy to understand, follow and execute is makes creating a wonderful experience more likely.
It behooves the DAO designer to understand why each of these intents exist, and how to structure them into their communities.
In the next three posts I will dive into each one of them, and unpack how they could help you more easily create meaningful experiences for your members.
************
Learn more about DAO Experience Design:
👇 Join my telegram channel by subscribing below 👇
Whenever we design anything, we are designing it for someone. If we don’t understand the context of who this someone is, and what their intent is while using our design, chances are it will not work as well as it could.
The same principle applies when we design DAOs. We are not (our shouldn’t be) designing just to design, but for the benefit of making someone’s life better.
The key question is; who is ‘someone’ and what is their intent?
Before we spend hundreds of hours on member interviews and testing, we can make some assertions on what all ‘someones’ have in common within the context of joining a DAO.
Here are some traits of someone looking to join a community that I have seen from my experience. I have phrased them in the intent form ‘someone wants to.’
Someone wants to Observe.
Someone wants to Participate.
Someone wants to Contribute.
These three intents follow a very basic structure that aligns with the Polyvagal Theory also known as the science of safety and belonging. It’s likely that you have followed the same structure before you joined your first DAO or community.
In the context of a DAO, I have found it beneficial to frame these three intents as basic roles that can be used to design meaningful member experiences.
Observer role.
Participant role.
Contributor role.
Each role comes with its own context, expectations and appropriate actions; and if we can make those easy to understand, follow and execute is makes creating a wonderful experience more likely.
It behooves the DAO designer to understand why each of these intents exist, and how to structure them into their communities.
In the next three posts I will dive into each one of them, and unpack how they could help you more easily create meaningful experiences for your members.
************
Learn more about DAO Experience Design:
👇 Join my telegram channel by subscribing below 👇
No activity yet