# data[].attributes.body
Sharing resources & strategies that have worked

Suggestion: add a resource section

# data[].attributes.body
Keep the dedicated space and time for us to validate/sanity check one another and collaboratively solve problems

Suggestion:
Great emotional support, but can also feel overwhelming

# data[].attributes.body
Moving us/forward back taking up half the meeting. Let's choose a time and hold to it.  KP

# data[].attributes.body
The google doc is really overwhelming and hard to read

# data[].attributes.body
+1 on moving us forward/holding us back. Shows validation and support, raises concerns across the PSLs -KP

Maybe MF/HB goes to the end so that if we have time we can still capture. Or it’s just written for people to read at their leisure (CH)

Suggestion:
- It often dominates what we do; can we move this to end, or reflect before the meeting?
- It is nice to start the meeting with celebrations
- Do a better job of holding ourselves to time
- it often prompts longer discussions about solving important problems --> could we list what's the one thing that's been the biggest blocker for you? maybe the purpose of the meeting shouldn't be able SOLVING the issue
- more structured agenda keeping close with time (Kate and Brittany connect to look at an existing template)

# data[].attributes.headline
Filling out the moving us forward/holding back during the meeting. 

# data[].attributes.subject
Filling out the moving us forward/holding back during the meeting. 

# data[].attributes.body
+1 KP
+1 NG

# data[].attributes.body
I wonder if there would be value for PED or CLG to be a fly on the wall; getting more context for the real work in the field. Maybe one designated person (CH) +1 (CG) +1(NG); example: moving us forward and holding us back

Problem trying to solve: people outside of PSLs feel removed from what's actually happening in the field

Concern:
- if we add another person, it may derail our meetings
- would this continue to be a safe space?

Suggestion:
- could we have a designated PSL who will communicate the information back?
- should we be creating space in our other meetings to share information?
- should we open it up once a month for people to attend and build empathy?
- would be great to have Bill there once a month
- could we have a 30 min touchpoint outside of the meeting? or add this to PED / PSL?
- bold items go on PED / PSL and CLG meeting?
Next steps:
Spend 10 mins of reflection time at PSL meeting identifying items that need to be brought up to other teams

# data[].attributes.body
+1 AVF

# data[].attributes.headline
Filling out the moving forward/holding back BEFORE the meeting. AVF

# data[].attributes.subject
Filling out the moving forward/holding back BEFORE the meeting. AVF

# data[].attributes.headline
Sharing things for us to read after [BG]

# data[].attributes.subject
Sharing things for us to read after [BG]

# data[].attributes.body
It's really hard to have reading homework from this meeting. I'd prefer to get the updates ahead of time OR in the meeting.

# data[].attributes.body
+1 KP

# data[].attributes.body
Suggestion:
- For holding us back --> do you need a solution or just acknowledge something is happening

# data[].attributes.headline
Important updates and info to kick-off our week. AVF

# data[].attributes.subject
Important updates and info to kick-off our week. AVF

# data[].attributes.body
- sometimes hard to bring things over to the next week

# data[].attributes.body
Move to the top of the session +1 AVF

# data[].attributes.body
Problem:
- It's easy to get lost in the document

Solution
- Is there a collaborative software where it can aggregate our moving us forward / holding us back? (AVF)
- Asana allows to assign comments
- It is helpful to have the summary / follow up --> but could we use that format and then bookmarks?
- Can we have a cleaner version of the doc?

# data[].attributes.headline
Love the idea of simple pre-work reflections, maybe we could even do it in a form or on a padlet? CG

# data[].attributes.subject
Love the idea of simple pre-work reflections, maybe we could even do it in a form or on a padlet? CG

# data[].attributes.headline
More time at the top for the to-do list review, it gets rushed and this gets stressful (CG)

# data[].attributes.subject
More time at the top for the to-do list review, it gets rushed and this gets stressful (CG)

# data[].attributes.headline
Do more generative work together, not just share outs (CG) +1

# data[].attributes.subject
Do more generative work together, not just share outs (CG) +1

# data[].attributes.body
Suggestions:
- The meeting is a lot of sharing and not a lot of doing; could we do 15 mins of doing work together on something?
- Even use time for some of the to-dos
- Problem / solution --> identify one of the problems and tackle it in the meeting

# data[].attributes.headline
1x a month look at calendars together to get a sense of who is where and doing what (CG)

# data[].attributes.subject
1x a month look at calendars together to get a sense of who is where and doing what (CG)

# data[].attributes.body
+1 (NG)

# data[].attributes.body
There are too many docs, decks, sheets and it's often hard to remember the right place to go (CH)

Suggestion:
Could we add a footer or links to top to a meeting agenda doc with key links?

# data[].attributes.headline
Designated owner of all PSL requests + start sharing those requests on this call [BG]

# data[].attributes.subject
Designated owner of all PSL requests + start sharing those requests on this call [BG]

# data[].attributes.body
Suggestion:
- One owner who collects all of the information and puts them in one place
- If someone has a request, it has to go through a specific email and fill out a template
- Make space in each meeting with what is needed from PSLs

# data[].attributes.headline
Pushing people to clearly articulate what they need [BG]

# data[].attributes.subject
Pushing people to clearly articulate what they need [BG]

# data[].attributes.body
When anyone has a to do or an ask, we should coach them to be clearer in articulating that ask (what, when, who, etc). If it's just an FYI vs an ask vs get feedback, be clear.

Suggestions:
Need to have a clear request
Need to have a due date

# data[].attributes.body
check-in
recurring updates
collaborative agenda creation
check-out