Been noticing a fork in how web3 orgs are evolving:
• Product-Communities (@guildxyz)
• Community-Products (@FWBtweets Dashboard)
Different approaches to mission development, interaction paths, and energy focus. Both excellent adventures for community development.
• Product-Communities (@guildxyz)
• Community-Products (@FWBtweets Dashboard)
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.
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.
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
