<Insert logo here>

Application       <Insert detail here>

Owners              <Insert detail here>

Date                    <Insert detail here>

Activity               Heuristic Evaluation       

Usability Testing            

Consultants     <Insert detail here>       

Participants	Role	System experience	No system experience
<Insert detail here>
	TOTAL

Executive summary

<Insert detail here>

Purpose of Study

<Insert detail here>

Method

<Insert detail here>

Participants

<Insert detail here>

Procedures

<Insert detail here>

Tasks

<Insert detail here>

Results

The results of the study have been divided into three sections:

1. Task performance (e.g. successes and failures)
2. Observations and recommendations
3. Post-test satisfaction ratings and comments

	Task	Success  Success    Failure Easy Difficult
1	<Insert tasks here>	<Insert performance outcomes here>
2
3
4
5
6
7
8
9
10
11
12

The following table presents the observations, interpretations, and recommendations for redesign. These data are organized into two major categories loosely based on a usability problem taxonomy [1]:

• Task Problems include those problems related to the effective mapping and facilitation of tasks by the system (e.g. navigation, process flow).
• Artifact Problems include those usability problems associated with individual interface objects (e.g. visual design, language, interactions with screen objects).

<Insert category here>
<Insert observations here>	<Insert interpretations here>	1. <Insert recommendations here>
		2. .
		3.
<Insert category here>
<Insert observations here>	<Insert interpretations here>	4. <Insert recommendations here>
		5.
		6.
<Insert category here>
<Insert observations here>	<Insert interpretations here>	7. <Insert recommendations here>
		8.
		9.
<Insert category here>
<Insert observations here>	<Insert interpretations here>	10. <Insert recommendations here>
		11.
		12.
<Insert category here>
<Insert observations here>	<Insert interpretations here>	13. <Insert recommendations here>
		14.
		15.

Conclusion

<Insert detail here>

<Insert screen shot here>	Screen 1: <Insert detail here, visually identify and verbally describe the problem>
<Insert screen shot here>	Screen 2: <Insert detail here, visually identify and verbally describe the problem>
<Insert screen shot here>	Screen 3: <Insert detail here, visually identify and verbally describe the problem>
<Insert screen shot here>	Screen 4: <Insert detail here, visually identify and verbally describe the problem>

 Post-Test Satisfaction Ratings

<Insert category here>	<Insert scale here>	<Insert scores here>	<Insert median here>
<Insert satisfactions questions here>	<Insert anchors here>
<Insert satisfactions questions here>	<Insert anchors here>
<Insert category here>
<Insert satisfactions questions here>	<Insert anchors here>
<Insert satisfactions questions here>	<Insert anchors here>
<Insert category here>
<Insert satisfactions questions here>	<Insert anchors here>
<Insert satisfactions questions here>	<Insert anchors here>
<Insert category here>
<Insert satisfactions questions here>	<Insert anchors here>
<Insert satisfactions questions here>	<Insert anchors here>

Post-Test Satisfaction Ratings

<Insert satisfaction question here>

<Insert user comments>

<Insert satisfaction question here>

<Insert user comments>

<Insert satisfaction question here>

<Insert user comments>

<Insert satisfaction question here>

<Insert user comments>

<Insert satisfaction question here>

<Insert user comments>

<Insert satisfaction question here>

<Insert user comments>

<Insert satisfaction question here>

<Insert user comments>

<Insert satisfaction question here>

<Insert user comments>

---

[1] Keenan, S.L., Usability Problem Taxonomy