# data[].attributes.body
Strong integrations and focus on CCI.

# data[].attributes.body
Enlarge font of most critical information/directions on Canvas Page so that participants have a quick means of checking their navigation.

# data[].attributes.body
Consider eliminating Perusall (with reluctance since I think we just need to know more about how to use the power of the tool ... maybe next time:-)

# data[].attributes.body
Modify approaches to reading text by varying Academic Language Learning strategies (choral/drop in/AB partner/active listening/word bank/sentence frame response, etc)

# data[].attributes.body
Extend Brainstorm Carousel in Systems module to include silent home group brainstorm, carousel additions with coding and a brief, structured report out strategy that deepens understanding and extends potential applications.

# data[].attributes.body
Strengthen emphasize on the "why" we are here and "how" we will learn together within the AM of Day 1 with specific attention to:  modeling, use of norms and processing practices (cups/sentence frames on name tents/domain and other partnering strategies/attention getters/callbacks/brain breaks https://nedbreaks.com/ ) and then be sure to incorporate/reinforce throughout strand.

# data[].attributes.body
Eliminate 1 or 2 videos and modify tasks involving remaining videos so that participants view them in different modes (individual /whole group) and with clear intentionality (look fors/taking notes)

# data[].attributes.body
Reduce content by approximately 60 minutes by integrating the instructional debrief and CCI/Site Team reflections and reducing the time spent on the ISTE standards for students.

# data[].attributes.body
We have plenty of content to work with.  Team felt that some of the things to look towards is to address approaches to learning.

# data[].attributes.body
The team was able to collect a lot of feedback. Lots of collaboration.

# data[].attributes.body
Staff Developers got a chance to experience the strand as a participant.

# data[].attributes.body
The pilot gave us an opportunity to be in a learning enviornment

# data[].attributes.body
Was the frontload, immerse, debrief, apply AVID PL framework modeled appropriately?

# data[].attributes.body
Could we plan out how to intentionally provide basic tool support?  How can we help participants feel comfortable with navigating the tools?

# data[].attributes.body
This didn't 'not work' but would be good to move earlier in the strand

# data[].attributes.body
THe shared screen in front that the presenters used was very difficult to see.  It wasn't useful for following along, as it was far too small in terms of font

# data[].attributes.body
I think the pairing was great - having a person who is a strong tech expert and another who is a strong AVID strategies practitioner was great.

# data[].attributes.body
I think one of the staff developers had a really strong sense of facilitation, and the other was more on the technical side.

I wonder, how much of the WICOR movement we experienced was written into the strand versus facilitation of the strand.

# data[].attributes.body
May look at the order the Digital Storytelling module is done - seemed a bit disjointed.

# data[].attributes.body
This was a really disconnected brainbreak and I think it would be better to switch that one out.

# data[].attributes.body
though I understand the focus on learning, digital tools often require a longer learning curve in terms of basic operation.  I thought the tools overviews and experimentation could have been given a little more time for those newbies who'd not used them previously to get familiar.  Perhaps this can be addressed in the pre-participation homework.

# data[].attributes.body
Click-by-click modeling needs to be done the first time we use every tool. And only intro one tool at a time

# data[].attributes.body
If we are going to use images to post the questions on Kahoot as a workaround to the character limit, I would recommend using a more high contrast image to better accommodate those with visual support needs

# data[].attributes.body
The Name tent was difficult to see before we had access to the OneNote

# data[].attributes.body
I was impressed with how the group work--right down to how groups were selected--was so strategic.  Group work can often be inefficient in terms of time and process, but because of the well-thought-out AVID group work structure, things got done in conjunction with the pilot goals.

# data[].attributes.body
Going between Canvas, Classroom, eBinder, and other tools being used was confusing and hard for participants

# data[].attributes.body
Kahoot is a great tool, and I think it has potential to be worked out before SI. I think it would be helpful to edit the questions to try and make them more succinct

# data[].attributes.body
There was never a time when it felt like the tools superceded the learning in terms of the focus.  The 4As and WICOR came through clearly as the overall focus.

# data[].attributes.headline
Level of Google Activities high for a beginner in Google.

# data[].attributes.subject
Level of Google Activities high for a beginner in Google.

# data[].attributes.body
But with the proper instructions and scaffolds should be accessible.

# data[].attributes.body
It was a little convoluted and disconnected to clearly exemplify the 4 stages of the As

# data[].attributes.body
Too much tool focus out of context of the content we were learning. Tools were the take away in many cases, and the learning came second.

# data[].attributes.body
Even though the group was small, there was still diversity in the perspectives represented and discussion was rich.

# data[].attributes.body
Many missed opportunities to apply APLPs and only loosely followed the syllabus.

# data[].attributes.headline
Direct connection from tool to AVID strategy.

# data[].attributes.subject
Direct connection from tool to AVID strategy.

# data[].attributes.body
These needed to be chunked and clear

# data[].attributes.body
I liked the idea of Digital storytelling as the theme.

# data[].attributes.body
Activity and group discussion

# data[].attributes.headline
Connection to Digital Storytelling and the Writing Process

# data[].attributes.subject
Connection to Digital Storytelling and the Writing Process

# data[].attributes.body
Using OneNote as the repository for all of the strand information. Being able to use it as the place where the presentation content, my notes, and activities lived was really helpful and useful.

# data[].attributes.body
, Cheryl from DTL and Virginia the staff developer, were an excellent team.  They complimented each other's skills well, and did a great job maintaining flow and pace. Having the right "mix" of strand leaders in the room In terms of skills and abilities is absolutely crucial for strand effectiveness.

# data[].attributes.body
Useful extensions that are used in innovative ways.

# data[].attributes.body
Were engaging

# data[].attributes.body
I think having the OneNote as a  driver of the content.  I think it might be better to have  the presenters primarily in the OneNote