Chances are you’ll start Headrush with a facilitated training session or series of sessions with a member of the Headrush implementation team or respective partner. Depending on your team’s availability and desired approach, this may roll out in different ways. However, many of the resources and starting points are similar regardless. This article aims to outline the recommended approaches and resources to aid your planning.

Start > Explore > Calibrate > Repeat

Scheduling Time for Initial Training

Initial training is part of your broader implementation process, which initially may go hand in hand with each other. Even though much can be done asynchronously, there is still value in gathering as a team to go through a collective experience, coordinate process decisions, as well as collaborate on expectations for interactivity. Thus, we at Headrush typically propose the following initial training spanning anywhere from 10 - 30 days:

  1. Pre-Training Prep and Configuration Review (2+ days BEFORE actual teacher training)
    ▪︎ 1 hour session to align agenda with internal champions
    ▪︎ Clarify what is/should be loaded for learning targets
    ▪︎ If possible, get list of those who will be attending
  2. Teacher Training
    ▪︎ 2-6 hour session (depending on size of group and desire of group to work asynchronously or not)
    ▪︎ Utilize a 'Learn Headrush by Using Headrush' Module with the group to frame and Guide
    ▪︎ Clarify remaining setup and configuration tasks
  3. Post Teacher Training Q & A (1-7 days AFTER Teacher training)
    ▪︎ 1-2 hour session used to answer questions and coach the group on best practice use
    ▪︎ Often without this, gaps in implementation can unintentionally germinate.
  4. Report Review and Audit (7-30 days AFTER Teacher training)
    ▪︎ 1 hour session with internal champions
    ▪︎ Overall check in and support
    ▪︎ Discuss how reports are being used and or what changes are needed to make more useful

Example Initial Teacher Training Agenda

1) Welcome and Intro (5 mins) —

Short intros of us tied to powerful 'whys' and default to in the chat for the intros of the group, unless smaller and or suggested otherwise.

2) What are your Learning Scenarios? (10-20 mins)

Share share how the group has done things and or how the they want to do things. The goal is to here them describe what they perceived they want to manage and pickup on keywords or friction they talked about independent of Headrush. This will help us get to know them as well as avoid lecturing them for the 1st hr.

3) Get them logged in (5-15 mins)

4) Scavenger Hunt (20-40 mins)

Get the group logged into the software and in a guided way point them to the various value propositions in Headrush. Having this early additionally presents an accidental slip to get and get.

5) Start with the end in Mind (5 minutes)

Plant the seed to think about and review the reports and views needed to make life easier for your school

6) Break

7) Create a Module Yourself (30-60 mins)

First model the pieces and flow, then get them back into the system attempting to have them map out their most relatable learning scenario in the system.

8) Break

9) Initial Reactions and open Questions

Gather initial thoughts and questions from the group to both gage formative assessment of the group, leverage existing emerging champions to help out, and dictate where to next

10) Brainstorm what to populate in your warehouse and what templates you will use

As the title suggests, get the team to think about what they can front load, get them to appreciate templates. Ideally have the internal champion lead the conversation and individuals continue to create.

11) Mock up a student or two
Mock up a student or two in Headrush by creating and completing work/learning. This will help you and your team see things from the student’s eyes as well as work out some of the details in terms of framing, workflows, and onboarding.

12) Internal Champion Bookending

Summarize learnings, establish what’s next all managed within the board. Reiterate setup activities.

Learning Headrush by Using Headrush

We use an actual Headrush Module and Task Board as the centerpiece of the Headrush implementation process. This provides a real example of how Headrush can be utilized, helps project manage the overall implementation process, and points you to relevant Knowledge Center articles in a non-overhwhelming format.

Task Board:

* The file you will download can be imported via an Admin following these instructions.

Did this answer your question?