# data[].attributes.headline
Changes that are in process that are working involve areas of communication especially to our TAP meeting agenda. We are reviewing next steps at the beginning of each meeting and sharing updates. Communication seems to be more clear about the how, what, where, who, and why of updates/projects. This is noted in the TAP agenda minutes which is very helpful for keeping track of details.  Email communication has been more clear with more details. It seems like team members are more communicative by asking clarifying questions and that is helpful as well.     

# data[].attributes.subject
Changes that are in process that are working involve areas of communication especially to our TAP meeting agenda. We are reviewing next steps at the beginning of each meeting and sharing updates. Communication seems to be more clear about the how, what, where, who, and why of updates/projects. This is noted in the TAP agenda minutes which is very helpful for keeping track of details.  Email communication has been more clear with more details. It seems like team members are more communicative by asking clarifying questions and that is helpful as well.     

# data[].attributes.headline
It seems like we need a place to put information that is shared when we don't have a TAP meeting during the week and we are communicating via email only. It is hard to remember all the details so it is great to have the TAP meeting agenda to review when we've had a meeting but when we don't have a meeting there is no place to hold all the details of our communications. We also talked about having all of our documents for projects -surveys, evaluations, etc all in one place as well.

# data[].attributes.subject
It seems like we need a place to put information that is shared when we don't have a TAP meeting during the week and we are communicating via email only. It is hard to remember all the details so it is great to have the TAP meeting agenda to review when we've had a meeting but when we don't have a meeting there is no place to hold all the details of our communications. We also talked about having all of our documents for projects -surveys, evaluations, etc all in one place as well.

# data[].attributes.headline
We need to talk about capacity and what is doable based on staffing and what needs to be developed and facilitated. 

# data[].attributes.subject
We need to talk about capacity and what is doable based on staffing and what needs to be developed and facilitated. 

# data[].attributes.body
Reviewing next steps at the beginning of each meeting has been really helpful. There has been more two way communication via email in between meetings.

# data[].attributes.body
It would be helpful to have a general practice of saving all google docs for our projects to our TAP google folder (example: BC planning/survey documents, evaluation reports). This would help us stay organized.
The email communication in between meetings has been really helpful but then sometimes emails get lost later on. Can we add those updates (cut and paste) to our TAP agenda or document for the project (ex. BC survey)?

# data[].attributes.body
There have been clearer asks within emails. For example, with doing the content reviews, it was helpful that there was an email containing specific questions that the content developers should address. Having team members provide responses in the agenda prior to the TAP meeting has also been helpful and sometimes made discussion more efficient.

# data[].attributes.body
I agree with a system to organize information that is shared via email - it can be a lot to keep track of.
I also agree that as we continue to plan for next year, we need to discuss capacity and how this would impact possible projects or roles on projects.

# data[].attributes.body
Clear ask of what is expected to share when doing a content review. It is clear what Molly needs from us and we have implemented those changes smoothly.

Reviewing next steps and actually following up on parking lot items has been very helpful

Encouraging pre work so that at the meeting we are not passive recipients of information and can spend our time discussing and unpacking any questions we may have about the updates/tasks at hand

# data[].attributes.body
Re: communication. Adding a section in the agenda that holds information that was emailed in between meetings can be super helpful to hold all information in one place

RE: planning for the future it would be helpful to address what are the expectations leadership has of how many deliverables we need to have next year overall and how that will impact workload for each team member. What that means for a full time position vs a 30hr position.

How many hours will we commit to SW department? if that is clear we can have a voice on how to structure the hours because brainstorming without boundaries is very difficult.

How many hours/trainings (however leadership will like to define this) for other projects?

Having a benchmark can be super helpful like we have had in the past TAP teams. How many end products will feel like we are honoring the amount of money we are given for this work? - that is something I do not feel qualified to make a decision on.

# data[].attributes.headline
For next steps- I like the idea of what we did after our first retreat-  maybe we can decide together on a couple of things to try out and then we check in to see how it's going.

# data[].attributes.subject
For next steps- I like the idea of what we did after our first retreat-  maybe we can decide together on a couple of things to try out and then we check in to see how it's going.

# data[].attributes.body
As we look into diversifying what trainings we will do next year, how do we keep in mind staffs preferences for types of work as well as keeping the collaboration in projects going to avoid a return to assigning individual projects to individual people. That practice created isolation and inhibited collaboration and innovation that happens when more than one person works on a project.