...

• Editing on resume desired (does not want to have to go back to the first page to edit content)
  • Severity - Cosmetic
  • Solution - Text on resume could be editable
• Wizard look confusing (unsure if after “Save and Continue is clicked, one can return to that step in the process or not”)
  • Severity - Cosmetic
  • Solution - Remove numbers from each step (1, 2, and 3)
• “Resume Name” not seen (user clicked “Save Resume” without seeing naming possibility)
  • Severity - Cosmetic
• Solution - Do not let user “Save Resume” if “Resume Name” textbox is empty
  • “It’s so fast”
  • Good
• “I really like that it formats for you”
  • Good

Reflection

During this process, our group learned many different things. Firstly, we learned that multiple stages of testing before the product is even build can allow you to solve many of the issues that arise. All three of us have worked on multiple projects where we have made design documents, built a product, and tested and iterated. By that time, we were often reluctant to make drastic changes. But because we spent a lot of time building the product before we actually build it, we had already made a lot of the drastic changes we would have had to make, just before we had invested a lot of time and resources instead of after.

Also, thinking about the UI the whole time made us have a better product than we otherwise may have. In other projects, we have often started by building an acceptable UI, just so we could get a working project. The problem was, once we had a working product we found it very difficult to revamp the UI because we were already thinking that the UI would look something like what was already there.

...