|
Key Info
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Defining "Best"Once you have created a number of possible solutions to your design problem, you need to choose which one is best. RequirementsFirst, look at whether each possible solution met your design requirements. Consider solutions that did a much better job than others, and reject those that did not meet the requirements. Nice to Haves, DesirablesIn addition to your design requirements, you probably have some features that would be "nice to have" in your solution. These are things that are not quite as important as your design requirements; they are desirable, but not mandatory. Some of your possible solutions might include more of these nice-to-have features than others, and that is a possible reason they might be better. Universal Design CriteriaSome criteria apply to virtually every design. Good designers consider them in every solution that they choose to implement.
The Decision MatrixAs you compare potential solutions to your design brief and the universal criteria for a good design, it may be obvious which solution is the best. More often than not it helps to compare the solutions in a decision matrix. A decision matrix is a chart with your requirements and criteria on one axis and the different solutions on the other. Use a simple numeric evaluation scale to rate each solution against each of the criteria (2 = totally meets the criteria, 1 = somewhat meets the criteria, 0 = does not meet the criteria). Total up the columns to see which solution is best. Alternatively, if you have colored stickers or pens, you can rate projects with a color scale (green = totally meets the criteria, yellow = somewhat meets the criteria, and red = does not meet the criteria). Using colors gives a highly visual indication of which solution is best (the more green the better!). In our example, we lump together nice-to-have, desirable features and the universal design criteria into the "Other criteria" row of the decision matrix. That way these criteria serve as a tiebreaker, but they do not out-weigh "must-have" design requirements. You can make the design matrix with as many requirement rows and solution columns as you need, as shown in the example below.
Pros and ConsIf your requirements and solutions are relatively simple, you can sometimes just list the pros and cons for each solution, as shown in the example below. Pros are good things about a solution and cons are bad things. (The terms pro and con come from the Latin phrase pro et contra, for and against, and they have been used for centuries.)
Decision Matrix WorksheetHere's a Decision Matrix Worksheet to help you choose a design. Design Solution ChecklistAnswer the questions in the quick checklist below to find out if you have made a good design choice.
|