Usability Analysis Report

Test Plan:
Scope- To test how well our set of instructions explain the process of inserting Headers and Footers into
a Microsoft Word document.
Purpose- To evaluate how clear the instructions are and if the user will be able to use them without
running into any trouble. We also want to evaluate how easy each user says the instructions are to follow.
Equipment- A computer with the set of instructions saved on it. Example files and images to insert.
Participants- Anyone using Microsoft Word 2013.
Scenarios- Instructions contain two tasks. Inserting a desired Header and inserting a desired Footer.
Metrics (Background question) - Participants will be asked how easy the instructions were to follow
along with.
Roles- Participants will go through the instructions and group members will observe the participant and
see if they have any issues or questions.

Usability Report:
Our first user only made a simple request that we make a change in the wording that we used. We
originally had the instruction listed as Delete header/footer. However, when working in Microsoft word,
the button the user needs to click actually says Remove header/footer. We assumed that the wording
would be easy enough to understand, but decided we needed to change it to the exact text the user
would see.
Our second user did not run into any issues and added that the document was very concise and well
formatted.
Our third user only had one issue and it was when the instructions read insert desired text. He thought it
was something he had to click on instead of it just telling him that he had to type whatever he wanted it to
say. He explained this to him and he noted it was a silly mistake, so we made no changes to the text.
Our fourth user made a suggestion that we should include a note that says if the text is already
highlighted, there is no need to double click and you can just start typing. He also pointed out the problem
our first user noticed where it said Remove instead of Delete footer. He also ran into this issue
because we did not fix the issue until all usability testing was completed.