To use evidence to drive the design process, your team will test hacks, collect results, check assumptions, and generate key insights. Documenting the process with artifacts will help bring others along and communicate your team's impact. This is essential to ensuring you are pausing, reflecting, and pivoting, where necessary.
This journey has helped my instruction because the evidence is coming from our most important stakeholders: students. Their voices and perceptions should not be discounted, and asking them for input empowers them to be engaged, connected learners.
An overview of this phase's goals, activities, and desired outcomes.
Forecast the impact of hacks before they happen or uncover early indicators that things are moving in the right direction.
After your team has implemented your hacks, ask students to reflect on the change. Consider unconventional measures to encourage and collect feedback.
Facilitate a discussion to reflect on the outcomes of your team's hacks. Invite individuals to share stories and encourage feedback from the group to deepen future impact.
The activities in this phase will set you up to have multiple forms of evidence, including feedback from your peers. Your team should know if you’re on the right track towards making the change that you hope to see in your school community.
Have a question or suggestion about this phase? Share it with the Facebook Group.
Share Your ThoughtsSign up to be the first to hear about Toolkit updates and news
