CIRCA:Feedback

From CIRCA

(Difference between revisions)
Jump to: navigation, search
(Created page with 'Feedback is '''Rationale''': '''Questionnaire''': *7.1 What feedback do you and your stakeholders want and from who? *7.2 How does the game work for players? What is their ex…')
 
(One intermediate revision not shown)
Line 1: Line 1:
-
Feedback is
+
Feedback is feedback and responses.
-
'''Rationale''':
+
'''Rationale''':  
 +
Arguably one of the most important steps, Feedback identifies what sort of responses parties want and how to handle that feedback. Feedback is important because it identifies how the project has been received, what should be implemented in further and immediate modifications, and if your project is even getting the feedback its looking for. Furthermore, Feedback may also highlight unexpected elements that were missed during the design process.
 +
 
 +
Feedback is extremely useful at any point of the game design process. For example, though you may think your interface is perfectly functional, once its released players may find flaws with it. Feedback allows you to adapt your project to accommodate.
'''Questionnaire''':  
'''Questionnaire''':  
Line 15: Line 18:
'''[[CIRCA: Assessment Tools | Recommended Methods]] ''':
'''[[CIRCA: Assessment Tools | Recommended Methods]] ''':
 +
*AB Testing: If you have alternative designs, AB Testing is a quick way to get feedback regarding which version users prefer.
 +
*Feature Testing: Feature testing controls users' exposure to specific features or concepts, allowing you to test features/concepts against each other. This allows you to test features one at a time, while also seeing whether it will work for the users in the final version when all the features are available.
 +
*Interviewing:
 +
*Play-Testing:
 +
*Talk-Aloud:
 +
*Usability Testing:

Current revision as of 21:00, 25 November 2013

Feedback is feedback and responses.

Rationale: Arguably one of the most important steps, Feedback identifies what sort of responses parties want and how to handle that feedback. Feedback is important because it identifies how the project has been received, what should be implemented in further and immediate modifications, and if your project is even getting the feedback its looking for. Furthermore, Feedback may also highlight unexpected elements that were missed during the design process.

Feedback is extremely useful at any point of the game design process. For example, though you may think your interface is perfectly functional, once its released players may find flaws with it. Feedback allows you to adapt your project to accommodate.

Questionnaire:

  • 7.1 What feedback do you and your stakeholders want and from who?
  • 7.2 How does the game work for players? What is their experience?
  • 7.3 How will reports from the players or other stakeholders be handled?
  • 7.4 Can we provide feedback to encourage player engagement with the game?
  • 7.5 How can feedback influence further design?

Recommended Methods :

  • AB Testing: If you have alternative designs, AB Testing is a quick way to get feedback regarding which version users prefer.
  • Feature Testing: Feature testing controls users' exposure to specific features or concepts, allowing you to test features/concepts against each other. This allows you to test features one at a time, while also seeing whether it will work for the users in the final version when all the features are available.
  • Interviewing:
  • Play-Testing:
  • Talk-Aloud:
  • Usability Testing:
Personal tools