# data[].attributes.body
I think this would be a great resource to share with grade level teams. It explains the why behind common assessment data and the importance of what teams do with this data.

# data[].attributes.headline
Data Dialogue Protocol Window Assessment Determine Tier 1 Needs

# data[].attributes.subject
Data Dialogue Protocol Window Assessment Determine Tier 1 Needs

# data[].attributes.body
Excellent Data tool for anyone who hates recreating the wheel. This worksheet guides teams through the data analysis process from beginning to end.

# data[].attributes.body
I would title this worksheet "The NOW what". The instruction plans that teams would create using this worksheet is the purpose (often neglected) for common assessments and data analysis.

# data[].attributes.body
My team uses the same pre and post test based on Standard 1 skills. However, we have not created any common exit tickets for particular units/chapters/topics, etc. At our next meeting I would like to propose that we create a simple exit ticket where we can all see the results (maybe a Google form) then use the FCPS Google Doc called "Exit Ticket Data Dialogue Protocol" to see if our students are at Emerging, Developing, or Proficient levels of knowledge.

# data[].attributes.body
This resources is a great tool to guide CTs in identifying students by name and need. I like how it is easy to follow and specific to the otucomes.

# data[].attributes.headline
Team Protocol for Common Formative Assessment

# data[].attributes.subject
Team Protocol for Common Formative Assessment

# data[].attributes.body
This is great for both group reflection and individual reflection. It seems like it allows enough flexibility for teachers to continually reevaluate their teaching and also evaluate the systems in place across the CLT.

# data[].attributes.body
I can see a lot of these common pitfalls happening. The two that stood out the most to me were the pessimism and prematurely suggesting solutions. Especially after this year and the way our profession has been attacked, it is so easy to feel helpless and pessimistic. We are working harder than ever for less while getting called lazy and told we don't care about kids. As for prematurely suggesting solutions, our time is so limited it is hard not to. My team's CLT is 35 minutes during a normal school year. There is not time to have a lengthy conversation.

# data[].attributes.body
I like Jot Thoughts. Its similar to the solution tree but feels much more casual

# data[].attributes.body
I think this could be great for think, pair, share. Teachers can come to the meeting with the sheet filled out for their individual students which we will use for the foundation of our discussion. Then we can work together to complete a team-wide version

# data[].attributes.body
Having the right questions to ask to shift conversations to where we can meet the students is essential to our goals as leaders and educators.

# data[].attributes.body
I think the pitfalls presentation is a really useful tool for us as beginners as it's sometimes hard to see the common mistakes!

Specifically addressing the pessimism issue, I think focusing on internal best practice (so those that had higher achievement as supported by the data) would be a great start.

I think the latter concern about "feeling defeated no matter what" is possibly outside the scope of this and more an issue of applying a growth mindset. Instead of focusing on an ideal, improvement from baseline needs to be highlighted.

# data[].attributes.body
Team created interventions and remediation only benefit all parties when done with data. This also includes team created extensions of learning for students who have shown mastery.

# data[].attributes.body
I've never seen this page before and I think it is great! Definitely bookmark worthy.

Jot Thoughts is perfect for my team-guides thinking about how we are teaching and where gaps in both teaching and learning might be. At the same time, it isn't too wordy. A visually overwhelming page tends to cause some of my teammates to become resistant as it looks like something for which they won't have time.

# data[].attributes.body
I definitely see the challenge of the pessimism in groups I've been a part of. If the results aren't the way we hoped, many people just get discouraged and give up. Also, blaming the students for "just not getting it" happens a lot.

# data[].attributes.headline
Jot Thoughts Preassessment Data Dialogue

# data[].attributes.subject
Jot Thoughts Preassessment Data Dialogue

# data[].attributes.body
I think this could be something useful to our team and relevant to our standards and skill development. Data dialogue is not a protocol that we have incorporated. Administrators or Coaches do not attend our meetings, I think this could be a good starting tool for us.

# data[].attributes.body
I've experienced most of these pitfalls. Discussing data can feel personal, and when it doesn't look the way you want it to look, it can be emotional. Collaborative responsibility can really help work through some of these pitfalls.

# data[].attributes.body
Having a toolbox of protocols to guide a data dialogue can help teams move through pitfalls and common challenges.

# data[].attributes.headline
Team Protocol for Common Formative Assessment

# data[].attributes.subject
Team Protocol for Common Formative Assessment

# data[].attributes.body
I worked with a fabulous Math specialist who taught me a lot about math assessments in particular. I feel like this lends itself well to reflecting on assessment and making sure it can give us the best accurate information.
This form really allows for you to look at the data and see how to target students by name and need.

# data[].attributes.body
I enjoyed exploring the resource called Solution Tree Protocol. This protocol relies on data from previous years to help plan a unit and where the emphasis of certain standards might need to be. This protocol touches on the importance of reflecting on teaching practices based on data. Ultimately, this protocol might help teams work smarter, not harder.

# data[].attributes.body
I love that there are so many different options. Some questions/prompts might support teams better than others, so I am glad that there are all these options to pick and choose pieces of that would best meet the needs of different teams.

# data[].attributes.body
Looking through the pitfalls, I noticed and recognized my own engagement in many of them. They really are COMMON when discussing data, especially when it comes to "they should have learned this last year." If this year is any indication, we cannot rely on what "should have been." It is just not a valid reason to explain a undesired performance. Rather we should think deeper, using those meditative questions to collaborate and vulnerably consider where our own instruction is faulting, how we could support these students as individuals (not just collectives) and how we can help each other remain focused on our goals rather than, what is essentially, complaining.

# data[].attributes.body
I'd really like to make time to go through a lot of these. I am relatively new to FCPS, so even though I feel like I am experienced with looking at student data, it would be nice to really understand all of the tools available to me here.

# data[].attributes.headline
Protocol for Team Analysis Prior to Teaching a Unit

# data[].attributes.subject
Protocol for Team Analysis Prior to Teaching a Unit

# data[].attributes.body
I really like this because it "saves" time by thinking about student successes and struggles with the unit in previous years. While each group of students is different, keeping longitudinal data about each unit could help us see trends or patterns that are otherwise unapparent. It's a place to record all the great work we do during a data dialogue so that each time we teach the unit we can push farther rather than repeating the basic steps each time.

# data[].attributes.body
This would be beneficial to my team because it allows us to analyze all our learners and provide for rigorous learning for everyone.  We can easily identify as a grade level, who is struggling, who is understanding the material, and who needs enrichment. It then takes it one step further in providing a common lesson to support each groups needs.

# data[].attributes.body
Allowing time to process what feels like a failure evident in our data, but then being able to become your team's cheerleader and redirect their attention towards other definitions of success are both key traits of a great leader. PLCs can swing very quickly from fun yet unfocused to pessimist and hyper-
focused on the negative, and this slide deck helped me brainstorm several ways to help encourage teams to move more towards a middle ground.

# data[].attributes.headline
The idea of talking about students "by name and by need" is so important. Not seeing your classes numeral value as a whole, but the individual children and analyzing what parts of the assessments were difficult and considering why. 

# data[].attributes.subject
The idea of talking about students "by name and by need" is so important. Not seeing your classes numeral value as a whole, but the individual children and analyzing what parts of the assessments were difficult and considering why. 

# data[].attributes.body
Instead of saying engaging in a conversation by saying that students didn't get the material and did poorly on a formative assessment, take more of an action approach and reflect on what students need more support and how to give them that support. Reflect on how the material was introduced, and what can be retaught to improve the content understanding.

# data[].attributes.body
It's easy to get stuck in talking about your class as a whole and skipping over some of the important conversation about your data and the strategies that were used and the results of those strategies.

# data[].attributes.body
This slide deck had a direct connection to an earlier reading I completed: 'Leading others in the process'. In this reading, it specifically talked about setting goals and making sure to take the time to brainstorm which factors are out of the team's control before setting a goal in order to avoid this pitfall.

# data[].attributes.body
This slide deck was helpful in learning what to say when negative rhetoric tries to derail a meeting. As a leader it is important to keep the team on track and know how to respond to the team when the focus is shifted off task. The focus should always be student achievement, and how we can help students achieve. Let the data do the talking and drive the decisions.

# data[].attributes.body
This slide deck was helpful to generate ideas on how to respond to what I would call the "negative rhetoric" that can sometimes persist in PLC meetings. The focus can easily get sidetracked and as a leader it is important to know how to steer the direction of the meeting back on task. The ultimate focus needs to be on student achievement and what we can do to help students. The best way to do that is with data. Let the data do the talking.

# data[].attributes.headline
We use tableau to show our data. We gather that data and share it with the teams. The best part in my opinion is it tracks a standard over time to see how students perform during the year. 

# data[].attributes.subject
We use tableau to show our data. We gather that data and share it with the teams. The best part in my opinion is it tracks a standard over time to see how students perform during the year. 