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.
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.
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.
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.
Community scale is based on parallelisation, not sequential speed. Investing in core foundations to support multiple decoupled projects is the key.
Reflecting on this thought: why does it feel like traditional companies are constrained by this? What are the characteristics that help parallel execution vs. coupled dependencies?
I wish I had understood the power of poetry decades ago.
Alas, it’s something that needed to be found on its own timeline.
I totally misunderstood the power of language for so long - it’s as much a tool to communicate with others, as a way to communicate with your selves (emphasis on the plurality there).
Building digital-first communities follow an interesting path - you have to build communication scaffolding prior to allowing strategy, governance and longer-term components emerge.
In some ways this requirement was hidden from obvious need since in-person work provides you that scaffolding for granted: synchronous conversation and dialogue.
The C*nst*t*onDAO is an absolutely excellent case study for the future of memetic swarm power, networked movements, populist democracy, and poor time-based decisions.
Folks should pay close attention and write 1000s of articles. This show is just getting started 🍿
If you are a community manager, DAO summoner, or contributor - I encourage you to read through the history of this monumental financial flash mob, it’s power, weaknesses, and, importantly, it’s mistakes.
Career progression in digital-first organizations seems different. In interlocking networks there is dynamic upward mobility, instead of convergent paths. What are the consequences of this? How will people shape their journey?
In the emerging space there are four levels of rewards, which intuitively are associated with varying levels of status and power:
- No Payment
- Grants / Projects
- Grant Allocation (DAO to Guild to Project to Member)
- Role Based 'Salary' (UBI, (opt by level or skill xp)
- Subjective Contribution (e.g. via Coordinape)
- Objective Network Activity (e.g. via SourceCred)
Digital-Native Organization Compensation Framework:
POTENTIAL REWARD DIMENTIONS:
- Community Tokens
- Partnership Token
- Other Rewards: NFTs, Events
Ok, so I'd like to add a plug-in to my website (currently in Notion) where people can purchase a set of services via crypto?
Let's say for example, someone wanted to buy a 1-hour advisory/coaching session.
1. They would go to my website 2. Browse 2-3 types of services (e.g. chat, interview, research) 3. Purchase via crypto transaction a token redeemable via burn for the service (edition NFT?)
“We are desperate for Creator platforms in HR: we want to create learning content, employee journeys, feedback systems, back-to-work tools, reporting and analytics interfaces, and lots of communication and change programs….
We don’t want HR Tech platforms that “do what is designed” – we want systems that let us create our own content, our own customizations, and our own innovative ideas. So in many ways, all HR Tech platforms are becoming “Creator Systems.”
- Tipping and shoutouts for good work, democratised across the org
- Integration of customers into shared digital spaces with the company
- Transparency in all components of the org, all metrics across all teams
- Minimal mobility friction between jobs, let ppl follow their muse