Shifts in practices that are intended to re-engage students
The 4-step process for iteratively testing ideas that is embedded within the Eskolta Design Cycle
PDSA Cycle
A group of students at Eskolta that provide advice to network leadership
Youth Advisory Board (YAB)
A group of people working together to move the needle on a specified aim
NIC
This space provides coaches with an opportunity to share what’s working with their teams, strategies impacting students and modifications to change ideas
Consolidation
Data that helps us know whether or not a change idea is possible
Feasibility Data
The articulation of the specific area your team is trying to improve
Problem of Practice
A form of independent, critical research led by youth
Youth Participatory Action Research (YPAR)
This group is responsible for coordinating school-team learning, identifying promising ideas and practices, and sharing that learning between schools in our Network
Hub
These evidence based strategies for youth re-engagement can be shared with both internal and external audiences
Knowledge Products
Data that indicates whether or not a team is testing a change idea as intended
Fidelity data
The umbrella term for methods for improving complex systems that involves testing ideas over time
Continuous Improvement
Information and learning that emerges from direct human interaction
Street Data
This group of people engage in 8-10 collaborative training sessions and monthly coaching calls
Eskolta Fellows
These touchpoints in the design cycle are when coaches fill out their field reflection slides
Data Share Moments
A low-lift way to collect data to gauge the impact of a change idea
Embedded Measure
The tendency for teams to jump ahead and name solutions before fully understanding the depth of the problem that needs to be solved, if you’re being cheeky
Solutionitis
Information at a medium grain size that can help us identify patterns across a class or school aka GPS data
Map Data
These school teams are focused on understanding research on culturally sustaining, strengths-based practice through external research, and internal research, like gathering stories & data from students (team meetings 2-4x month)
Eskolta Exploratory
These step-by-step instructions outline the most evidence-back strategies in our Network
Change Packets
Eskolta’s term for a graphic organizer or protocol to capture the testing of a PDSA cycle
Inquiry Record
A description of a series of actions or events we believe will lead to a desired outcome
Theory of Change
Data that can help identify big trends in the data in order to point in a general direction for further investigation, but is also often used to reinforce biases
Satelite Data
School teams ins this category explore an existing problem of practice through student perspectives and other relevant data, design and test a prototype of a change idea through multiple inquiry cycles; and document and share practices developed through inquiry cycles
Eskolta Pilot
The evidence we collect to demonstrate whether we are impacting our drivers to move towards our aim
Driver Measure