One of the biggest challenges I ran into as president of the BYU Country Swing Club was helping more than 50 volunteers teach moves consistently.
People wanted to learn a lot of different moves. Our instructors had different experience levels, and move names were not always consistent. Someone might know a move by one name while another person called it something else. If I was at club, I could often help sort out what people meant. But what happened when I was not there?
Showing a move helps in the moment
The simplest answer was to show people the move. Demonstration is important in dance. You need to see how a move is supposed to look, and you need to practice it with a partner. But a demonstration can be hard to remember after the lesson ends. It also does not answer every question a volunteer might have later.
We needed a resource people could return to: somewhere to look up a move, agree on what we were calling it, and learn it without needing to find one particular person. That would give volunteers more confidence and make it easier for dancers to keep learning outside of a single class.
From scattered knowledge to a shared resource
I started building a move and line dance database. At first, it was an internal tool for keeping names and information organized. As I worked on it, I realized that having a list of names was not enough. The tutorials were not all there, and a name by itself does not teach someone how to dance a move.
So the resource grew. We added tutorials and made the collection public, starting with the moves and line dances we taught at BYU. The goal was to make the material useful to the volunteers teaching and the dancers learning from them.
What I learned
Teaching a large group of volunteers is not just a matter of finding someone who knows the material. People also need a shared reference, clear names, and a way to review what they are teaching. That does not replace a good instructor or time on the dance floor. It gives both instructors and dancers something to build on.
The move library came from a practical question: how can we help volunteers teach what people want to learn, even when I am not standing there to answer questions? Building a resource around that question made the club's knowledge easier to share.
Keep reading
The King Lab: Week 4 - Security, Structure, and Slowing Down
Securing the CMS, defining the 'Big Three' techniques, and the reality of maintaining momentum during the holidays.
The King Lab: Week 3
Defining Roles & The Theory of Connection
The King Lab: Week 2
Securing the platform, gamifying the curriculum, and a look at managing 1300+ dancers.