Exercise: board game teaching practice

This is the details of the gaming exercise in Teacher.

I (rkdarst) think there is a lot of analogies to teaching games and teaching technology. Both are complex systems with many interlocking parts, and it can seem hard to get started until you know everything. Both have many abstraction layers that connect together and you can easily overwhelm the learner. Yet, somehow things must be linearized for teaching. In this exercise, we will have some fun playing board games while reflecting on our teaching.

The task / instructions

  1. Choose board games and divide into groups appropriate for the games. In each group, there should be one (or possibly two) people who knows the game, and it’s new to the rest (this is flexible).

  2. The teachers teach others the game. The learners pay close attention to the way the game is being taught (perhaps taking notes; without interrupting the teaching too much). Learners can also read the list below to see what to look for.

    Special notes:

    • Manage time well and decide the proper level of detail. Don’t get stuck on small things.

  3. When time is up, everyone discusses how the explanation went (use the evaluation rubric from the last section on this page):

    • What went well and didn’t go well?

    • How would you improve it next time?

    • Also use the opportunity to practice constructive criticism - find a way to say what you think nicely but directly, even if it’s not comfortable.

  4. Discuss how this applies to us teaching technology to others.

    • Did you feel overwhelmed?

    • Do you think some of our customers/garage visitors feel like you felt?

    • How do we avoid the feeling of being overwhelmed?

Preparation by the game teachers

This must be done at least a few hours in advance.

Game learners: You may watch/read the things above, but you don’t need to. You can browse the table below to see a summary.

Game teachers: Read the evaluation checklist below, or How to teach board games like a pro. Optionally, watch the CodeRefinery teaching motivation version (or read it). Take a game you have and prepare to teach it, using the best practices from this information.

The teachers should make a teaching plan in accordance with the lessons in the info (Not too detailed, but some notes on how you linearize the process). You do not have to teach the whole game or do a complete play-through - for example, try to teach what you can in 30 minutes, and have 15 minutes for discussion. Treat it is our SciComp teaching: you don’t have time to teach the full topic, but you can probably get someone started and interested. (Look at the schedule to see how much teaching time you have, and adjust to that.)

Teaching strategy reference

The left column is from the video (things in parentheses are my additions), the middle column is a connection to SciComp teaching.

Points from the game-teaching video

Analogy to teaching technology

Comments

(Know your audience)

<– same

Different audiences need different things taught.

Know the game well enough to teach it. Know what not to teach for the first round.

For tech, also know what not to teach - not everyone needs to know the same things.

Let people fiddle, it isn’t a lecture.

Let people try things out themselves.

“Teach while doing”.

Before the rules: “Who, how, and why?” (the game’s theme)

Explain the big picture of what and why to give context.

People are here to do something, not learn the rules.

It’s a performance; consider rehearsing. Decide the path you will take through the rules.

Make a practice (also in the same environment as a learner would have). Decide what you do and don’t teach.

I especially try to rehearse the first five and last five minutes.

(Consider making a specific setup (not random) to demonstrate things in the order you want.)

Make a good initial setup, with good examples that are straightforward and without pitfalls.

Randomness isn’t necessary in the teaching

Always use your friends in examples. Use their names.

Use examples as specific and realistic as possible.

Make sure you encourage questions (but postpone answering until later, if it’s appropriate).

Encourage questions, but realize what is advanced and should be explained later.

It’s a fine balance between questions and derailing.

(Very careful about jargon. Example: Players see and think cubes, not diseases. I try to say the physical thing (“cube”) and in-game name (“disease”, so “disease cubes”) when explaining.)

Spread the jargon teaching throughout the explanation and give reminders when you use recently-introduced jargon.

Can you make some sort of reference card?

Employ a flight attendant (helper) and avoid multiple teachers.

Co-teachers, but one person in charge.

One captain on the ship. Decide the captain and let them handle the flow of what is taught in what order. Others support.

Careful how you play the game, too (if you win, you lose the teaching).**

You can simplify for the audience. If you teach exactly what you would do, maybe it’s too much for your learners to use anything.

Run a dummy round is necessary (trial run, reset for the real game). Dummy rounds with open information are OK.

I always do a demo first, before expecting someone else to do it alone (even if I am telling them what to type).

Nothing is as good as seeing the real thing. For example, if in garage I need someone to do something from the command line and they clearly have little experience, I will demo or screenshare before I ask them to try themselves.

(Experienced people go first. Order players from most to least experienced and try to use a round as a demo.)

^ similar

The teacher may still need to control what gets explained (and not) at what times.

The secret superpower of simple games (Start with simpler games first during a teaching session).

Make simple examples to start off.

Another instance of “teach what people need to learn, not what you would do”.

(Teaching isn’t just the lesson, it’s also mentoring during the game.)

You (or someone) needs to be around later on to mentor.

I try to start off by teaching, but I don’t need to explain everything. I fill in other aspects by mentoring or mid-game lessons. The entire first game can be the lesson, even if it makes it not a realistic game.

Evaluation checklist

There are other discussion questions in the instructions above.

Reserve enough time to feedback to the teacher based on the criteria above. Don’t practice just giving feedback, but giving constructive criticism that might be a bit uncomfortable in real life. Some of the most important points are below, also in the printable grading sheet. Then, discuss how well the feedback process worked.

Make sure you know the game well enough to teach it Different from knowing the game well - know what is important and not important to focus on.

Set up the game in advance So that you can get right to the interesting part.

Theme of the game What are we trying to do and why?

Do as much teaching as possibly while actually doing things Minimal intro, start the game, and teach the rest of the concepts while playing.

There should be one primary teacher There is co-teaching, but one person responsible for making sure time gets kept and things progress.

Make it easier Teach the game the learners will play, not the game that you will play.

Experienced people go first Don’t expect someone to do something they haven’t seen demonstrated first.

Be very careful about jargon Are you using only jargon of the game without descriptions that make sense to any gamer?

(Run through the lesson first myself) (Perhaps not relevant when there isn’t preparation time! Focus on smooth first five and last five minutes)

Mentor even after teaching is done and the game is being played