Formative Evaluation of Mechanics

Posted by Jere on May 2, 2006 at 12:04 PM

Neel had asked what sort of formative evaluation I recommend for mechanics. Here’s the process I tend to try to follow.

Design review is alwyas important. Basically this whole flow is the subprocess under Formative Evaluation”. Design review is always important. We’ve gone and developed a set of objectives for the game, defining them in the campaign design document. With these we know what we want the game to do. Each new mechanic should be evaluated against this for appropriateness. If it passes the test than you’re ready to test it.

Testing the mechanic is as serious or as light as you deem appropriate. Some mechanics (or systems of mechanics) require significant testing. Others just need a light sanity test. Basically what you’re looking for is compliance of the delivered mechanic to the requirement its supposed to meet.

Review the performance and make the decision of “Does this Mechanic meet our objective.” If it doesn’t, or does it not quite exactly, revise the mechanic and do it again. If it does than document the mechanic. Writing something down is the best way to ensure everyone is on the same page. Never under estimate the ability of the written word to help dispel confusion and make sure everyone is on the same.

Then introduce the mechanic into play. Watch its performance; make sure its getting the desired results in a reproducible period of time. This is really summative evaluation (i.e. actual play). If a mechanic strays outside of the acceptance criteria for the objective than begin the mechanic development process again.

Repeat as necessary.