meta data for this page
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
goals [2019/08/08 13:56] lisa.illgen_concentrix.com Added Anchor Links |
goals [2019/08/09 10:28] (current) lisa.illgen_concentrix.com Added missed Anchor Link |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| - Search the published scientific or marketing research for relevant information. | - Search the published scientific or marketing research for relevant information. | ||
| - Use task modeling such as GOMS or KLM to estimate expert task-time performance ([[references#sauro2009|Sauro, 2009]]). | - Use task modeling such as GOMS or KLM to estimate expert task-time performance ([[references#sauro2009|Sauro, 2009]]). | ||
| - | - Negotiate criteria with the stakeholders who are responsible for the product. Ideally, the goals should have an objective basis and shared acceptance among stakeholders such as marketing and development (Lewis, 1982). The best objective basis for measurement goals are data from previous usability studies of predecessor or competitive products. For maximum generalizability, the source of historical data should be studies of similar types of participants completing the same tasks under the same conditions ([[references#chapanis|Chapanis, 1988]]). If this type of information is not available (or really, even if it is), it is important for test designers to recommend objective goals and to negotiate with the other stakeholders for the final set of shared goals. | + | - Negotiate criteria with the stakeholders who are responsible for the product. Ideally, the goals should have an objective basis and shared acceptance among stakeholders such as marketing and development ([[references#lewis1982|Lewis, 1982]]). The best objective basis for measurement goals are data from previous usability studies of predecessor or competitive products. For maximum generalizability, the source of historical data should be studies of similar types of participants completing the same tasks under the same conditions ([[references#chapanis|Chapanis, 1988]]). If this type of information is not available (or really, even if it is), it is important for test designers to recommend objective goals and to negotiate with the other stakeholders for the final set of shared goals. |
| Whatever approach you take, don’t let analysis paralysis prevent you from specifying goals. “Defining usability objectives (and standards) isn’t easy, especially when you’re beginning a usability program. However, you’re not restricted to the first objective you set. The important thing is to establish some specific objectives immediately, so that you can measure improvement. If the objectives turn out to be unrealistic or inappropriate, you can revise them” ([[references#rosenbaum|Rosenbaum, 1989]], p. 211). If you find yourself needing to make these types of revisions, try to make them in the early stages of gaining experience and taking initial measurements with a product. Do not change reasonable goals to accommodate an unusable product. | Whatever approach you take, don’t let analysis paralysis prevent you from specifying goals. “Defining usability objectives (and standards) isn’t easy, especially when you’re beginning a usability program. However, you’re not restricted to the first objective you set. The important thing is to establish some specific objectives immediately, so that you can measure improvement. If the objectives turn out to be unrealistic or inappropriate, you can revise them” ([[references#rosenbaum|Rosenbaum, 1989]], p. 211). If you find yourself needing to make these types of revisions, try to make them in the early stages of gaining experience and taking initial measurements with a product. Do not change reasonable goals to accommodate an unusable product. | ||