Create structured onboarding flows and career progression paths for DAO contributors to reduce churn and develop talent.
ROLE: You are a DAO people operations specialist who designs onboarding experiences and career development paths for decentralized organizations. You understand that contributor retention and development are critical challenges for DAOs — people join excited but leave confused if there is no clear path forward. CONTEXT: My DAO struggles with contributor retention. People join enthusiastically but many leave within 2-3 months because they do not know how to contribute, feel lost in the decentralized structure, or cannot see a clear growth path. I need to create a structured onboarding experience and career progression framework that retains and develops talent. TASK: 1. Onboarding Journey Design — Explain how to create a structured onboarding experience for new DAO contributors. Cover the first day experience (welcome message, access provisioning, orientation materials), the first week plan (introduction calls with key people, exploration of workstreams, first small task), the first month milestones (assigned buddy/mentor, completed onboarding quest, first contribution), the onboarding documentation (contributor handbook, communication norms, tool guides), welcoming different contributor types (developers, community managers, marketers), and measuring onboarding success (time to first contribution, 30-day retention rate). 2. Contribution Pathways — Detail the different ways people can contribute and advance in a DAO. Cover the explorer path (learning about the DAO, attending calls, asking questions — pre-contributor), the bounty hunter path (completing specific tasks for payment — flexible, project-based), the regular contributor path (ongoing work within a workstream — steady commitment), the core team path (leadership within a workstream — significant responsibility), the governance path (proposing and voting on DAO decisions — influence without operational work), and the cross-functional path (contributing to multiple workstreams — building broad skills). 3. Skill Development & Training — Walk through building contributor capabilities within the DAO. Cover identifying skill gaps across the organization, creating learning resources for DAO-specific skills (governance, on-chain tools, communication), pairing programs (matching experienced contributors with newcomers), funding external training and conference attendance, internal knowledge sharing sessions (weekly learn-together sessions), and building a culture of continuous learning and skill-sharing. 4. Recognition & Advancement System — Describe non-monetary recognition systems that motivate contributors. Cover contribution badges and credentials (on-chain POAPs, Otterspace badges for milestones), public recognition in community calls and newsletters, leaderboards for different contribution types (without creating toxic competition), advancement ceremonies when contributors move to new levels, contributor spotlights that highlight individual stories, and creating a culture where recognition is given peer-to-peer, not just top-down. 5. Retention Strategy & Exit Interviews — Explain how to retain top contributors and learn from those who leave. Cover regular check-ins with contributors (monthly 1:1s with workstream leads), early warning signals for disengagement (decreased activity, skipped calls, reduced communication), proactive intervention when contributors seem to be losing interest, exit interviews for departing contributors (what could we have done better?), alumni network for former contributors (they may return or refer others), and analyzing retention data to identify systemic issues. 6. Remote & Async Work Infrastructure — Address the operational infrastructure needed for distributed DAO contributors. Cover communication tools and norms (Discord for real-time, Forum for async decisions, Notion for documentation), meeting cadence that respects global time zones, async-first culture (important decisions are documented, not just discussed in calls), documentation standards (if it is not written down, it did not happen), tools for project management and coordination (Linear, Dework, GitHub Projects), and building social connection in a remote decentralized team.
Or press ⌘C to copy