{"id":220,"date":"2023-04-03T20:11:55","date_gmt":"2023-04-03T20:11:55","guid":{"rendered":"https:\/\/projects.etc.cmu.edu\/disco\/?p=220"},"modified":"2023-04-17T00:18:44","modified_gmt":"2023-04-17T00:18:44","slug":"week-10-playtest-day","status":"publish","type":"post","link":"https:\/\/projects.etc.cmu.edu\/disco\/week-10-playtest-day\/","title":{"rendered":"[Week 10] Playtest Day"},"content":{"rendered":"\n

In this week, we have the BIG EVENT on Saturday, which is the Playtest Day! <\/p>\n\n\n\n

Since it’s such a big event, and we can gain a lot of useful feedback, data and materials for us to evaluate the function of the current product, and improve more in the future, we really desired to use this event thoroughly for further progress. <\/p>\n\n\n\n

However, we actually struggled a lot for preparing this.<\/strong><\/p>\n\n\n\n

On Monday, we tried to brainstorm some playtesting ideas based on the scenario that the tester could give real feedback to each others. So we came up with several ideas based on team role-playing.<\/p>\n\n\n\n

\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n

However, these ideas didn’t have the core function to contribute to our project. There need to be a hero focus of what we want to learn and gain in this playtest process. In the Tuesday’s meeting, Jessica gave us a series of process and schedule as a reference.<\/p>\n\n\n\n

\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n

This first image is “What is the biggest risk in Filer”, and the second image is the process of the testing schedule.<\/p>\n\n\n\n

Based on the Jessica’s schedule, Alexa (responsible for playtesting) sorted out a series of playtest day schedule, and scheduled a team meeting to discuss more details for the testing process.<\/p>\n\n\n\n

\"\"
Meeting agenda<\/figcaption><\/figure>\n\n\n\n

We created a detailed plan for the Playtest Day, based on all the UX design progress and testing goal. Then we categorized all the tags and made some combinations of high-quality feedback, low-quality feedback, and mixed ones. In addition, we split the workload of writing sample feedback of ‘drawing a bird’ to all the teammates. Finally, we finished all the contents of sample feedback cards!<\/p>\n\n\n\n

\"\"
Tag Categorization<\/figcaption><\/figure>\n\n\n\n
\"\"
Sample Feedback Cards<\/figcaption><\/figure>\n\n\n\n

We color printed all the cards out, together with the emotional wheels, scripts, backets, etc… We were confident about the playtesting and looking forward the next day – Saturday – comming!<\/p>\n\n\n\n

\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n
Playtest Day Preparation<\/figcaption><\/figure>\n\n\n\n

The Playtest Day went successfully which is over our expectation! We took lots of notes for every testers about their thinking, behaviors and categorization information. We would definitely start analyzing all the data we got and all the answers from survey to improve our product! <\/p>\n\n\n\n

\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n
Playtest Day<\/figcaption><\/figure>\n\n\n\n

Tech demo updated by our programmer – Muru:<\/p>\n\n\n\n