UXW-tworld2-Working Agreement

https://guide.techfleet.org/handbooks-and-glossaries/tech-fleet-workbooks/working-agreements-workbook

  1. Team Behavior:
    1. Working agreements define the expected behavior and attitudes of team members. They can include guidelines on respect, collaboration, and inclusivity.
  2. Communication:
    1. These agreements often specify how team members should communicate with each other. For example, they might outline which communication tools to use (email, Slack, in-person meetings, etc.) and when to use them.
      1. Use Discord
        1. Use group chat for now
        2. Use DMs for 1:1
        3. What goes in our individual team channel?
          1. Meeting summaries
        4. Acknowledge personal preferences and comfort levels
  3. Meeting Protocols:
    1. Working agreements can establish rules for team meetings, such as starting and ending on time, setting agendas, and ensuring that everyone has an opportunity to speak.
  4. Decision-Making:
    1. Teams may define how they will make decisions, whether through consensus, voting, or another method. This ensures that everyone understands the decision-making process.
  5. Conflict Resolution:
    1. Working agreements can address how conflicts and disagreements will be handled within the team, such as through open dialogue or involving a mediator.
  6. Roles and Responsibilities:
    1. They can clarify each team member's role and responsibilities, ensuring that everyone knows what is expected of them.
      1. Ambassadors (Outward Liaisons)

        Wait for other teams to share their meeting times

        Be informed of meeting agenda’s for other teams prior to meeting

        1. Keila?
        2. Design: Ashleigh?
        3. Research: Dana?
        4. Product Strategy: Aaron?
        5. PM: Lyn & Michelle
      2. Inward Ambassadors

        1. Maybe PM or Research might attend our meeting; not design or product historically
  7. Task Management:
    1. Teams may establish guidelines for task management, including how work is assigned, tracked, and reported.
  8. Accountability:
    1. Working agreements can define how team members will hold each other accountable for their commitments and actions.
  9. Documentation:
    1. They may decide on how documentation will be created, stored, and maintained to ensure transparency and accessibility.
  10. Iteration and Improvement:
    1. Teams often agree to periodically review and adjust their working agreements to adapt to changing circumstances and improve their collaboration.

Phase 1

Working Agreement – UXW Taíno World Project

Based on our FigJam prompts & survey

Part A: Messages

Every UXW member agrees to check their Discord messages and the project threads (including UXW and their Ambassador team) at least once a day. The majority of members agree to check throughout the day (ranging from every 2 to 4 hours).

The majority of UXW members agree to respond to Discord UXW messages within 12 hours as a minimum. The majority of members agree to respond within 2 hours or throughout the day as possible. Please note that 1 team member has been transparent with the team about not guaranteeing a 12 hour response due to the timing of checking messages once a day.

For time sensitive messages, when someone isn’t responding promptly: