# data[].attributes.body
Roles and Partners
Metrics
Workstreams
Trainings

Next week we will start dissecting each category. This will create the system for start of year

# data[].attributes.body
Making sure that our goals align with the data that we are collecting and how we are collecting it and creating it in our daily service.

# data[].attributes.body
-          Clarity (or lack thereof)

-          Shared understanding of what service is/how it’s done

-          Feedback loops + consistency

# data[].attributes.body
Clarity on the purpose of each segment of data and data collection and how the data is utilized by departments site wide

# data[].attributes.body
Confidence in utilizing our data as a site

# data[].attributes.body
Backwards planning with the end in mind to build  the best way to make it to the end

# data[].attributes.body
There is a strong desire for us to come together for a consensus making this work

# data[].attributes.body
Finding a shared "why" behind the work we do, the information we collect and how we communicate it. Getting everyone on the same page and feeling confident to execute to results

# data[].attributes.body
Individuals will understand the impact in the moment - seems obvious, but it's not always a thing that all ACMs see.

# data[].attributes.headline
Aside from clarity, I believe this process will reveal to us the areas of our data that have been forgotten and or looked over and allow us to create an intentional system that makes sure that no parts of the data world end up on the back burner. 

# data[].attributes.subject
Aside from clarity, I believe this process will reveal to us the areas of our data that have been forgotten and or looked over and allow us to create an intentional system that makes sure that no parts of the data world end up on the back burner. 

# data[].attributes.body
Hopefully this will improve ACM feelings of preparedness and role clarity

# data[].attributes.headline
I am working to understand the purpose and role of data outside of the school building. What are our data-based goals, where do they come from, who all in invested in us accomplishing them, and which data is most useful to which persons. 

# data[].attributes.subject
I am working to understand the purpose and role of data outside of the school building. What are our data-based goals, where do they come from, who all in invested in us accomplishing them, and which data is most useful to which persons. 

# data[].attributes.body
Team work, students first collaboration always, service to a cause greater than self

# data[].attributes.body
This can also help inform how reports get better? I know that's simple but I love that

# data[].attributes.body
Challenge: ACMs on different levels of understanding at all times, regardless of the training
Opportunity: data-focused skills-based trainings

# data[].attributes.body
Hopefully with everyone being on the same page, ACMs and staff can feel more aligned and on track (without feeling surprised about expectations at any point in time) (Jodi)

# data[].attributes.body
I also see this exercise helping ICs figure out what kind of data they want to be measuring next year too....

# data[].attributes.body
The full team must be committed to doing the work and sticking to the plan. We will have to revisit the information over time

# data[].attributes.body
PROCESS FOR TESTING AND LEARNING!!!!!

# data[].attributes.headline
For me the top motivators in these sessions are clarity and collaboration. Understanding the big picture and setting ourselves up for success in future years to come.

# data[].attributes.subject
For me the top motivators in these sessions are clarity and collaboration. Understanding the big picture and setting ourselves up for success in future years to come.

# data[].attributes.headline
TEAMWORK - I'd like to continue to build connections across my own team, but also the other teams who are using the same data (e.g. - office based staff?) 

# data[].attributes.subject
TEAMWORK - I'd like to continue to build connections across my own team, but also the other teams who are using the same data (e.g. - office based staff?) 

# data[].attributes.body
As an IC, I'm interested in using data to inform the work I do with ACMs that are directly tied to improving our student outcomes. I want to have a shared definition of skills that drive outcomes so that we can collect the right data for the right reason (Jodi)

# data[].attributes.body
feedback loops and lack of communication when it comes to our data process and student outcomes

# data[].attributes.headline
My hope is that this process will establish a deeper understanding of all of the roles that are affected by data, and when necessary we will identify collaborative solutions to improve our data.

# data[].attributes.subject
My hope is that this process will establish a deeper understanding of all of the roles that are affected by data, and when necessary we will identify collaborative solutions to improve our data.

# data[].attributes.headline
shared understanding of the data we already have access to prompting discussions on what we can add or improve + how we share that with necessary stakeholders 

# data[].attributes.subject
shared understanding of the data we already have access to prompting discussions on what we can add or improve + how we share that with necessary stakeholders 

# data[].attributes.body
It will help me if we realign to our purpose throughout the process and keep consistent so that we don't get lost along the way (Jodi)

# data[].attributes.body
If staff and ACMs understand the data we are using and how to utilize that data, we can better communicate with our school partners

# data[].attributes.body
I also think a challenge is that we haven't in the past had real outcomes data on a week-to-week basis. Only outputs. Consistency is a good step forward though

# data[].attributes.headline
The result from the collaborative approach to data will create a result that may be more complex at face value, but will be more effective and understood because each person will be able to go to the same product to find what they need.

# data[].attributes.subject
The result from the collaborative approach to data will create a result that may be more complex at face value, but will be more effective and understood because each person will be able to go to the same product to find what they need.

# data[].attributes.body
Using data for a purpose! (Jodi)

# data[].attributes.body
The work will improve as folks in all positions begin assessing the same data and speaking the same language. Not that this is not happening now, but a clearer process of what data is being used/how it is collected will be helpful for driving investigative and reflective conversations.

# data[].attributes.body
A share approach will allow for both all parties to understand and have a part in developing the "why" behind the data use. This will lead to greater buy in and hopefully more incorporation into the service experience

# data[].attributes.body
Improve my understanding of what IMs are interested in. Do they care about consistency each week? Or would another measure/metric be more helpful as a manager?

# data[].attributes.body
I think a shared approach to data use and having the most up to date information will help impact staff at school sites improve feedback loops with school partners like admin and teachers by being able to hold more informed decision making conversations around service

# data[].attributes.body
I'm hopeful that having a shared vision will make the ICs and IMs and ACMs work more cohesively and with the same information source driving our conversations

# data[].attributes.body
A unified approach to how we interpret and utilize our data

# data[].attributes.body
I want to keep a value of students first, collaboration always. Sometimes I feel like it's easy to lose to perspective/value when we talk about data that we should be looking to understand not only how ACMs are navigating their work but ALSO how they are benefitting students or not.

# data[].attributes.body
coming to a clear understanding together of what the data that we have available to us can be used for -- is this data going to be used to understand how ACMs are getting their work done? Or is this data going to give us a picture into how students are being impacted by ACMs?

# data[].attributes.body
coming to a consensus on what kind of data the Impact team is interested in at what cadence (consistency data weekly; student growth data weekly; MAP data quarterly; etc.)

# data[].attributes.body
I think having a shared approach to data use will help the data team present the most real-time/relevant info to the Impact team each week AND ALSO make pathways for IMs/SLs/IDs/etc. to explore data on their own as they become curious.