Use this document to write down any general observations you have in project management processes around the DAO.

frog's notes:

• Kanban board is helpful, but often requires heavy administration
• Projects need a core coordinator
• Discord tags
• Surfacing needs → Go to guilds for talent
• Project governance (equitable ways for people to move up and down)
• Budgeting for future seasons is

links' notes:

• There is a monthly remuneration/accounting flow emerging in the DAO
  • I believe it started in the Writers Guild, and is also used in Academy and Translators Guild.
  • I believe that Ap0ll0517.eth is the mastermind behind this
  • Uses Notion/GnosisSafe/CSVAirDrop
    • all payments are recorded in a Notion DB, which is the source of truth for remuneration state
    • every month, a single transaction is made from a multisig paying out all owed remunerations
  • Is this a potential area in which we can reduce administrative burden for all projects in the DAO?
• The guild work intake processes have a lot of friction points
  • Client = person who has work to do, Creator = person who does the work
  • Clients looking for creators (i.e. design, writing, etc) have to go into a Discord channel and ask nicely, hoping someone will respond
  • Clients often don't know the information that creators need to get started or the appropriate pricing. Even when guidance is available on Notion, it's rare that clients will view this and shape their request
  • It's not always clear which guilds do what kind of work (i.e. Design guild does visual design, AV Guild does UX design)
  • Guild coordinators and talent scouts end up spending a lot of time coordinating btw client and creators, which is something they typically don't enjoy
  • Many people grab guild tags so they can interact with the guild, but they aren't actually members
    • This leads to a situation in where people seem like they are part of a guild, but aren't
    • Some workarounds included new Discord tags after people have gone through the intake process (i.e. EPA tag for Writers Guild editors)
• Many of the current processes are synchronous
  • i.e. you have to be at a weekly meeting to get work
  • There are some emergent asynchronous workflows driven by strong cultural voices (i.e. writers guild EPA process), but they are the exception
  • There seems to be some confusion between decentralized/asynchronous/democratic/etc. These aren't the same thing, and not all are values of the DAO.

bo's notes:

• Agenda-driven meetings are most efficient.
  • Doc should read: Agenda / Meeting Minutes / Action Items
  • Agenda must be coordinated in advance by the project champion
    • members of the working group should be helping to populate the agenda with items that should/must be discussed in the meeting
    • milestone reporting shoudl be a recurring item
  • Meeting Minutes are taken during the meeting
  • Action Items are identified (along with owners) during the meeting
    • next meetings should address last week's action items