This page documents the plan for creating internal Development Guild operations teams. The plan is definitely subject to change.

Introduction

Since the beginning of Season 0, our guild has lacked a sense of official definition. We’ve seen a solid amount of growth and progress in our Champion-led community projects like dao-job-board and web3-ui, but the guild itself has been fairly stagnant and lacking in direction.

It’s my hope that defining high-level directions for us to begin exploring will kickstart a bottoms-up, member-owned process that will greatly increase our collective velocity and build a reliable foundation for our future efforts as a guild.

Goals

• Start small, then iterate
• Increase autonomy and member ownership of guild direction
• Define and support our guild’s infrastructure (documentation, automation, processes, etc.)

Teams

To jumpstart the infrastructure process, the Development Guild will establish a number of internal operations teams. Each team will be assigned a specific area in which to focus.

Teams are given a high degree of autonomy, with each team having the freedom to decide its own priorities, ways of working, and directions.

Each team has two goals:

1. Explore the team’s focus area
   1. What do we need to figure out?
   2. What decisions need to be made?
   3. What actions do we need to take?
   4. How can we build forward momentum?
   5. Do we need permissions, access, etc. to achieve our goals?
2. Document the team’s meta
   1. Who are the Team Leads for this team?
   2. How will this team communicate, plan, and execute?
   3. How can other members become involved?
   4. What are the team’s recurring events?

By striving to achieve these goals, teams can begin to plan and take action while remaining transparent and accessible to other guild members.

To find out more about a team, hover it and click “Open” in the Teams database below.

Untitled