Different approaches to mission development, interaction paths, and energy focus. Both excellent adventures for community development.
In product-communities, a small team creates a product and mobilizes a community that supports and rallies around the mission.
Then the community helps shape the product through active input, advocacy and partnership in testing as well as adoption.
In community-products, a community forms around a mission and then begins to create an internal set of tools that are then added to product lines, sold, and scaled.
The products emerge from community experiments, supporting the scale of the community as a priority.
And of course, this is not a binary - just variables in a large multidimensional space.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
This week we will be looking at the DAO Digital Space Design - thinking holistically about all the virtual (and physical) interfaces that community members interact with:
Once community comms infrastructure in place, then comes parallelisation: mission, projects, incentives, governance.
But no scale until reliable comms in place for community mobilisation. A strong influential network lead is a shortcut… but unsustainable, point of failure.
In the short term, effective. In the long term you need to replace personal network influence with tech power. And that means inspiring comms delivered at scale. In other words: fan development.
Key issue tho is that fan base can be double edged sword. So you want sober active advocates for long term community sustainability.
Every community should have a living manifesto, that get's reviewed every season, and re-written from scratch every age (4-5 seasons).
It is the north star, a call-to-action, and summary of values, and a primary form of alignment between new members.
A well-written manifesto should be an articulation of the vibe, a spawner of memes, and a decision framework for potential as well as current contributors.
✨Some news✨
I'll be joining @viamirror team as their DAO Lead! 🪞
My journey into web3 started in 2014, as a crypto-lurker, then a year and a half ago I fell into the rabbithole of digital communities. And barely 2 months ago I decided to go full web3.
What a ride.
In the role, I'll be supporting Mirror's journey to full decentralization:
- Building community infrastructure
- Mobilizing the most talented group of web3 writers, creators, and communities in our space today
- Nurturing an ecosystem of mutual support and D2D partnerships
A short reflection - because wow.
A year and a half ago I came across @ribbonfarm, which led to the @yak_collective and @JonathanHillis's writing, which in turn drove me to community twitter and @rosiesherry's incredible course on building minimum viable community.
Five types of community messaging:
- Sharing (Ideas, News)
- Signalling (Direction)
- Scheduling (Events)
- Summary (Newsletter)
- Sh*tposting (Connection)
We need interfaces that can handle them all, and create feeds tailored by type.
Sharing ideas evolve often from a dedicated channel, into some signalling milestone - then into gDocs, knowledge mgmnt or exploration interface. Very fragmented today.
Signalling evolves often into soft and hard voting. From various channels into proposal drafts (gDocs) finally into polling interfaces (Snapshot)