UXW-tworld2-Working Agreement
https://guide.techfleet.org/handbooks-and-glossaries/tech-fleet-workbooks/working-agreements-workbook
- Team Behavior:
- Working agreements define the expected behavior and attitudes of team members. They can include guidelines on respect, collaboration, and inclusivity.
- Communication:
- 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.
- Use Discord
- Use group chat for now
- Use DMs for 1:1
- What goes in our individual team channel?
- Meeting summaries
- Acknowledge personal preferences and comfort levels
- Meeting Protocols:
- 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.
- Decision-Making:
- Teams may define how they will make decisions, whether through consensus, voting, or another method. This ensures that everyone understands the decision-making process.
- Conflict Resolution:
- Working agreements can address how conflicts and disagreements will be handled within the team, such as through open dialogue or involving a mediator.
- Roles and Responsibilities:
- They can clarify each team member's role and responsibilities, ensuring that everyone knows what is expected of them.
-
Ambassadors (Outward Liaisons)
Wait for other teams to share their meeting times
Be informed of meeting agenda’s for other teams prior to meeting
- Keila?
- Design: Ashleigh?
- Research: Dana?
- Product Strategy: Aaron?
- PM: Lyn & Michelle
-
Inward Ambassadors
- Maybe PM or Research might attend our meeting; not design or product historically
- Task Management:
- Teams may establish guidelines for task management, including how work is assigned, tracked, and reported.
- Accountability:
- Working agreements can define how team members will hold each other accountable for their commitments and actions.
- Documentation:
- They may decide on how documentation will be created, stored, and maintained to ensure transparency and accessibility.
- Iteration and Improvement:
- 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:
- 4 out of 6 team members prefer that the process should move on without them if they can’t respond in time and/or go ahead with the majority and current information