PIP: [to be assigned]
Title: Community Contribution Initiative
Created: Aug 10, 2021
PieDAO remains one of the most underrated communities and asset management protocols in the space - albeit it being one of the largest. As mentioned in @gabriele’s Inside the Bakery: How We Build Pies publication, PieDAO “employs an open and responsive process for the modeling of its different Pies through discourse.” and rightly so. It is imperative that PieDAO (the protocol) and PieDAO (the community) generate an effective synergy to not only maximize feedback but to welcome & challenge innovative ideas that will propel PieDAO to reach critical mass.
I’ve been a part of PieDAO since the early days. It’s an amazing group, and still one of the most authentic, exciting projects and communities I’m in. But I think we’re leaving a great deal of potential momentum and energy on the table when it comes to the DAO.
The last couple of weeks I’ve been chatting with some folks and observing and I wanted to feedback some of what I’ve seen and heard.
What I’ve seen and heard:
- This community has largely developed organically, and grown via word-of-mouth and shared interests and values
- Across all of our core areas - from product to marketing to biz dev and new offering development - there are opportunities to add value and pick off some low hanging fruit that will advance the DAO and our users
- As our roadmap and ambitions increase, we’ll need more capacity to drive development, strategy, and growth of the DAO
- Every week, new and existing members raise their hands to help out or contribute in some way, sometimes directly with a specific offer, sometimes indirectly by asking how they can help
- There is no clear way to contribute and help out for members interested in doing so
All in all, we have a need for more contribution, and a community asking to contribute more.
How do we make it easier for people to propose, find, commit to, and execute work for the DAO?
I’d like to propose the creation of two Community lead roles, supported and with direction by @jnova and myself, focused on managing the ongoing engagement of the community, and working with the core team to build the infrastructure, processes, and cadence to consistently align would-be-contributors from the community with key strategic projects, priorities and needs.
In short, make it easier for the right community member to propose/identify and execute the right contribution.
I propose the funding of a 4 month probationary period focused on the following:
- Project/Task identification (what should the community work on?)
- Incentive system and tooling (how should it be incentivized?)
- Accountability and management (how do we drive completion and quality?)
- Strategic alignment (how do community contributions connect to the core product and DAO roadmap?)
- A place where valuable projects are scoped well and collected (backlog)
- A standardized process to source new project proposals from the core team and the community
- A system for incentivizing and rewarding community contributions
- Help relevant community members discover, commit, and complete backlog projects
- 2 x half-time Community Leads across different key timezones
- Supported by core team
|Resource||Total Cost (4 mth)||Funding Method|
|Community leads (2)||24000 $DOUGH + Dollar component to be discussed||Monthly: 3000 $DOUGH each per month. TBD dollar amount a month per CL|
|Tooling / Software||As needed||Ad hoc|
|Contributor Incentives||As needed ($DOUGH)||Ad hoc|
- Increase the conversion of community members to contributors, as measured by…
- Primary KR: # of contributor-executed projects
- Secondary KRs:
- Number of Backlog projects/proposals/bounties listed
- Number of member interests/skills submitted
Deliverables (potential, amendable)
- Contributor system:
- Standardized proposal system
- Backlog of DAO needs and potential contribution areas
- Community member skills/capabilities intake system
- Bi-weekly opportunity update
- Community onboarding flow towards contribution
- Prioritized integrated strategic roadmap
- Standardized templates for core outputs:
- Scope / Scoping questions
- Consistent communication: The group will update the DAO weekly on progress and asks
- Transparent work process: The group will run the work on open channels, with open participation
I look forward to hearing feedback and answering any questions.