# data[].attributes.headline
Clarify expectations and support needed on-site

# data[].attributes.subject
Clarify expectations and support needed on-site

# data[].attributes.body
SD meeting went well - It was good to have the longer meeting time in the AM. Can we include a more structured break between the newbie session and the returners in order to smooth out that transition?

# data[].attributes.body
Very helpful. Would it be possible to have to have the SI specific resources (or links to them) in the folder as well?

# data[].attributes.body
How about a one-pager with guiding questions and and coaching stems to support rigorous and structured conversation? (Because as you all know - what we need is one more one-pager:))

# data[].attributes.body
Amazing!!!!!!!!

# data[].attributes.body
Develop and train a support team to field SD specific questions and issues.

# data[].attributes.body
Might be helpful to create a meeting template with key areas to address.

# data[].attributes.body
Should it be SOP to provide ISD team with list of singletons at the Day 0 meeting? If so, can SDS provide that as part of Day 0 setup? And a lsit of ISD team phone numbers?

# data[].attributes.body
The staff developer supports were once again great! They seemed very well prepared

# data[].attributes.body
It was a great launch to the project. Staff Developers seemed comfortable with the app and gave great feedback for updates. The AVID Roster team has that feedback for their refinements

# data[].attributes.body
I liked the balance of community building, logistics, and internal professional learning (the goal activity work)

# data[].attributes.body
The differentiated times supported and honored our staff developers time. They could choose to attend the morning part more than once or just come at 10 am.

# data[].attributes.headline
There definitely needs to be a clear break between the newbie session and the beginning of the larger meeting.  In addition, it would be good to create a quick team builder to do at the start of the newbie session.  The start was kind of flat (Denise)

# data[].attributes.subject
There definitely needs to be a clear break between the newbie session and the beginning of the larger meeting.  In addition, it would be good to create a quick team builder to do at the start of the newbie session.  The start was kind of flat (Denise)

# data[].attributes.body
The resources are great but the volume got a little large which led to more searching than desired.  Lets brainstorm a way to streamline (Denise

# data[].attributes.body
I like the idea of the one pager and I think we might consider asking one staff developer from each strand to be the leader of the session to ensure strong facilitation (Denise)

# data[].attributes.body
Great job Michelle C and Sara Beth  They were so well prepared (Denise)

# data[].attributes.body
Create an enter button on the app so Staff Developers get a sense of completion regarding attendance (Denise)

# data[].attributes.headline
The first year staff developer needs community building at the beginning of the meeting. There also needs to be about 15 minute break between sessions. 

# data[].attributes.subject
The first year staff developer needs community building at the beginning of the meeting. There also needs to be about 15 minute break between sessions. 

# data[].attributes.headline
I like the idea of guiding questions for debrief. 

# data[].attributes.subject
I like the idea of guiding questions for debrief. 

# data[].attributes.headline
Great support. Perhaps need training to help troubleshoot the technology tools used in strands. 

# data[].attributes.subject
Great support. Perhaps need training to help troubleshoot the technology tools used in strands. 

# data[].attributes.headline
Need additional support for troubleshooting issues. 

# data[].attributes.subject
Need additional support for troubleshooting issues. 

# data[].attributes.headline
Everything needed was available; however, sometimes it took a bit of time to find what was needed. 

# data[].attributes.subject
Everything needed was available; however, sometimes it took a bit of time to find what was needed. 

# data[].attributes.headline
I agree with all comments. The first year staff developer meeting should have an opener to help begin that community building. I thought having an ice breaker went well for that, and continue to refine. Break needed between the newbie session and main meeting. Michelle

# data[].attributes.subject
I agree with all comments. The first year staff developer meeting should have an opener to help begin that community building. I thought having an ice breaker went well for that, and continue to refine. Break needed between the newbie session and main meeting. Michelle

# data[].attributes.headline
It was helpful having everything in one place. Maybe include that SI-specific folders so that we can share with our co-facilitators the revised presentations. How can we also catalog questions, concerns, a-ha's, etc from the previous SI for the remaining SIs? Michelle

# data[].attributes.subject
It was helpful having everything in one place. Maybe include that SI-specific folders so that we can share with our co-facilitators the revised presentations. How can we also catalog questions, concerns, a-ha's, etc from the previous SI for the remaining SIs? Michelle

# data[].attributes.headline
I think next year, we have a greater opportunity to front-load information so that the Day 0 meeting includes more like reminder points. Michelle

# data[].attributes.subject
I think next year, we have a greater opportunity to front-load information so that the Day 0 meeting includes more like reminder points. Michelle

# data[].attributes.headline
Can we use AVID Roster to check in staff developers for Day 0 mtg? Lets model it. 

# data[].attributes.subject
Can we use AVID Roster to check in staff developers for Day 0 mtg? Lets model it. 

# data[].attributes.headline
Move all docs toward electronic. With the SI app next year, we wont need to distribute the program. The emergency number card can be electronic or placed on PPT slice and staff dev take pic, it should also be in the bulletins. Day 0 bulletins should also be electronic. 

# data[].attributes.subject
Move all docs toward electronic. With the SI app next year, we wont need to distribute the program. The emergency number card can be electronic or placed on PPT slice and staff dev take pic, it should also be in the bulletins. Day 0 bulletins should also be electronic. 

# data[].attributes.headline
We can move to one dev support for most SIs. Not sure need more than one now with the ISDs, especially the lead ISD, providing a lot of support

# data[].attributes.subject
We can move to one dev support for most SIs. Not sure need more than one now with the ISDs, especially the lead ISD, providing a lot of support

# data[].attributes.headline
Is there a way to document ahas, questions, etc. electronically so even if you are alone, no other SI strand like yours, you can see what others wrote on a live link/page

# data[].attributes.subject
Is there a way to document ahas, questions, etc. electronically so even if you are alone, no other SI strand like yours, you can see what others wrote on a live link/page

# data[].attributes.headline
Keep the Differentiated meeting, but make a clear start for the second meeting.  

# data[].attributes.subject
Keep the Differentiated meeting, but make a clear start for the second meeting.  

# data[].attributes.headline
Cleaner file naming and organization could be helpful.  I found myself clicking a lot.  It was good having everything in one place.  The concerns link was hard to find and I think the 2017 file was in this years so that was confusing at first.  Consider giving ISD access to the folders needed for coaching and observations (flow chart for addressing issues, etc.)

# data[].attributes.subject
Cleaner file naming and organization could be helpful.  I found myself clicking a lot.  It was good having everything in one place.  The concerns link was hard to find and I think the 2017 file was in this years so that was confusing at first.  Consider giving ISD access to the folders needed for coaching and observations (flow chart for addressing issues, etc.)

# data[].attributes.headline
Do we have any data or feedback on how these went?   Maybe add a file for the stands to capture a debrief reflection or notes as they are meeting.  

# data[].attributes.subject
Do we have any data or feedback on how these went?   Maybe add a file for the stands to capture a debrief reflection or notes as they are meeting.  

# data[].attributes.headline
Very positive experience and changes for activities over the summer were beneficial.  

# data[].attributes.subject
Very positive experience and changes for activities over the summer were beneficial.  

# data[].attributes.headline
Went well.  Captains were prepared and really took the lead with the meetings.  

# data[].attributes.subject
Went well.  Captains were prepared and really took the lead with the meetings.  

# data[].attributes.headline
Tech team on the ground were very responsive and visible.  Would be good if the created a file for us of "commonly seen issues" for us to have going in to the second year.  

# data[].attributes.subject
Tech team on the ground were very responsive and visible.  Would be good if the created a file for us of "commonly seen issues" for us to have going in to the second year.  

# data[].attributes.headline
I think the responsibilities for the captain's role should be a bit more explicit so that there is consistency between all SIs and staff developer directors.

# data[].attributes.subject
I think the responsibilities for the captain's role should be a bit more explicit so that there is consistency between all SIs and staff developer directors.

# data[].attributes.headline
Can we get the roster to scroll faster? 

# data[].attributes.subject
Can we get the roster to scroll faster? 

# data[].attributes.headline
Have the Staff Developer Support schedule a text reminder toward the end of the day on Day 1 (we did this at a few SIs but was not a part of our Templates)

# data[].attributes.subject
Have the Staff Developer Support schedule a text reminder toward the end of the day on Day 1 (we did this at a few SIs but was not a part of our Templates)

# data[].attributes.headline
Loved having SDs access SI specific logistics information digitally, but would like to evaluate different platforms. SharePoint/Word Online worked okay this year, but did not allow SDs to download/save the document.

# data[].attributes.subject
Loved having SDs access SI specific logistics information digitally, but would like to evaluate different platforms. SharePoint/Word Online worked okay this year, but did not allow SDs to download/save the document.

# data[].attributes.body
Where two staff developer support staff are needed is at large SIs with multiple hotels and convention center being used (Dallas, SD2)- Linda

# data[].attributes.body
Need to make sure the Roster is available to singleton SD who manage two groups (ML/HS strands)