Structural Update: guilds

RnDAO’s structure is divided in between Project Units and DAO Work Units. This proposal introduces a further component: Guilds.

The problem:

The current structure is one centred around cross-functional teams that deliver a specific value proposition. Although this structure is good for customer focus and agile innovation, it’s not particularly good at fostering technical excellence, professional development and career progression, and efficiency (functional redundancy across Project Units).

The solution:

This proposal suggests adding an additional category to our Structure (to be reflected in both Notion and Discord): Guilds.

Guilds are defined as learning communities, where each Guild is focused on a specific role/skill (e.g. developer guild, marketing guild, etc).

Guilds are exclusively advisory, meaning that under no circumstances they are allowed to impose decision on a Project Unit. 

Activities

Participants are invited to seek and provide support for each other.

Guilds can develop suggested best practices, standards, and/or templates.

Membership

Guilds are reserved for Project Unit contributors and are opt-in.

Organisation

Each Guild is facilitated by a Guild Lead, an honorary position given to a member of the Guild. Guild leads are elected (and removed) via a vote of the Guild members using our 🤔
Decision-making
 process.

Guild Leads are tasked with overseeing the organisation of the Guild, including the convening of meetings or gatherings as needed.

Incentivisation

Participating in Guilds is meant to be primarily a voluntary activity for the purpose of learning.

However, participants can praise one another for their mentorship and support using the Praise bot and be compensated in RnDAO points.

Formation & Dissolution

Project Unit Contributors can request the formation of a new Guild via a message in the #general-channel. If at least 4 contributors from at least 2 different Project Units commit to the Guild, the @Discord Architect will proceed to create it.

Guilds that are inactive (no meetings nor interactions in the channel) for a period of 8 weeks will be archived.

Structural Update: guilds

RnDAO’s structure is divided in between Project Units and DAO Work Units. This proposal introduces a further component: Guilds.

The problem:

The current structure is one centred around cross-functional teams that deliver a specific value proposition. Although this structure is good for customer focus and agile innovation, it’s not particularly good at fostering technical excellence, professional development and career progression, and efficiency (functional redundancy across Project Units).

The solution:

This proposal suggests adding an additional category to our Structure (to be reflected in both Notion and Discord): Guilds.

Guilds are defined as learning communities, where each Guild is focused on a specific role/skill (e.g. developer guild, marketing guild, etc).

Guilds are exclusively advisory, meaning that under no circumstances they are allowed to impose decision on a Project Unit. 

Activities

Participants are invited to seek and provide support for each other.

Guilds can develop suggested best practices, standards, and/or templates.

Membership

Guilds are reserved for Project Unit contributors and are opt-in.

Organisation

Each Guild is facilitated by a Guild Lead, an honorary position given to a member of the Guild. Guild leads are elected (and removed) via a vote of the Guild members using our 🤔
Decision-making
 process.

Guild Leads are tasked with overseeing the organisation of the Guild, including the convening of meetings or gatherings as needed.

Incentivisation

Participating in Guilds is meant to be primarily a voluntary activity for the purpose of learning.

However, participants can praise one another for their mentorship and support using the Praise bot and be compensated in RnDAO points.

Formation & Dissolution

Project Unit Contributors can request the formation of a new Guild via a message in the #general-channel. If at least 4 contributors from at least 2 different Project Units commit to the Guild, the @Discord Architect will proceed to create it.

Guilds that are inactive (no meetings nor interactions in the channel) for a period of 8 weeks will be archived.