# data[].attributes.body
I like the idea of having working agreements visible in the CLT room, on all CLT or other agendas, and attached to the calendar invite or email. It gives a team the opportunity to frequently see those working agreements and refer back when necessary. For the first few meetings, this could be a 5 minute apart of the agenda to revisit and reflect on the working agreements. It may not be necessary to have this apart of your agenda for every meeting, however, possibly once a month.

# data[].attributes.body
I also like how this particular protocol offers an opportunity for individual reflection prior to the sharing with the group

# data[].attributes.headline
Reflecting on Adherence to Working Agreements - Molly 

# data[].attributes.subject
Reflecting on Adherence to Working Agreements - Molly 

# data[].attributes.body
Something I think gets overlooked often is this reflection piece. I notice that we tend to lose sight of some working agreements at times. For example, something simple like staying on the topic at hand until the team is ready to move on, gets overlooked when the team gets distracted or off topic. I think reflecting would help the team to recognize what is going well and what needs to be improved upon moving forward.

# data[].attributes.body
I like that each idea in this process has you label a working behavior from each category. This will enable clear expectations for everyone on your team and they will feel apart of the decision making.

# data[].attributes.body
It is so important to be flexible. We must always be willing to adjust tasks at hand. We must always be evaluating and adjusting. Things change, needs change, we have all heard the old saying "It happens". If we do not evaluate and revisit how do we know if we are moving forward.

# data[].attributes.body
Working agreements is a vital part of creating an environment where everyone's voice and opinion is heard. I think we start off strong with the working agreements, but then we forget about them or just go over them casually at the beginning of meetings. It was interesting to read over the reflect and refine portion because often times this step is forgotten. Teams continuously grow and change and I think it is safe to assume that working agreements would change along with the team. It may be a good idea to do the Reflect and Refine after each quarter know that the agreements could change or stay the same.

# data[].attributes.body
I like the idea of having working agreements visible in the CLT room, on all CLT or other agendas, and attached to the calendar invite or email. It gives a team the opportunity to frequently see those working agreements and refer back when necessary. For the first few meetings, this could be a 5 minute apart of the agenda to revisit and reflect on the working agreements. It may not be necessary to have this apart of your agenda for every meeting, however, possibly once a month.

# data[].attributes.body
Creating working agreements together as a team is an important part of making sure all participants are on the same page and are in agreements with the guidelines of the meeting.  Having the agreements visible and reviewing the agreements before meetings set the stage for everyone to have a productive meeting.  Having a working agreements as a living document allow members to check in with themselves and it provide a structure that includes individual and group reflection and refinement.

# data[].attributes.body
This is waaay out of my comfort zone, so I find it intriguing. I'd worry that it would quickly devolve into a complaining session, but with some tight guidelines and a strict timekeeper, I can see how it could be a "back door" approach to coming up w/a working agreement.

# data[].attributes.body
Having all team members approve and rank the support of working agreements after drafting.

# data[].attributes.headline
Promote a positive and productive environment

# data[].attributes.subject
Promote a positive and productive environment

# data[].attributes.body
Working agreements are necessary in order to create a positive and productive working environment. They contribute to a shared sense of responsibility. Working agreements must be visible, simple, and direct. One thing to consider is to making an agreement to circle back to the working agreements quarterly. This will make sure your team is constantly evolving to ultimately creating a better and supportive environment.

# data[].attributes.body
It was really interesting to read through different ways that we can continue to reflect and refine our working agreements. We often set them at the beginning of the year, but sometimes we find that things need to change. When there are many people and tasks involved, it's always good to know you can come back to the agreements you've set. I really like the process of adopt, adapt, and abandon. I never thought that it could apply to working agreements, but this is something that would be really helpful to do!

# data[].attributes.headline
Keeping Working Agreements Alive - Jazzmin

# data[].attributes.subject
Keeping Working Agreements Alive - Jazzmin

# data[].attributes.body
If working agreements are not visited, they are forgotten and unused. At the beginning of each CLT or meeting, we make sure to revisit each working agreement and choose one to focus on for the time we are together. We then revisit them at the end. It's an easy way to hold everyone accountable, without being confrontational since we all agreed on the working agreements. It's also a neutral way to begin and end each meeting - sets the same expectation for everyone.

We also may realize that some working agreements are just not needed anymore like they were in the beginning of the year. We may gain or lose team members and working agreements may need to be revisited and adjusted. It should be a common thing to revisit and adjust as needed.

# data[].attributes.body
On this type of padlet you can connect your comments to others!
1. Read
2. Write your post
3. Click the 3 dots in the top right hand corner of your post and click "connect"
4. Click the connect button on the post you're connecting with!

# data[].attributes.headline
Get the conversation started for Option 2!

# data[].attributes.subject
Get the conversation started for Option 2!

# data[].attributes.headline
Get the conversation started for Option 1!

# data[].attributes.subject
Get the conversation started for Option 1!