Testing 1… 2… 3…
Design Cycle
Engaging with youth
People & teams
Knowledge Management
100

Shifts in practices that are intended to re-engage students


Change Idea
100

The 4-step process for iteratively testing ideas that is embedded within the Eskolta Design Cycle

PDSA Cycle

100


A group of students at Eskolta that provide advice to network leadership


Youth Advisory Board (YAB)

100

A group of people working together to move the needle on a specified aim 


NIC

100

This space provides coaches with an opportunity to share what’s working with their teams, strategies impacting students and modifications to change ideas

Consolidation

200

Data that helps us know whether or not a change idea is possible 


Feasibility Data

200


The articulation of the specific area your team is trying to improve


Problem of Practice

200

A form of independent, critical research led by youth

Youth Participatory Action Research (YPAR)

200

This group is responsible for  coordinating school-team learning, identifying promising ideas and practices, and sharing that learning between schools in our Network

Hub

200

These evidence based strategies for youth re-engagement can be shared with both internal and external audiences

Knowledge Products

300


Data that indicates whether or not a team is testing a change idea as intended


Fidelity data

300

The umbrella term for  methods for improving complex systems that involves testing ideas over time

Continuous Improvement

300


Information and learning that emerges from direct human interaction


Street Data

300

This group of people engage in 8-10 collaborative training sessions and monthly coaching calls

Eskolta Fellows

300

These touchpoints in the design cycle are when coaches fill out their field reflection slides

Data Share Moments

400


A low-lift way to collect data to gauge the impact of a change idea 


Embedded Measure

400

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

400

Information at a medium grain size that can help us identify patterns across a class or school aka GPS data

Map Data

400

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

400

These step-by-step instructions outline the most evidence-back strategies in our Network

Change Packets

500

Eskolta’s term for a graphic organizer or protocol to capture the testing of a PDSA cycle

Inquiry Record

500

A description of a series of actions or events we believe will lead to a desired outcome

Theory of Change

500

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

500

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

500

The evidence we collect to demonstrate whether we are impacting our drivers to move towards our aim

Driver Measure