The single most important thing to focus on, is figuring out the right difficulty and the right music categories for your quiz.
If too easy, the experienced participants will get it all right and not find it challenging enough.
If too difficult, participants with less knowledge about music will quickly lose interest and give up.
So, before you start, you should figure out how experienced the players are.
If not possible, you should probably go for an easy quiz where the audience can at least recognize most of the music as this will generally, please the most.
If you have reached the right level of difficulty, the winning team will probably have about 90-95% correct answers, and the lowest ranking team will have maybe 25-50% correct.
Some people love 80's music, and some love the new hits from the last 5 years, typically depending on the age of the audience.
So, if your audience is of mixed age/interest, be sure to include music from different categories.
If you're doing a 30-minute quiz with e.g. 15 songs, you should alternate between songs from different categories (e.g. pop / rock / 80's / new hits etc.), so people don't get discouraged.
If you are running a 3-hour quiz for an experienced audience, you could have multiple rounds with different themes where different teams get to shine.
Using teamquiz.dk you can easily build e.g. 3 rounds each with a different theme so you can announce a winner of each round, as well as an overall winner across all rounds.
The easiest way to build the rounds quickly, is to create a playlist for each round in Spotify, and then import the songs into teamquiz.dk with a few clicks.
The songs artist(s) and title will automatically be imported as two questions, but you can easily edit or remove what you prefer afterwards.
The duration of the quiz is also important and again depending on your audience.
If you're entertaining mixed guests at a birthday party or colleagues at the Friday bar, you should probably not use more than 30-60 minutes to avoid killing the party for those who dislike quizzes.
On the other hand, if you're a professional quizmaster and your audience is attending only for the quiz, you can plan for several hours without problems.
For teams that are not music experts, using multiple choice is often a good choice, but if you have more experienced teams in the audience, they will enjoy the extra difficulty of not having predefined choices, but having to remember and type the artist names, song titles etc. in free text.
Using teamquiz.dk
you can do a combination of both multiple choice and free text answers with up to 4 questions per song-clip,
as shown in below example with 3 free-text questions for artist, title and lead singer and 1 multiple choice field
for the release year:
When allowing free text answers, there will be spelling errors and/or small typing mistakes from the teams.
teamquiz.dk features an intelligent semi-automatic correction system that will help you.
Correctly spelled answers are of course automatically verified by the system, but many spelling errors are also verified automatically, e.g. a tricky artist
like "Eurythmics" will also be auto corrected if spelled "Eurothmichs", "Eurithmix" or "Eurythmix".
This means the quizmaster will not have to spend a lot of time correcting the responses as the system will typically auto correct most of them.
Below is a sample screenshot from the live verification page where 27 teams are listening to and guessing the song "Prisoner" by Miley Cyrus & Dua Lipa.
The responses are color encoded in the following way:
- Green responses are either 100% correct or too far from the right answer (<50% overlapping characters)
- Blue responses "sound" correct e.g. "Miley Cirus" so is also considered correct
- Red responses requires verification from the quizmaster as it's close (>50% overlapping characters), but not quite right.
As you can see in the image, there are just 3 red entries requiring manual verification by the quizmaster, the rest is done automatically by the system so the quizmaster has time to interact with the teams as well.
