# data[].attributes.body
We have a ton of data in schools.  There is no way a school can analyze it all in a 90 minute meeting.  As schools identify available data, we need some guidance on how to prioritize and select the right data.

# data[].attributes.body
We believe guidance should be included that encourages the CI team to solicit feedback on data from the staff BEFORE event 3 happens.  This would enable the school to present data findings to the community (Event 2) to get their input as to why they believe the data looks the way it looks and offer potential solutions for the school team to consider as they dig deeper into the data.  And it gives the "lead" an opportunity to collect and synthesize the data to present to the CI team during event 3.  Activities such as a data carousel/gallery walk would work well.  The Data Analysis Handout asks for individual reflection. We don't believe this should be done in the meeting, but again, ahead of time.

# data[].attributes.body
We need to provide guidance on how to reach a consensus within a group (Fist to Five, for example) so teams can set that norm up front to guide conversations.

# data[].attributes.body
We feel that the school community should be provided an opportunity to share their perspectives on WHY the data looks the way it looks (for example, high absenteeism on Fridays) and offer potential solutions. We do not feel schools should present all data and ask the community to analyze it. I don't think this idea comes across in the guidance/resources/tools created thus far. So we need some sample communication that schools can use. This should also include how to solicit input from the community should they not be able to attend the outreach meeting.

# data[].attributes.body
We believe a bank of questions should be provided so schools do not have to make up survey questions to send to the community.

# data[].attributes.body
We believe guidance on how to discuss data within a team is needed. Protocols such as Data Driven Dialogue and/or a protocol for examining data from the National School Reform Faculty would be helpful to school teams.

# data[].attributes.body
The Roadmap states to create a SMART goal. Schools may need guidance on how to do this.

# data[].attributes.body
School teams are asked to develop specific, actionable problem statements. They need some type of guidance, beyond a sample in the roadmap, to do this well.

# data[].attributes.body
Guidance should be provided that ensures there is an alignment between these events. They are all connected, so ensuring the data that is collected and analyzed in the first two events is the data that is used in Acts 2 and 3. We know this...but I think it should be explicitly stated somewhere early on.

# data[].attributes.body
Schools need guidance on what to do if they realize they do not have data that answers essential/probing questions.  So, in event 1, if they say "we do not have any data that tells us...." then they should be encouraged/guided to think about what data they could begin to collect and make a plan for that.  Then present that plan during Event 3.  This then also informs an action step in the Roadmap, where they say, for example, once a week/month we will collect a sample of student work and determine the level of rigor and standards alignment to evaluate "Access to rigorous texts and tasks."

# data[].attributes.body
We tell schools to determine what the root cause(s) are, but we do not provide any activities or guidance on how to lead a team to identify root causes.  Some may be really skilled in this work, and not need guidance.  But for those who need it, we should be providing it.  How will schools know they are at the narrowed root cause?  For example, weak Tier I instruction is not a root cause.  But we see that all the time in our plans.  They do not understand that they need to dig deeper into understanding WHY the tier I instruction is weak.

# data[].attributes.body
Schools need guidance on how to focus on things within their control, while acknowledging/honoring what is outside of their control.

# data[].attributes.body
Jamboards, Whip Around, Think/Pair/Share, etc. guidance should be provided to assist school teams in having conversations around root cause.

# data[].attributes.body
They are asked to draft improvement strategies in the handout, but no guidance is provided.

# data[].attributes.body
After root causes are narrowed, and improvement strategies drafted, the CI team should independently think about action steps to alleviate the root cause and meet the identified goal. They will be adding this to the roadmap in event 5, but along with resources needed, challenges to tackle, and equity supports, but no guidance or activity or instructions are provided to do this. Either a handout should be created or this information added to the root cause analysis handout so teams can think about this before event 5, or we need to create a slide deck for event 5, so this can be accomplished during event 5.

# data[].attributes.body
See homework section of Event 4

# data[].attributes.body
Nowhere in the facilitation guide or slide decks do we provide guidance on drafting intended outcomes. Not sure where this fits, but it is needed because it is included in the roadmap.

# data[].attributes.body
There are a lot of terms used in the roadmap that are not clearly defined. For example, is an improvement strategy the same as an action step? If not, clearly differentiate between these terms.

# data[].attributes.body
Event 5 is the time for the team to draft the action steps, resources needed, challenges to tackle and equity supports (the bulk of the plan) but nothing was developed to lead the team through this work. This is the Plan! This is where the school comes together to determine what they are going to do about all the things they discovered through events 2-4. We need to provide the CI team with these resources.

# data[].attributes.body
NDE should ensure there is guidance for schools to use Nevada Accountability Portal to complete the School Information page in the Roadmap. Not every school administrator (or members of the CI team) are proficient in this website.

# data[].attributes.body
We need a "thank you" draft communication for school teams to use to thank the members of the CI team, include a link to the completed roadmap, let them know they will be invited back to review progress, etc.

# data[].attributes.body
We should explicitly connect the idea the protocol used for data conversations in Event 3 to the status checks conversations.
From Facilitation Guide - "Prior to the meeting, figure out how much time you can spend on each improvement strategy so you can help the CI Team balance the need for discussion with the need to move through all of the improvement strategies." Schools may need more explicit guidance on how to do this - e.g., you have 60 minutes to discuss 6 improvement strategies  (60/6 = 10 minutes per strategy).

# data[].attributes.body
Schools are going to need guidance on Event 9, and how that will potentially take the place of Events 1-5 in year 2. Meaning, they don't necessarily need to re-create a data collection plan from the start. They might combine the data analysis/root cause analysis conversation/meeting into one as they review the summative data from the prior year. I just think we need to build this out a lot more to help schools understand what happens in this continuous process.

# data[].attributes.body
This is something my team has developed to try to assist schools with this process.  I just wanted to share it as a conversation piece.

https://docs.google.com/presentation/d/1icqvM_yyOkZ3hF001_IwTMbRwlxQGtt85Rxn34gL52c/edit?usp=sharing

# data[].attributes.body
A handout like this will help the team gather the necessary information to complete the roadmap.

# data[].attributes.attachment_link.title
Draft Event 5_ Resources, Challenges, Equity Supports Handout

# data[].attributes.body
Suggested handout for pre-work to allow CI team members to brainstorm action steps. The facilitator would fill in the information from Event 4 and send this out to the team. During Event 5, the CI team could present all ideas and work from there to determine which action steps they will implement. This enables the team to have a list of possible ideas if what they select doesn't work.

# data[].attributes.headline
CCSD Created Facilitation Guide for Event 5

# data[].attributes.subject
CCSD Created Facilitation Guide for Event 5

# data[].attributes.attachment_link.title
Event 5_ Roadmap Development Facilitation Guide (1)

# data[].attributes.headline
CCSD Created Resource for Prioritizing Action Steps

# data[].attributes.subject
CCSD Created Resource for Prioritizing Action Steps

# data[].attributes.attachment_link.title
Prioritizing Action Steps - Guiding Questions (1)