Skip to main content

Projects

New Projects​

New projects can be submitted for approval by any DAO member using the template below. The new Project is voted upon by DAO membership and a majority vote leads to approval.

Each Project has a lead.​

  • The Lead is chosen when a Project proposal is approved through a vote.
  • Project leads take full responsibility for everything that happens within their own Project.
  • The Lead can add and remove people from their team as they see fit.
  • The Lead is responsible for handling disputes between team members within their project.
  • Leads are responsible for specifying and meeting all output/deadlines within their own division.
  • Leads also work, unless their division is so large that they only have to time to work in a managerial capacity.
  • Each division has defined roles for every member, even if that role is somewhat elastic.
  • The Leader can award bonus stake (eg. for extra work), but must get approval from other DAO Leads. Usually there is an agreed upon * rate.

New Project Template/Example​

1st Phase:​

Submitted By: Jord

Suggested Lead: Jord

Customer: DAO Masons

What problem does this project solve?​

  • Lack of Focus: Setting up a dedicated project allows us to focus on tasks that are immediatley relevant in priority that gets us the greatest benefit. It also ensures that we're working together towards a shared goal.
  • Lack of Economy: While free form building may be good for exploration and overall enjoyment. Most in the DAO need to start earning yesterday. Using a focused project approach to building the DAO allows us to maximize the value we get out of every minute that we work for free.
  • Cold Start Problem: It would be perfect if we could paid to build our portfolio. Unfortunately, we're a deep niche in a troubled market. Most customers would not understand the value of what we're offering until we show them. Which means that we need to build an app to show them the value that we can provide.
  • Momentum There's a large push that's needed to start a DAO and put some energy behind our efforts. We need to see daily reminders of our progress and commitments to keep the motivation high. This project format is good for that.

What are the major deliverables​

  • The Game Design Doc: Documented social coordination mechanisms that are easy to read and are easy to use.
  • The Brand: A basic design that people in space will easily recognize
  • The App: An app that we use to coordinate, that also works as a show room model to attract customers. This app is also our landing page. Needs to shine. Needs attention to detail.
  • An outlet: A place for us to place our thoughts. Could be a custom blog or posted on an existing platform or both. (Optional: discuss)
  • Some Tools: All the basic DAO coordination tools we need to get started. A minimal but organized discord with roles, a place to organize our projects. (what is MVP here?)

Win State:​

All the above initiatives have a simple, basic implementation that performs their function well.

By the end of this project we should have a good idea of how this DAO works and how we coordinate. We have all the basic tools we need to support ourselves and we have demonstrated that we can build a great DAO (both technically and socially) to clients.

We measure success by comparing our goals before embarking on this journey and seeing how many of these goals we hit. Also, I want to hear some 'ooos' and 'aaahs' when people see our app.

Lose State​

What is the major impact of not doing this project

We lose interest and stop building because we're not going in any particular direction. Another DAO lost to coordination entropy.

Futhermore, we fail to demonstrate our own expertise in building a focused, streamlined DAO. Something that we are all interested in building.

What can go wrong?

  • We go in the wrong direction. We spend too much time building stuff without customers. This is why it's important to have 'the hunt' initiative to coincide with this project.
  • No one wants a DAO. Not really in our control. I'd rather know for sure that people don't want a DAO, by building a great example and having them turn us down, then assuming that no one will ever want a DAO.
  • All of our assumptions about building lean, focused DAOs with defined rules are wrong and we make asses of ourselves in public. This is possible. But I'd rather find out that we were wrong than not do it and never know. Or worse, we're right but never do it, and another team with the courage to take on the mission does it while we watch.

2nd phase:​

Timeline: Jan 6th - Feb 22nd (47 Days)

Lead: Jord

Roles Required (Team):

  • Lead/Product Manager/Dev
  • Dev/Design
  • Project Manager/Copy Editing
  • Comms/Community/Oddjobs

Budget & Labour:

Total DAO labour assumptions

UI: 3 hrs/day, weekends off Boiler: 2hrs/day, every day Rowdy: 2.5hrs/day, weekends off Jord: 4hrs/day, one day off (could be more if need be).

UI: 31 days x 3hrs = 93hrs Boiler: 47 days x 2hrs = 92hrs Rowdy: 31 days x 2.5hrs = 77.5hrs Jord: 39 days x 4hrs = = 156hrs

Total DAO labor commitments until EthDenver: 418.5

We agreed in the meeting following the first phase that ideally, this project would use 50% of the DAO's focus. Therefore our total estimated labour for this project is 209.25 hrs

Target Budget: 210 shares

Breakdown of tasks:

Game Design Doc (50hrs):

  • Required Docs:
    • Manifesto
    • Core DAO Mechanics:
      • DAO cultural norms (Summary of the manifesto)
      • How we arrive at decisions (Moloch Governance)
      • What are shares for?
      • What is loot for?
      • Outline of the following rituals.
    • Ritual of Sacrifice (Project Check-In Mechanic (Rough draft finished))
    • Ritual of Ranks (Core Member/Contractors, Onboarding & Removal Mechanic)
    • Ritual of Oaths (Colleague Letter of Understanding)
    • Ritual of Skill (Skill Badge Mechanic)
    • Ritual of Riches (Continuing Engagement & Dividend Mechanic)
  • Drafting (15hrs)
    • One person breaks away and writes down a specific mechanic that we plan to use in the DAO.
  • Discussions (25hrs)
    • We read the docs and make comments (async)
    • We discuss any written disagreements or nuances as a group
    • We arrive at agreements during the call
  • Formatting & Display (10hrs)
    • Edit for grammar and spelling
    • Format to MD
    • Display using a github template or in the app (if time permits)

Branding (5hrs) The basics, a couple logos, brand colors (BG, primary, secondary, warning etc)

  • Logo (mostly done)
  • Tailwind Color Scheme

Comms (8hrs)

Mininum viable Discord: We create a flow for potential customers and members. We have static messages that tell the user what they need to do. We set up a basic spam bot to esure that we're not getting destroyed by bots once we post our Discord on the site.

  • Enable and configure bot
  • Design new onboarding flow
  • Create discord structure (roles & rules) to match onboarding flow

App (134hrs)

A well-crafted app that works as both a tool for DAO coordination and a demonstration of our skill.

Components:

  • Landing Page
  • Claim Action
  • Consultation Page
  • Web2 consultation link (Contact Form)
  • Members Page
  • Services Breakdown Page
  • Projects Page
    • Project page (Timeline of Claims w/ desciptions)
  • Documents Posting (GDD posted to App, nice to have) - updating and ratification actions Description:
  • Mobile First
  • Vite
  • Tailwind for style
  • Optimized for Demos (reliable and visually appealing)

Labour Breakdown:

  • Tasks, Kanban mgmt (20hrs)
  • Design/wireframes/research (20hrs)
  • Dev, Prototype (12hrs)
  • Summoning and Tally existing hours (2hrs)
  • Dev, Polished App (80hrs)

Check Ins (20hrs):

  • 10mins X 31days X 4 members (20hrs)