Hack Future of Work: Hackathon Archive

[annaalexakr]

Motivation

During the transition of Foundation responsibilities to the DAO, we asked ourselves the question: how do we navigate the path from Foundation bootstrapped Community department to fully decentralized teams working for the protocol?

Summary

To explore this question Community Development hosted an internal hackathon, Hack Future of Work, to look at the different paths to contributing in the DAO and to give contributors a change to ideate on what this transition could look like.

For two weeks we paused all Comm-Dev related projects and programs and asked all contributors to consider the prompt: in 6 months, what does Community Development look like beyond the Foundation?

We outlined three different paths: contributors could propose a Core Unit, join an existing Core Unit, or Community Development can transition into the DAO in a re-defined context.

For contributors interested in exploring the option of a Core Unit we proposed a prompt: what does a sustainable working unit in the DAO look like?

Teams work for two weeks and presented their progress at a weekly stand up. The rest of the contributors gave feedback and suggestions on how the proposals could be improved.

As the result of the Hackathon, one team that presented at demo day went on to formally propose themselves to the community as a Content Production Core Unit and got ratified in April 2021.

Role(s)

• Hackathon facilitator
• Project leads to set up meetings for relevant teams to work together

Related Links

• Hack Future of Work Presentation
• State of Comm Dev 2021
• Hackathon Retro
• MIP39c2-SP5: Content Production Core Unit, MKT-001
• Core Unit Launch Pod Sessions ||| Session #5: Content Production Core Unit, MKT-001

Lessons & Recommendations

• Things to improve: More collaboration sessions to help form teams and share ideas.
• More programming related to learning about the Core Unit Framework, more facilitation of learning about the process would have been helpful.
• There is a lot of overlap in function of Core Units in development and operational support is needed to help teams coordinate better.
• Teams found it challenging to navigate administrative, financial, and legal side of creating a Core Unit.
• A retro uncovered many takeaways for what worked and what didn't. Overall it was a successful exercise to introduce community members to the Core Unit Framework and provide the space to test ideas before formally proposing them to the wider community.
• Reach out to @annaalexak on Maker Chat or Twitter with further questions.

🏆 Trophy Case