--- title: MBD Onboarding tags: --- # MBD Onboarding ## 0. Objective Create an onboarding framework for Metaverse Builders' DAO ## 1. Understanding the DAO <details> <summary> Sample Questions</summary> > 1. Why does the DAO exist? (Mission / Vision / Problem Statement) > 2. How does the DAO solve said problem? (Product / Service) </details> <br> MBD is an early-stage service DAO that helps build Metaverse / digital experiences for Metaverse landowners. MBD is 1-2 months old and is completing its first project for a Metaverse Colosseum As an early-stage service DAO, MBD's priorities are: 1. Create a service model that works 2. Onboard a small & relevant group of contributors that can run & test the model ## 2. Understanding Contributor Personas <details> <summary> Sample Questions</summary> > 1. Who are the contributors? What are their personas? > 2. How do they find out about the DAO? > 3. How familiar are they with your problem space? > 4. How familiar are they with Web3? > 5. How familar are they with DAOs? > 6. Why do they join the Discord / DAO? > Pointers > 1. The less familiar they are with your problem space, the more they will need product/problem-specific education (i.e. actual onboarding is backloaded/done on a concierge basis) > 2. The less familiar they are with Web3 & DAOs, the more hand-holding is required for onboarding </details> <br> **Assumptions** | S/N | Pointer | Answer/Assumption | Implication | | --- | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | 1 | Persona | Contributors are Metaverse builders who do 3D Modelling, Music Production, Space Design, Art Direction, Project Management & Programming. (Highly specific skillsets) | Likely to be small group of highly relevant contributors | | 2 | Referral Source | They find out about the DAO through Zesty Market & Jseam's Twitter. (They have context on MBD) | Not much education re | | 3 | Familarity with Problem Space | They are familiar with the Metaverse space (Due to the above 2 points) | Metaverse education / onboarding has low priority (for now) | | 4 | Familarity with Web3 | They are familiar with Web3. | Web3 education has low priority | | 5 | Familarity with DAOs | They are familiar with the concept of DAOs but may not have been super active in DAOs | "DAO processes" need to be simple | | 6 | Purpose of joining community | They join the Discord to meet other builders, build digital spaces and earn revenue from their skillsets | Need to help them find teams & get projects | MBD is a Service DAO that requires individuals with specific skills and awareness to build Metaverse / digital experiences. Since most contributors come from Jseam's twitter, these contributors will have context, awareness and skills-fit with MBD. ## 3. How can Onboarding support the DAO's goals? <details> <summary> Sample Questions</summary> > 1. What is the objective of "onboarding"? > * A. Convert social followers into a Discord community member > * B. Educate and engage followers / community members > * C. Convert community members into casual contributors > * D. Convert community members into core contributors > 2. What does a "onboarded member" look like? (Non-mutually exclusive) > * A. Joined Discord > * B. Had a call with existing member > * C. Familarized with documentation, process, tasks > * D. Started work on first contribution </details> <br> **Assumptions** To help the DAO in its priorities, I assume that the objective of onboarding is less of mass education & community engagement (i.e. A & B) but more of **recruiting contributors and activating contributions**. With this view, an onboarded member would have: **A. Joined Discord (required)** B. Had a call with existing members (depending on time constraints) **C. Familarized with documentation, process, tasks (required)** **D. Started work on first contribution (required)** ## 4. Suggestion With the above assumptions, here is a proposed onboarding flow: ![](https://i.imgur.com/bmWj4BZ.png) Since MBD's priority is to identify a highly relevant set of contributors, the onboarding flow is more hands-on in assessing and onboarding the right contributors. ### 1. Join Discord for "Self-Onboarding" When the user joins the MBD Discord, they will only see the Welcome section . They are required to indicate whether they are a `Builder` or `Community/Enthusiast` * WHEN the user is a `Builder` THEN the Discord server will show Lounge, Builders Guild & Workspace AND a Discord bot will ping user's name in `#guild-chat` to introduce themselves * WHEN the user is a `Community/Enthusiast` THEN the Discord server will show Lounge When the Builder introduces themselves and there is a skills fit, a Community Manager can DM to arrange an onboarding call (with Calendly link) ### 2. Onboarding Call During the onboarding call, the Community Manager should assess the skills and experience of the contributor through portfolio, past experiences, etc. When the contributor has experience & skills that can directly contribute to MBD, the Community Manager can continue with the flow: - Give contributor skill-based Discord role - Explain the WHY & HOW of the DAO - Explain the policy, processes and tooling of the DAO - Grant necessary permissions for tools - Check if the contributor has bandwith to start contributing - YES: Get contributor set up with a task - NO: Keep in mind for other tasks When the contributor's experience & skills may not contribute to MBD, the Community Manager should: - Ask questions to better understand the user persona - Kep the contributor in mind where there are suitable tasks :::info When there is more clarity on the DAO's model & contributors (i.e. product-market fit), we can look towards more ways to scale onboarding (e.g. automating certain steps or running a cohort-based onboarding approach) ::: ## 5. TODOs If the above flow makes sense, here are a list of TODOs: 1. Discord revamp (Permissions & roles) 2. Discord Bot (Ping for self-introductions) 3. Basic documentation about DAO's processes & policy (e.g. payments, revenue, clients, timeline, etc.) 4. Basic documentation about DAO's tooling ## Notes (Call with Jseam, Valdiz & Ryan) - Bottlenecks on demand side (customers) - There are currently more builders than paying customers - How to find builds that people are willing to pay? - Build 1: Ad revenue (insufficient ad traffic & revenue) - Build 2: Contract is on the way with Dutch government. Need to sort out "contract" - Sales Channel: Sales partner was supposed to find customers, but it might be difficult due to bear market - Bottenecks on builders side - Currently there are: - 13 3D modelelrs - 1 project managers - 9 programmers - 3 architects - 3 branding - 2 WebXR - Admix's development studio - Next Steps - [ ] Announcement post on the 1st build, progress & learnings + CTA on future builds - [ ] Landing Page & Typeform for inbound clients - [ ] Apply for Grants (Decentraland & Gitcoin) - [ ] Sales process to reach out to companies with (A) land parcels & want to do "metaverse marketing" (B) virtual event organizers - [ ] Sales lead generation through affiliates / commissions - [ ]