Community Architect for web3 startups 🏰 DAO Strategic process development consultant 🔮 Building at pubDAO & mClub 🎉 https://daoxd.xyz/
Community Architect for web3 startups 🏰 DAO Strategic process development consultant 🔮 Building at pubDAO & mClub 🎉 https://daoxd.xyz/
Subscribe to DAO Experience Design | by Brownrygg
Subscribe to DAO Experience Design | by Brownrygg
Share Dialog
Share Dialog
<100 subscribers
<100 subscribers
When building a web3 community there are a lot of factors to take into account.
Like, what content to create, or what to add to the discord, who do we reach out to, how do we select quality contributors, what should we measure and what is pointless to measure?
If we understand the change we are seeking to make for a group of people we are seeking to empower, then we have a frame of reference for how to approach these factors.
For instance a discord structure that seeks to manage a pump and dump group will look different than one wanting to make an NFT movie. Also, the kinds of people joining a pump and dump group or an NFT movie community are likely to have very different levels of interaction and dedication.
One factor that is difficult to name and tends to ignore any frame of reference for the change we are seeking to make are the mysterious voices of expectation in our heads. Even if the change we make is crystal clear, the seemingly infinite context of web3 creates endless space for voices to distract us from doing the work.
“Why you doing it this way, over there they do it much better.” ”You don’t need a system for that, it creates too much friction.” ”They are not going to like it like that, it’s too simple.”
And so we stop and start. Second guessing every decision we make - drowned out by the voices of expectation.
One approach to silencing the voices is to get very clear on who you exactly you are seeking to empower.
When the voices of expectation start yelling all we have to do is compare those voices with the actual expectation of those we seek to empower. If they are aligned, perhaps it’s time to pause and re-access a direction.
If one has nothing to do with the other, move on.
***************
Learn more about DAO Experience Design:
👇 Join my telegram channel by subscribing below 👇
When building a web3 community there are a lot of factors to take into account.
Like, what content to create, or what to add to the discord, who do we reach out to, how do we select quality contributors, what should we measure and what is pointless to measure?
If we understand the change we are seeking to make for a group of people we are seeking to empower, then we have a frame of reference for how to approach these factors.
For instance a discord structure that seeks to manage a pump and dump group will look different than one wanting to make an NFT movie. Also, the kinds of people joining a pump and dump group or an NFT movie community are likely to have very different levels of interaction and dedication.
One factor that is difficult to name and tends to ignore any frame of reference for the change we are seeking to make are the mysterious voices of expectation in our heads. Even if the change we make is crystal clear, the seemingly infinite context of web3 creates endless space for voices to distract us from doing the work.
“Why you doing it this way, over there they do it much better.” ”You don’t need a system for that, it creates too much friction.” ”They are not going to like it like that, it’s too simple.”
And so we stop and start. Second guessing every decision we make - drowned out by the voices of expectation.
One approach to silencing the voices is to get very clear on who you exactly you are seeking to empower.
When the voices of expectation start yelling all we have to do is compare those voices with the actual expectation of those we seek to empower. If they are aligned, perhaps it’s time to pause and re-access a direction.
If one has nothing to do with the other, move on.
***************
Learn more about DAO Experience Design:
👇 Join my telegram channel by subscribing below 👇
No activity yet