Operations Guild Proposal

Revised Operations Guild Proposal

@lee0007 @daniel-ospina @fartunov

The proposal is a request to Executive Sub DAO to fund $52,000 for Season 1 (April 1st - July 31st) for forming and running Operations Guild. During Season 0 we recognized the tremendous work put in by Bounty Holders and saw the need to bring all the active contributors to define the processes and frameworks that will ensure smooth functioning of the AN DAO. The proposal defined below will help AN DAO:

  • avoid guilds and working groups functioning in silos
  • build frameworks using agile methodology that can be applied by other guilds
  • maintain operational efficiency across the DAO

The Ops guild envision itself placed strategically within the AN DAO and help in coordination, drive project management discipline, avoid blockers so that all contributors, new or old, have a seamless experience in the DAO.

1. Rationale

During Season 0 we attracted a number of talented individuals to join Aragon and work on bounties around Core Operations. Community members joined and started to own tasks such as finance and payroll, tooling and documentation (notion) community coordination, communications and operational experiments. Building on this momentum, we seek to

  • define a set of core operations in the DAO
  • identify individual responsibility
  • create accountability for our ongoing work
  • drive operational efficiency/ remove inefficiencies
  • foster an environment for collaboration

We want to take the momentum around Season 0 and propose to create and fund an Ops Guild. The proposal aims to secure funding for 3 months to carry on smooth functioning of DAO and continuously support other guilds and working groups.

Today we fund individual projects or working groups, which pushes significant operational overhead to these teams. Moving into season 1 we seek to create and empower DAO Ops Guild to drive operational efficiency for our community working groups and enable teams to focus on deliverables

A DAO’s ability to deliver results is directly proportionate to the efficiency with which it functions. The essential elements of an efficient DAO are effective governance, transparent treasury management, agile operations, and the quality of its contributors. Our focus is to remove inefficiencies by applying agile frameworks to support and foster collaboration in terms of

  • cross-functional teamwork within guilds and working groups
  • contributor accountability
  • constant iteration of complex team structures

The guild will work in sprints (2 weeks each) which will increase flexibility and adaptability to change. This will allow Ops guild to detect the issues faster and address them during weekly calls with the community.

DAO governance should be fundamentally democratic, accompanied by a standard governance process that can represent participation and voting power. Governance planning often requires a dedicated group of contributors that can function independently, transparently and equitably. A dedicated governance bounty holder will be required to perform tasks keeping those ethos intact.

2. Deliverables

Metrics

Objective Deliverable Due Baseline Target
ACCOUNTABILITY Ensure 100% of Bounties have metrics at outset and that performance is tracked 31-Jul 10% 100%
RESPONSIBILITY 100% Bounty adoption by identifying key responsible contributors 31 July 90% 100%

Process

  • OPERATIONS: Create a guide on how to use DeWork for project management (task tracking, similar to JIRA) and bounty management by June end
  • OPERATIONS: Establish payment infrastructure with DeWork for bounties by 15 June.
  • COLLABORATION: AN DAO Wiki Notion and Ops Guild Notion Page revamped by31 July
  • COLLABORATION: Weekly/Bi- Monthly/Monthly meeting (depending on the group) cadence scheduled in the shared calendar to aid alignment and collaboration
  • EFFICIENCY: End of Season Documented Operations Guild Feedback
  • EFFICIENCY: Monthly implementation and advancing documentation of DAO tooling process to aid operations and accountability

Routine (Hrs)

  • Weekly Tactical meeting (1) with Guild Stewards
  • Weekly meetings with Metrics, Finance, and Growth squads (3)
  • Monthly Operations documentation (8+8)
  • Weekly tooling feedback DeWork (8)
  • Weekly Contributor calls for Notion Maintenance(4)
  • Weekly contributor calls for Discord upkeep (4)
  • Weekly Notion Documentation, feedback captured and suggestion (2)
  • Monthly tooling call (2)
  • Monthly feedback (4)
  • Monthly community call (1)
  • Monthly reporting (2)

Team

â—Ź Anukriti#6039 - Preseason & S1 Ops Contributor and Scrum Master (30-35 hours pwk) working to drive operational efficiency, contributor responsibility and accountability and document operational process

â—Ź Lion917#3637 - Preseason Knowledge Catalyst now Ops Coordination and Knowledge Catalyst S1 ( 40-45 hours p wk) working to support effective colloboration and knowledge sharing to aid operational efficiency

â—Ź Governance Bounty Holder: The contributor must be an experienced personnel in DAO space who can advise the community on best practices about Governance.

3. Strategic Alignment

Some additional key points of alignment for the coming months:

  • Work with AA and ESD members to identify and remove any operational overheads.
  • Work with the dTech team and propose agile frameworks for product enhancements and development.
  • Work with People Guild and Onboarding contributors to understand the needs of the community and enable an operations structure which is friendlier to new contributors in order to create a frictionless onboarding experience.
  • Work with DAOAcademy contributors to draft the learnings of DAO tools.
  • Work closely with Growth, Finance & Treasury, Metrics working groups and provide support whenever needed. These squads are being established for the first time within the DAO. Hence, the Operations Guild will also temporarily assist these groups to set goals, track progress and enable functioning.

4. Limitations & Risks

  • We expect that the Ops guild will need significant time investment from members of the Aragon core team. These team members will continue to work in stewardship roles, with the ambition being that teams are fully autonomous by completion of Season 1.
  • Since AN DAO is in its early stages, it is important to understand that many unforeseen tasks and challenges occur on a regular basis and a group of dedicated contributors are required who have the bandwidth for the same. Operations guild will function with agility and efficiency in order to facilitate the efforts to overcome challenges and roadblocks.
  • Getting accustomed to a new tool, DeWork for tracking tasks. It requires a certain amount of time commitment from guild stewards to update the tasks on the DeWork board.

â—Ź As per Season 0, another limitation might be some inability to fully predict unseen factors that will change the trajectory of the team.

5. Funding Information

The guild proposes to fund the following:

â—Ź Core Contributor(s): Someone who will take on a first POC within the squad. The person in the contributor role has been a bounty holder and has demonstrated high performance.

â—Ź Additional Bounties: A pre-defined allocation towards currently undefined bounties that will allow ops to be nimble and attract talent or fund action that supports effective operations of the AN DAO.

The ops guild requests funding of $13k per month with following distribution -

Adding the per month distribution, the total disbursement requested for Season 1 is $52,000.

Stakeholder Compensation/Month Compensation for Season 1
Ops Guild AA Champion Alex NA NA
Ops Coordination and Scrum Master Anukriti#6039 $4,000.00 $16,000.00
Ops Coordination and Knowledge Catalyst Lion917#3637 $5,000.00 $20,000.00
Governance Bounty TBD $2,000.00 $8,000.00
Additional Bounties TBD $2,000.00 $8,000.00
Funding Requested $52,000.00

Imp Links:

The findings of DeWork during Season 0 can be found here:

Bounty Board for Season 0

Note: The Ops guild started the DAO Tactical meeting in April with Guild stewards along with Notion change feedback process and Discord survey for regular upkeep. Ops guild also started doing ground work on DeWork bounty management with DeWork core contributors during April.

8 Likes

Thanks for this proposal. I think this focus on increasing synergy and coordination across teams and already deployed resources will increase value creation, efficiency and reduce miscommunication. I also look forward to seeing the proposals from other “squads” that will support core operations.

One call out, the deployment of Dework can be a very meaningful contribution because teams today manage projects management and tracking/reporting separately. With Dework, teams manage and the tool tracks (and even enables payments). This will transparency of all activity within the DAO and allow groups such as the ESD to review detail of any project, group or guild in real time.

Lastly, I think the proposers demonstrate the values and culture we want to see in AN DAO, so having them highly visible and engaged with all teams will bring intangible value not directly described in the proposal.

2 Likes

DAO Ops is mission-critical. This is a talented team and the value operational efficiency can not be overestimated. But where are the Specific MEASURABLE Achievable Relevant TIMEBOUND deliverables as requested by the ESD for approval of funding

It was also made clear in the preceeding proposal that objectives (provided) and metrics (missing) would be a requirement for further funding

Beyond operation rhythms and regular meeting cadence the only SMART deliverable here is for a yet to begin Governance role offering over $100 an hour for 15-20 hours of governance work with the deliverable to assess, analyse and report on governance.

I note in pre-season Metrics Review that they report the following KPI

KPIs & Success factors

  • Did we identify the data and information needs in the DAO effectively?**
  • YES. The metrics team has done good analysis on what is needed

I can not locate that analysis and there is nothing here to enable the ESD to assess deliverables beyond funding time spent in meetings and an overpriced or underscoped bounty. Due to Easter, it is now highly unlikely that this proposal will be decided upon at the next ESD meeting scheduled for Monday 18 April UTC 1900 and will most likely roll over to the 3 May.

If someone can DM me an editable document (not notion) I will have a crack at providing some possible SMART deliverables based on the list of activities provided.

2 Likes

Hi @lee0007, I have DMed you an editable ops proposal link on Discord.

Beyond operation rhythms and regular meeting cadence the only SMART deliverable here is for a yet to begin Governance role offering over $100 an hour for 15-20 hours of governance work with the deliverable to assess, analyse and report on governance.

Just a small correction, maybe we did not convey it properly. The hours mentioned in the proposal are on weekly bases. So, 15-20 hours per week and the payment is monthly (60-80 hours). Hence, the governance bounty is paid at 25-35 USD per hour.

I have to echo Renee’s sentiment here about “Specific MEASURABLE Achievable Relevant TIMEBOUND deliverables” as a requirement and absolutely essential.

1 Like

Thanks for the comments all. Just to clarify @Anthony.Leuts & @lee0007 on the deliverable listed are you looking for dates when they will be delivered by or KPIs to track each one?

Any suggestions on the KPIs you would like to see in these would be really helpful

1 Like

Hi @Anthony.Leuts, thanks for your comment. Could you suggest how we could make our deliverables better? For example, a Notion Revamp will be based on the feedback of the community. It’s hard to define a measurable metric with respect to the success of the same. We will follow the abovementioned steps and make sure to document everything with monthly forum updates.

I did the same for Discord Revamp last month. We also designed a scalable skeleton for guild structure. Here is the documentation and work for Discord:

  1. Finalised the feedback table regarding current discord (15-20 calls): Discord Feedback - Google Docs

  2. Final suggestion sheet and Discord Analysis: Aragon Discord Reorganisation - Google Sheets

  3. PPT for discord reorganisation: Discord Reorganisation.pptx - Google Slides

We intend to follow a similar pattern for all our work and any significant change will go through a round of community feedback. We will be designing quite a few ops procedures to make the DAO transparent and scalable. The success of the same is associated with the AN DAO’s total increase in proposals, participation and deliverables.

For example, as the bounty board manager, I worked with @b3n for 4 weeks prior to design launching the bounty board. I believe the success of my task should not just be measured with the metrics of those bounties, but also the impact it had during season 0. Having a healthy bounty board with paid work drove traffic to AN DAO and it helped us identify leaders. Based on Season 0, there are multiple Guilds and Squads that are forming now and many contributors are part of those groups because they were allocated paid bounties. Hence, with distribution and operation type roles, it’s hard to identify specific success metrics unless the organisation is at an advanced stage. The processes/scalable operational solutions that Anukriti and I will help design will act as the basic infrastructure for the DAO to operate. For example, the success metric of putting in place a project management tool and educating the DAO about the same is that the future projects are managed transparently in a frictionless manner. This will create a healthy cycle of projects. I am unsure about what other reportable metrics can be attributed to this task except for the fact that such a tool was implemented and used. All the deliverables that have been mentioned will be delivered within Season 1.

I would love to learn more about different success metrics that can be associated with our specific deliverables/milestones.

Hey Lion, thanks for the questions!

Maybe this example will help lead a bit, you mentioned discord, notion, and bounty board.

When I see the bounty board drove traffic to ANDAO to identify leaders. I immediately think: how much increased traffic was brought to the board, how many more bounties were filled then previously (if it wasn’t first iteration and if it was first what data did we collect), how many leaders did we identify and how many more ANDAO members are more engaged because of their intro through the bounty board?

Totally agree that comparing to before can be difficult but then I think it’s really important to describe in detail what will be measured and in what way can one create a data profile to build off of in the future! Otherwise we get into the vicious loop of: “couldn’t get data on improvement because there wasn’t data”

Same with discord and notion improvements. How can we prove that the awesome work you are doing is impactful? There is data to collect through surveys, interviews, and of course no1 is saying that qualitative data isn’t important!

So the goal as described above is: “remove inefficiencies in the DAO by adopting an agile framework focusing on cross-functional teamwork within guilds and wgs, accountability among contributors, and constant iteration to support complex team structures.” I’m not seeing enough evidence in the deliverables to quantify success or not?

Rhythms, implementing Dework, reviewing discord structure, building operations processes, revamping AN Dao Notion, maintenance of notion, facilitating a governance bounty are all attempting to reach a goal to remove efficiencies in the ANDAO as mentioned. How will we know we’ve removed those efficiencies that exist and are on an efficient path?

How can we prove we reached what goal?

I hope this makes a lot more sense! Btw, this is just constructive feedback! Looking forward to seeing you both working on this! Also, we on the core team are also really focusing on implementing agile operations. LOVE seeing this used in the DAO!!!

2 Likes

Hello @lee0007 and @Anthony.Leuts, thank you for the suggestions and the concerns raised regarding the proposal.

I can help and answer few questions and have follow-up questions from ESD and Core team –

The key objectives under the proposal can be identified under 4 buckets –

  • Meetings
  • DeWork Adoption
  • Discord Upkeep and Notion Revamp
  • Governance Bounty

In the SMART format, we have covered - Specific, Achievable, and Relevant. The ones missing are Measurable and Timebound. I will try and fill in the blanks as addition to the proposal -

Meetings - The success of every meeting can be measured whether we identified issues and resolved them or have a path forward to resolve them. During Season 0, we captured those during Weekly Contributor Calls and towards the end of Season 0, we started having DAO tactical meetings with the stewards of each guilds. In Season 1, we plan to continue DAO tactical meetings within Ops Guild along with Treasury, Growth, Metrics and with each guild steward.

o Measurable KPI for this objective

  • How many meetings did we have/month that were a success and that were a learning?
  • How many issues/blockers were identified in the meetings along with a path forward?

o Timebound – This has to be a monthly KPI and will be reported in the monthly forum update.

DeWork Adoption – MDlawyer, Luiz, Lion, and I did a POC of DeWork during Season 0 with dTech guild for using the tool as a kanban board for AN DAO. We had several calls with DeWork team as well to clarify follow up questions. At the end of the POC, Ops Guild and dTech guild decided to move ahead with DeWork as a PM tool for Season 1 for ANDAO. In addition, support guild to start using the tool for bounty management as well. This wasn’t done in Season 0, so POC would need to be carried out along with Finance and Treasury team on how to pay the bounty holders.

o Measurable KPI for this objective –

  • How many guilds/squads/working groups adopted DeWork as their PM tool?
  • How many of those were most active and engaged? This will be tracked on completion of projects within DeWork.
  • How many bounties were posted on DeWork?
  • How many bounties were picked up by new contributors from DeWork?
  • How many bounty holders were paid from DeWork?

o Timebound – Aforementioned KPIs will also be monthly KPIs and will be reported in the monthly forum update.

Note: As highlighted in the “risk and limitation” portion of the proposal, achieving this objective highly depends on core contributors and the community.

Discord Upkeep and Notion Revamp – During Season 0, Lion did a fantastic job of organizing discord. Not an easy and small feat, as several interviews were conducted with the contributors to take in feedback and suggestions. As a Knowledge Catalyst, it is a difficult job because everybody had great suggestions, however not everyone’s suggestions could have been implemented. This is a time consuming and exhausting job which took 6 weeks to complete. A similar exercise will be conducted for Notion pages (main ANDAO wiki page, Ops guild page, Contributors Workspace, Trainings and Resources along with other pages wherever any guild that needs help).

o Measurable KPI for this objective –

  • While not quantitative, a big qualitative KPI is the notion page(s) itself for everyone to see.
  • A quantitative KPI, the number of visits on our notion pages. We could use Google Analytics API or Metrics team could help us writing a Python script to track the number of notion visits. The number of visits could yield following metrics -
  1. How many times a page has been viewed? Will only capture important pages while measuring metrics.
  2. How many new users on the landing page?
  3. How long did each session last?
  4. Geolocation tracking i.e. where the users are based out of geographically?

o Timebound – Aforementioned KPIs will also be monthly KPIs and will be reported in the monthly forum update.

Note: A risk worth highlighting, the aforementioned KPIs will be tracked based on Metrics team help and their knowledge of API integration.

- Governance Bounty – This bounty is a roll over from Season 0 as no one claimed it during the season. We don’t have a Governance contributor as of today and governance is at heart of any DAO. Ops guild believe that it is imperative we have a core contributor for Governance and it should start with a bounty to test the skills and experiences of the bounty holder.
While I agree the bounty is under scoped, that is on purpose, I don’t believe in laying down a path already for a new contributor who will come in and bring new ideas. The whole purpose of a DAO and Web3 is bring in about change and fresh ideas. If Ben hadn’t given me the opportunity to bring in my thoughts and ideas, I wouldn’t have suggested DeWork and we would still be using Notion as Kanban board. I’d request ESD and the DAO to leave some room for the new contributor to come in and advise us on Governance with their own experience without us telling the contributor in advance what to do. We can define a high level objective for the bounty and open to suggestions from everyone on what the bounty should achieve by Season 1 end.
As for overpriced, I can only say that the bounty and the comp was approved by ESD in Season 0 and that is exactly what I am suggesting.

I hope the above can fill in the blanks in SMART that ESD is looking for.

@lion917 @anukriti10 can I get links please to your respective pre-season bounty, please.
You’ve both done a brilliant job to help the AN DAO build traction pre-seasons and I’m doubtful that this proposal - focused on tooling - makes best use of your time or talent in S1 or requires more than one full time role in total

Are dework, notion and discord really our leading operational needs?

@lion917 you mentioned process development which imo is an operational need. In regards to this process

Although certainly comprehensive, how did you determine that this was an effective, efficient process and should be repeated and scaled? Or to ask this another way was talking to 15-20 (~10hrs?) people more effective than a simple asynch survey that also enabled you to measure results. For example, if we ask

On a scale if 0-10 - 10 being outstanding - how would you rate the current Discord experience?
Please a share your thoughts on ways we could improve your Discord experience

Thank for the clarification in regards to this bounty

Being that the Governance was not role picked-up/tested pre-season as a bounty, can you describe the gaps that you see that suggest we need a 240 -320 hours 8k bounty S1 to develop a report on governance?

Can someone provide a list of the planned bountied for S1 (at this early stage)

1 Like

ESD General Meeting Monday 18 April UTC 1900: We are keen to see this team continue to deliver impact for AN DAO in terms of operational efficiency and effectiveness. This proposal currently lacks the impact and SMART deliverables that we require to agree to funding. At this point the proposal requires significant work to the extent that a final funding decision will rollover to 2 May 2021.

cc @daniel-ospina @fartunov

1 Like

Thank you for the updated proposal. Clarification of deliverables goes a long way to helping us “assess deliverables” as per our Charter mandate Sub DAO Agreements S 2 (a) I 2 (c). This proposal will be a priority for final decision at the next ESD General Meeting 2 May.

2 Likes

Hey, @anukriti10 appreciate the effort in revising the proposal!

Here are a few questions comments:

I understand that the Ops guild will work on cross-guild cohesion and set up best practices on how guilds can enable that. To avoid any doubt, the responsibility of transparency and accountability for each guild should sit with the guild itself! Another set-up will be entrenching teams instead of enabling fluidity.

I do not understand what this means in practical terms.

I, unfortunately, have to disagree with @lee0007. The “metrics, process, and routine” thing makes it more confusing than helpful, to be honest.

The deliverables as outlined (for some reason) under Process under Operations and Collaboration make sense, and I am willing to support the funding request.

“Monthly implementation and advancing documentation of DAO tooling process to aid operations and accountability” not sure what this should mean

Hey @fartunov, thanks a lot for your comments and your support with respect to the funding request. I would like to respond to your points for clarity.

I understand that the Ops guild will work on cross-guild cohesion and set up best practices on how guilds can enable that. To avoid any doubt, the responsibility of transparency and accountability for each guild should sit with the guild itself! Another set-up will be entrenching teams instead of enabling fluidity.

  1. Agreed, the responsibility of transparency and accountability for each guild should sit with the guild itself. However, we will be focusing on building the infrastructure that enables it so that all guilds have a basic structure that is similar to each other for cross guild coordination. For example, we would like to build a table which reflects the funding of each bounty and the outcome within each guild. The guild members will be filling that table. The ops team will only provide everyone with the template so that transparency is maintained across guilds in a uniform manner.

I do not understand what this means in practical terms.

  1. I believe we were just describing our view on governance when we drafted the proposal. In practical terms, an analysis is required with respect to the current governance process to make it more transparent and a governance secretary can help enable that.

“Monthly implementation and advancing documentation of DAO tooling process to aid operations and accountability” not sure what this should mean

  1. Lastly, we just volunteered to provide a monthly update on the forum/notion about operations and DAO tooling. This will make us more accountable with respect to our work. `

I hope this helps.

1 Like

Awesome! Thank you!

As part of this proposal, in addition to improved Notion, can we please get a commitment on:

  • Improved discord structure (we have improved substantially), but currently, the Discord tailors mostly to someone looking to join the DAO as a contributor, while we have a (hopefully) increasing flow of other stakeholders
  • Better forum structure

still vague to be honest. Is this about more clarity in Notion about how the DAO operates and who makes what decisions, or what is it?

Of course. We have already started working on that, to improve the discord structure, and @lion917 has sent out a survey requesting contributors on what they’ll like to see in the discord. While this is the second phase of discord upkeep (first was in Season 0), Ops Guild will be responsible for continually improving Discord, if need be.

This certainly we can take on a task for Season 1 and work with the Governance contributor.

We have included Governance Bounty in our proposal as we don’t have a dedicated Governance contributor within the DAO. The description and the further clarification was to set a tone for as to why we are requesting funding for Governance Bounty.

1 Like

I have a question about “build a table” - given we are using DeWork - does DeWork integrate with Notion so we can filter this bounty information from a single master database? You’re not building a new table right or duplicating bounty info?

I would expect tooling documentation to be in Notion (at this stage) is there a reason it needs to be on the forum? I understood this to mean that while using these tools you are also building the documentation so that other people can learn from your learning?

Finally, I return to my only real sticking point on this proposal. I still have an issue as to how a 10-15 hour bounty pre-season suddenly became 40-45 hours and it looks to me like a lot of the extra time proposed is for time dedicated to talking about doing, as opposed to delivering. I’m a communications major, so I understand the importance of ongoing communication however I believe I could achieve similar results in significantly more efficient ways.

Given a stated objective of this guild is to

@lion917 how do you justify 8 hours a week “contributor calls” as efficient?
@anukriti10 how do you justify 8 hours a week “tooling feedback DeWork” as efficient?

I believe you could each gather the same type and quality of information each month in 8 hours (one day) per month. I suggest rather than so much time talking you look to drive efficiency through group communications or asynch information capture. Some proven ideas include

  • Group: Miro or Jam board 30-minute sessions during the tooling call to gather qualitative feedback
  • Asynch: Survey to gather quantitative and qualitative feedback
  • Asynch: Form for contributors to submit suggestion

In total it appears you propose 72 hours per month 288 hours in season one to talk about tooling time that could be better used imo implementing tooling and expanding the remit of your roles and team.

At this point, I agree to fund 52k for DAOOps but not for the amounts currently allocated. I will agree to both core members at the equivalent of 30-35 hours 4k per month. I trust that in limiting your budget @lion917 you will work together with @anukriti10 to find more efficient means to gather and apply insight and hold each other accountable for this.

This would increase the 8k for funding bounties to 12k S1, to cover additional time and tasks, not yet defined in this proposal and I hope that will help this team resource the Ops Guild to become the leading example of operational efficiency.

@daniel-ospina @fartunov

2 Likes

Yea…as in if favor of the proposal

2 Likes

ESD General Meeting 2 May UTC 1900: majority support for maximum 52k funding as per the requirements that

  • Up to 32k equal funding for two core members at 30-35 hours 4k per month.
  • Up to 20k S1 Bounties to cover additional time and tasks, not yet defined in this proposal
  • Release of monthly funding dependent on reporting against proposed deliverables (includes April)

cc @fartunov @daniel-ospina

1 Like

@daniel-ospina @lee0007 @fartunov

EOM May Report:

  • Accountability: Ensure 100% of Bounties have metrics at outset and that performance is tracked (In progress)
    • Three Ops bounties were opened out of which one bounty’s KPIs have been defined. Rest 2 are In progress as there is a dependency on guild stewards and meetings are in progress.
  • Responsibility:100% Bounty adoption by identifying key responsible contributors (Complete)
    • All 17 bounties posted in the month of May have been filled and bounty holders are working on completing the defined KPIs.
    • Create project management tasks of Ops guild in DeWork (Complete)
  • OPERATIONS: Create a guide on how to use DeWork for project management (not started) and bounty management (Complete) by June end
  • OPERATIONS: Establish payment infrastructure with DeWork for bounties by 15 June (In progress with @Ricktik6)
  • COLLABORATION: AN DAO Wiki Notion and Ops Guild Notion Page revamped by31 July (In progress)
  • COLLABORATION: Weekly/Bi- Monthly/Monthly meeting (depending on the group) cadence scheduled in the shared calendar to aid alignment and collaboration (Complete)
    • Complete Monthly AN DAO All Hands in collab with Community Experience Team
  • EFFICIENCY: End of Season Documented Operations Guild Feedback (Not Started)
  • EFFICIENCY: Season 0 Bounty Holder Feedback (Complete)
  • EFFICIENCY: Monthly implementation and advancing documentation of DAO tooling process to aid operations and accountability (In Progress)
    • DAO Tooler Bounty was filled and the meetings with stakeholders has started @Shanzz @ifun

Funding Request:

  • USCD 90% Total: $8,145.00 (Including contributor and bounty rewards)
  • ANT 10% Total: $1305.00 (Including contributor, bounty rewards, and Coordinape)
  • Amount Contributor rewards: $8000.00 (Lion and Anukriti $4000 each)
  • Amount Flexible Rewards: $400.00 ($50X8 for Coordinape)
  • Amount Bounty Rewards: 1050.00 (3 Bounty holders getting paid $150 and 3 bounty holders getting paid $200)

EOM Report

2 Likes