SUDAO-IP-15: Team Reporting [PASSED]

SUDAO-IP-15

Team Reporting

Rationale
There is a lack of clarity of exactly what each team’s accomplishments, goals and problems/issues are. There is also a large effort that is going into better communicating internally and externally about the DAOs overall goals and accomplishments. This report that each team is tasked to create will help with initiatives such as the newsletter and keeping UMA DAO informed of the ongoings of the SuperUMAns. This will also help us be better prepared when it comes time to approach UMA DAO with our next funding proposal. Overall this will be a great exercise for each team to write down their goals, reflect on any issues, and show off their accomplishments all while bolstering our communications efforts.

Content of the Proposal:
This document is to create a formal process for teams to report their accomplishments and goals on a bi-weekly basis.

  • Each team will have a dedicated channel underneath #getting-started named #reports
  • The report will be due on a bi-weekly timeline, specifically every 2nd and 4th Monday of each month.
  • Operations will create the channels for each team and also check for reports the day after a report is due to ensure there has been a report made. If a report has not been made operations will remind the team that the report is due.
  • Overall it will be up to each team to manage who is responsible for creating the report and making sure it’s posted on discord by each due date.
  • It’s recommended that each team assign two people to be responsible for these reports.
  • We encourage each team to set up their own google calendar to help keep track of the due dates and to help stay organized overall.
  • The #reports channel should also be strictly reports and any comments made that aren’t reports will be deleted.
  • Format would be simplistic: Long term goals, short term goals, accomplishments, problems/issues

Reasoning:

  • Every 2nd Monday is an easy way for each team to keep track of when another report is due.
  • Having the #reports live under each team’s dedicated category would make it very easy for anyone to keep up with the happenings of each team.
  • Operations will assist more heavily in the beginning but then play a lesser role by only reminding teams if a report is late. Ultimately each team will need to come up with how they will be putting up reports on the specified days.
  • It’s highly recommended that team leads aren’t the ones actually creating these reports. The biggest role a team lead should play is helping decide who would be responsible for the reports, checking reports, and continuously coming up with goals/ iterating on goals.
  • A team google calendar can help keep any important dates/deadlines in one place including when a report is due.
  • The format is kept pretty generic as this isn’t meant to be a complicated exercise. It would be good to see the types of problems each team is running into as well.

Changes to SuperUMAn DAO - Design Principles V2 - Google Docs:

Under Structure of the SuperUMAn DAO after Preamble :

Team Reporting
Each team will be self-reporting in a public channel every two weeks. This channel will be located beneath each teams #getting-started channels named #reports. The report will be due every second Monday each month. Operations will check for reports the day after a report is due to ensure there has been a report made. If a report has not been made operations will remind the team that the report is due. There will be four pieces of information each report must have: Long term goals, Short term goals, accomplishments, and any problems/issues (if applicable).

What on-chain actions might this proposal entail:
none at this time

17 Likes

i agree with this as we do not know much about others and if you are active only in one two teams, you may seem inactive to others and you may think others are inactive if you are not checking other teams. you may need someone to be some kind of supervisor to check all the teams and do some monthly or epoch activity report. this would be good. two weeks is not enough. one month should be at least, as it will be quite a bit of work.

1 Like

While I agree that there should be some degree of accountability and team reporting, the proposed cadence of a report every 2 weeks is too short. As such I’m currently against this proposal in its current wording.
For my part, given that Ambassador teams need a lot of time for outreach and doing the work to implementation of the integration, I suggest this is done once a month or even twice an epoch.

1 Like