🏦

Marketing Governance Monthly

Attendance
Date
Feb 3, 2023
Agenda
  • Introduction
    • documented clarity around roles and circles
    • marketing circle, content,
    • what is objective of sub-circle
    • how establish purpose at every level
  • Murmur
    • place to record roles and circles
    • role template
      • compensation tied to role
      • expiry/ term limits
  • Growing marketing office
    • marketing circle
    • social circle
      • strategy
      • execution layer Twitter, LI, farcaster
    • content circle
      • editor
    • Circle = specific responsibility
    • Roles
      • mutual consent
        • raise hand, safe to try
        • enthusiastic consent
        • if its not a hell yeah, its a no
  • Refine purpose
  • Define structure
  • Establish new roles
  • Establish new subcircles
  • Discuss circle-level agreements that govern how we work together or with other circles
  • Moonrock Finance project
    • Product awareness
    • Ongoing marketing arm
  • How do we onboard new Marketing Associates? What is the process for vetting?
  • How do we fairly end role tenure? Term limits?
    • Related: how do we maintain consistency between terms?
  • Standard Operating Procedures
  • Budgeting and compensation
  • Requests from other Circles
 
Action Items
  • sidd define roles in Murmur
  • content circle charter
 
Meeting Transcript:
Action Items
  • Ryan to document clarity around roles and circles in Murmur due at the end of the meeting.
  • Ryan to discuss compensation and expiry for each role due soon.
  • Ryan to discuss strategy for growing the marketing office due soon.
  • Ryan to discuss roles within the content circle due soon.
  • Ryan to own the social media strategy
  • Ryan to come up with a perfect system for the Idm process due day away
  • Ryan to create a short list of standard questions for job interviews
  • Ryan to create a rubric for evaluating potential candidates for roles
  • Hiro to create language for roles that is tough enough to work with but also makes it clear what qualifications are needed to be considered for the role
  • Ryan to share a link for the role definition for the marketing circle lead
  • Adrian, Anna, Hiro, Siddhearta, RTJ, and 0xMarcus to write their role charter for their position using the template in murmur
  • 0xMarcus to rewrite the role definition for the Misdef circle and propose changes to the Biz Dev Circle Charter to the marketing group
  • Hero and Siddhearta to put together a charter for the content circle due next week
  • Marcus to revise and resurrect the business circle charter
  • Ryan and Hiro to discuss the inverse of onboarding for breaking up with someone if things are not happening
  • Everyone to get the charters and roles done when possible
Summary
  • Roles should be filled with qualified individuals who are able to meet the criteria and expectations of the role.
  • Roles should have an explicit compensation tied to the role and not the person, and should have an expiry date to ensure that roles do not become stale.
  • The group discussed strategies for growing the marketing office in a smart way that leverages external skill sets.
  • The group discussed the possibility of having a social media circle lead and individual roles for day-to-day execution.
  • The team should use an Integrative Decision Making (IDM) approach to staffing the marketing office, which requires unanimous consent from all team members.
  • When selecting a new team member, the team should use a combination of mutual consent and standard questions to evaluate potential candidates.
  • The team should be clear about the qualifications and expertise required for each role, and should avoid self-nomination in order to ensure that the right people are chosen for the job.
  • The team discussed the importance of self-defining roles and responsibilities in order to create a framework for self-management.
  • The team discussed the possibility of taking on more regular marketing agency type work in order to fund the office and keep valuable contributors around.
  • The team discussed the possibility of offering clients services to Web 3 projects and protocols, such as marketing and content creation.
  • The team discussed the need for a humane process for dealing with roles that are not being serviced, such as having a conversation with the person about ways to improve and giving them a chance to correct their actions.
Decisions
  • Document clarity around roles and circles in Murmur, including evaluation criteria and qualifications for each role.
  • Ryan proposed that every role should have an explicit compensation that is tied to the role and not the person.
  • Ryan proposed that roles should be reviewed every three months and that people should have the freedom to switch roles if they are not enjoying them.
  • Ryan suggested that decisions about staffing roles should be made as a group using a consent-based model.
  • Ryan proposed a group discussion to discuss the strategy for growing the marketing office in a way that leverages external skill sets and balances having external resources.
  • Ryan proposed a discussion about the strategy for growing the marketing office, leveraging external skill sets, and balancing internal and external resources.
  • Ryan proposed individual roles for the top level of the social media strategy, with one person owning the general strategy and others owning specific strategies for Twitter, LinkedIn, and Forecaster.
  • Ryan proposed that the team move in the direction of having written down roles and responsibilities to create a more anti-fragile organization and Hiro agreed that this would be necessary for commitment and to reduce frictions.
  • The team agreed to use a system of mutual consent when assigning roles in the marketing office, with the same process used for murmur agreements.
  • The team agreed to use a mutual consent system for staffing the marketing office.
  • Ryan and Hiro agreed to use a consent-based approach to decision making, where the bar is set at enthusiastic consent for a decision to move forward.
  • Ryan and 0xMarcus agreed to create a short list of standard questions to ask potential candidates and then deliberate together to come up with a job interview.
  • Ryan and Hiro agreed that there should be qualification rules in place.
  • The team agreed to choose by mutual consent and use a rubric to evaluate candidates based on strategic prioritization and team player skills.
  • Ryan agreed that people should be able to raise their hand for positions and actively nominate someone while also encouraging people to self-nominate.
  • Ryan asked the other participants to write their role charters using the template in Murmur.
  • Hiro and Ryan agreed that they will self-define the scope of their roles and Ryan will post a template for them to use.
  • Ryan asked Hiro and Siddhearta to put together a charter for the content circle.
  • Marcus was asked to revise and resurrect the charter for the business circle.
  • Ryan and Siddhearta discussed the possibility of taking on more regular marketing agency type work and onboarding more people to do so.
  • Ryan agreed that the moon rock project should be done slowly and that it should be treated as a normal project from a funding perspective.
  • Siddhearta suggested that the project should be used to keep valuable contributors around by providing consistent work.
  • Ryan proposed building systems to make the marketing projects repeatable and scalable.
  • The team agreed to use a process similar to the one used for onboarding when deciding to break up with someone if they are not fulfilling their role, which includes a conversation element and requires unanimous consent.
  • Ryan and Hiro agreed that there needs to be a more humane way of dealing with conflict and firing people.
  • Marcus agreed that if someone does not meet the expectations of a role, it is necessary to give feedback and that they should take it if that is the case.
  • Creating a system in which feedback is welcome and it became the norm to ask for feedback regularly.
  • The team agreed to move forward with the project and to create charters and roles for the project.
 
🏦

Marketing Governance Monthly

Attendance
Date
Feb 3, 2023
Agenda
  • Introduction
    • documented clarity around roles and circles
    • marketing circle, content,
    • what is objective of sub-circle
    • how establish purpose at every level
  • Murmur
    • place to record roles and circles
    • role template
      • compensation tied to role
      • expiry/ term limits
  • Growing marketing office
    • marketing circle
    • social circle
      • strategy
      • execution layer Twitter, LI, farcaster
    • content circle
      • editor
    • Circle = specific responsibility
    • Roles
      • mutual consent
        • raise hand, safe to try
        • enthusiastic consent
        • if its not a hell yeah, its a no
  • Refine purpose
  • Define structure
  • Establish new roles
  • Establish new subcircles
  • Discuss circle-level agreements that govern how we work together or with other circles
  • Moonrock Finance project
    • Product awareness
    • Ongoing marketing arm
  • How do we onboard new Marketing Associates? What is the process for vetting?
  • How do we fairly end role tenure? Term limits?
    • Related: how do we maintain consistency between terms?
  • Standard Operating Procedures
  • Budgeting and compensation
  • Requests from other Circles
 
Action Items
  • sidd define roles in Murmur
  • content circle charter
 
Meeting Transcript:
Action Items
  • Ryan to document clarity around roles and circles in Murmur due at the end of the meeting.
  • Ryan to discuss compensation and expiry for each role due soon.
  • Ryan to discuss strategy for growing the marketing office due soon.
  • Ryan to discuss roles within the content circle due soon.
  • Ryan to own the social media strategy
  • Ryan to come up with a perfect system for the Idm process due day away
  • Ryan to create a short list of standard questions for job interviews
  • Ryan to create a rubric for evaluating potential candidates for roles
  • Hiro to create language for roles that is tough enough to work with but also makes it clear what qualifications are needed to be considered for the role
  • Ryan to share a link for the role definition for the marketing circle lead
  • Adrian, Anna, Hiro, Siddhearta, RTJ, and 0xMarcus to write their role charter for their position using the template in murmur
  • 0xMarcus to rewrite the role definition for the Misdef circle and propose changes to the Biz Dev Circle Charter to the marketing group
  • Hero and Siddhearta to put together a charter for the content circle due next week
  • Marcus to revise and resurrect the business circle charter
  • Ryan and Hiro to discuss the inverse of onboarding for breaking up with someone if things are not happening
  • Everyone to get the charters and roles done when possible
Summary
  • Roles should be filled with qualified individuals who are able to meet the criteria and expectations of the role.
  • Roles should have an explicit compensation tied to the role and not the person, and should have an expiry date to ensure that roles do not become stale.
  • The group discussed strategies for growing the marketing office in a smart way that leverages external skill sets.
  • The group discussed the possibility of having a social media circle lead and individual roles for day-to-day execution.
  • The team should use an Integrative Decision Making (IDM) approach to staffing the marketing office, which requires unanimous consent from all team members.
  • When selecting a new team member, the team should use a combination of mutual consent and standard questions to evaluate potential candidates.
  • The team should be clear about the qualifications and expertise required for each role, and should avoid self-nomination in order to ensure that the right people are chosen for the job.
  • The team discussed the importance of self-defining roles and responsibilities in order to create a framework for self-management.
  • The team discussed the possibility of taking on more regular marketing agency type work in order to fund the office and keep valuable contributors around.
  • The team discussed the possibility of offering clients services to Web 3 projects and protocols, such as marketing and content creation.
  • The team discussed the need for a humane process for dealing with roles that are not being serviced, such as having a conversation with the person about ways to improve and giving them a chance to correct their actions.
Decisions
  • Document clarity around roles and circles in Murmur, including evaluation criteria and qualifications for each role.
  • Ryan proposed that every role should have an explicit compensation that is tied to the role and not the person.
  • Ryan proposed that roles should be reviewed every three months and that people should have the freedom to switch roles if they are not enjoying them.
  • Ryan suggested that decisions about staffing roles should be made as a group using a consent-based model.
  • Ryan proposed a group discussion to discuss the strategy for growing the marketing office in a way that leverages external skill sets and balances having external resources.
  • Ryan proposed a discussion about the strategy for growing the marketing office, leveraging external skill sets, and balancing internal and external resources.
  • Ryan proposed individual roles for the top level of the social media strategy, with one person owning the general strategy and others owning specific strategies for Twitter, LinkedIn, and Forecaster.
  • Ryan proposed that the team move in the direction of having written down roles and responsibilities to create a more anti-fragile organization and Hiro agreed that this would be necessary for commitment and to reduce frictions.
  • The team agreed to use a system of mutual consent when assigning roles in the marketing office, with the same process used for murmur agreements.
  • The team agreed to use a mutual consent system for staffing the marketing office.
  • Ryan and Hiro agreed to use a consent-based approach to decision making, where the bar is set at enthusiastic consent for a decision to move forward.
  • Ryan and 0xMarcus agreed to create a short list of standard questions to ask potential candidates and then deliberate together to come up with a job interview.
  • Ryan and Hiro agreed that there should be qualification rules in place.
  • The team agreed to choose by mutual consent and use a rubric to evaluate candidates based on strategic prioritization and team player skills.
  • Ryan agreed that people should be able to raise their hand for positions and actively nominate someone while also encouraging people to self-nominate.
  • Ryan asked the other participants to write their role charters using the template in Murmur.
  • Hiro and Ryan agreed that they will self-define the scope of their roles and Ryan will post a template for them to use.
  • Ryan asked Hiro and Siddhearta to put together a charter for the content circle.
  • Marcus was asked to revise and resurrect the charter for the business circle.
  • Ryan and Siddhearta discussed the possibility of taking on more regular marketing agency type work and onboarding more people to do so.
  • Ryan agreed that the moon rock project should be done slowly and that it should be treated as a normal project from a funding perspective.
  • Siddhearta suggested that the project should be used to keep valuable contributors around by providing consistent work.
  • Ryan proposed building systems to make the marketing projects repeatable and scalable.
  • The team agreed to use a process similar to the one used for onboarding when deciding to break up with someone if they are not fulfilling their role, which includes a conversation element and requires unanimous consent.
  • Ryan and Hiro agreed that there needs to be a more humane way of dealing with conflict and firing people.
  • Marcus agreed that if someone does not meet the expectations of a role, it is necessary to give feedback and that they should take it if that is the case.
  • Creating a system in which feedback is welcome and it became the norm to ask for feedback regularly.
  • The team agreed to move forward with the project and to create charters and roles for the project.