# data[].attributes.headline
appreciated getting to look back at our evaluations from the end of 2023

# data[].attributes.subject
appreciated getting to look back at our evaluations from the end of 2023

# data[].attributes.body
A lot of us used the time to read the evaluations so there was no real time to discuss or even take action on anything that was uplifted.

# data[].attributes.headline
was great to look back at evals, but our group spent the whole triad session just reading ours bc it arrived right before the sesh. maybe send any docs more in advance next time?

# data[].attributes.subject
was great to look back at evals, but our group spent the whole triad session just reading ours bc it arrived right before the sesh. maybe send any docs more in advance next time?

# data[].attributes.body
With clear, thought provoking questions that helped us get to the meat of the issues

# data[].attributes.headline
that 1 hr break in between blocks was so key!! Thank you for building in that spaciousness

# data[].attributes.subject
that 1 hr break in between blocks was so key!! Thank you for building in that spaciousness

# data[].attributes.headline
Really loved the padlet as a tool, and Julian's facilitation using the padlet to encourage more conversation and elaboration

# data[].attributes.subject
Really loved the padlet as a tool, and Julian's facilitation using the padlet to encourage more conversation and elaboration

# data[].attributes.headline
For future evaluations, I wish we had more time and preparation before we were doing the eval. 30 minutes during a staff meeting where it wasn't expected didn't work for me. I would have liked to have done some of the circle evaluation in conversation within our circle with shared prompts for example. I did appreciate having space for reflection though - agree that it's super important and grateful for the labor that went into it

# data[].attributes.subject
For future evaluations, I wish we had more time and preparation before we were doing the eval. 30 minutes during a staff meeting where it wasn't expected didn't work for me. I would have liked to have done some of the circle evaluation in conversation within our circle with shared prompts for example. I did appreciate having space for reflection though - agree that it's super important and grateful for the labor that went into it

# data[].attributes.headline
Agenda felt packed, and therefore the pacing was intense

# data[].attributes.subject
Agenda felt packed, and therefore the pacing was intense

# data[].attributes.body
Loved the slider in general, but particularly revisiting it after our conversation

# data[].attributes.headline
lovvved the framing for the sessions, felt v clear. didnt have enuf time to go thru all charters tho

# data[].attributes.subject
lovvved the framing for the sessions, felt v clear. didnt have enuf time to go thru all charters tho

# data[].attributes.headline
such great faciliation all around. loved the hot takes section, & how it was framed language of 'assumptions'. felt like a moment where we could all be real. 

# data[].attributes.subject
such great faciliation all around. loved the hot takes section, & how it was framed language of 'assumptions'. felt like a moment where we could all be real. 

# data[].attributes.headline
I'd really like us to adjust Thursday's schedule so that west coast folks don't have to start at 8am!

# data[].attributes.subject
I'd really like us to adjust Thursday's schedule so that west coast folks don't have to start at 8am!

# data[].attributes.headline
KEEP: amazing facilitation, topics all connected, breaks, time during sessions to read/add to padlet (vs homework) ending with debrief/actions

# data[].attributes.subject
KEEP: amazing facilitation, topics all connected, breaks, time during sessions to read/add to padlet (vs homework) ending with debrief/actions

# data[].attributes.headline
CHANGE: spread out planning/facilitation more, more prep time, maybe fewer sessions, add in board session

# data[].attributes.subject
CHANGE: spread out planning/facilitation more, more prep time, maybe fewer sessions, add in board session

# data[].attributes.headline
Where does GO week planning/coordination live? 

# data[].attributes.subject
Where does GO week planning/coordination live? 

# data[].attributes.headline
Do we want to keep doing this quarterly? More, less, not at all? 

# data[].attributes.subject
Do we want to keep doing this quarterly? More, less, not at all? 

# data[].attributes.headline
Was this about the right amount/type of time?

# data[].attributes.subject
Was this about the right amount/type of time?

# data[].attributes.headline
Is there a desire to integrate board and/or members for a session in the future?

# data[].attributes.subject
Is there a desire to integrate board and/or members for a session in the future?

# data[].attributes.headline
Make sure to reserve 5 minutes at the end of each session so people can do the padlet feedback. I think it's a good practice for us to sharpen our collective facilitation craft, not to mention inform upcoming sessions

# data[].attributes.subject
Make sure to reserve 5 minutes at the end of each session so people can do the padlet feedback. I think it's a good practice for us to sharpen our collective facilitation craft, not to mention inform upcoming sessions

# data[].attributes.headline
EOY campaign debrief was out of place/not relevant to governance

# data[].attributes.subject
EOY campaign debrief was out of place/not relevant to governance

# data[].attributes.headline
What's the *culture* that we want to sustain our WSDNP structure with?

# data[].attributes.subject
What's the *culture* that we want to sustain our WSDNP structure with?

# data[].attributes.headline
My big hot take: I think we should empower a team of three people to design all the sessions vs. passing each thing between facilitators. I think that allows more cohesion and overall flow. That doesn't mean that other people won't be asked to present on things, but I would love to see us empower/trust a facilitation team to hold us. 

# data[].attributes.subject
My big hot take: I think we should empower a team of three people to design all the sessions vs. passing each thing between facilitators. I think that allows more cohesion and overall flow. That doesn't mean that other people won't be asked to present on things, but I would love to see us empower/trust a facilitation team to hold us. 

# data[].attributes.headline
Do we want to share our GO Week procedures and reflections outside to our network? 

# data[].attributes.subject
Do we want to share our GO Week procedures and reflections outside to our network? 

# data[].attributes.body
would be cool to be more intentional about sharing governance learnings to our network, esp those looking to transition to alternative models

# data[].attributes.headline
second part of the session with the sticky notes and big q's felt less clear to me than the first part. 

# data[].attributes.subject
second part of the session with the sticky notes and big q's felt less clear to me than the first part. 

# data[].attributes.body
could benefit from clearer instructions next time!

# data[].attributes.headline
i liked this process and liked that it encouraged the facilitator to just propose something!

# data[].attributes.subject
i liked this process and liked that it encouraged the facilitator to just propose something!

# data[].attributes.headline
Looking forward to getting to talk about retrospectives...feedback...etc 

# data[].attributes.subject
Looking forward to getting to talk about retrospectives...feedback...etc 

# data[].attributes.headline
I would loveee for GO week team to make a menu of all the different committees and governance labor coming up, so we can make sure everyone is involved in something and no one is over burdened

# data[].attributes.subject
I would loveee for GO week team to make a menu of all the different committees and governance labor coming up, so we can make sure everyone is involved in something and no one is over burdened