On this page:
Invision prototypes
In the last stage, our designers set up Invision prototypes to create high-fidelity clickable prototypes. We then used these interactive prototypes for user testing.
High level results
While the results and user feedback certainly showed the subjective nature of web design (and even information architecture) there were some clear patterns. For example, while we had one subject who strongly preferred the second homepage design, our other seven users strongly preferred the first one. This gave us a clear case for choosing the first homepage design with some minor alterations.
We also discovered that the menu name of ‘Giveback’ was still not clear for users (we’d originally had this titled ‘Community’, then changed to ‘Giveback’). Based on user feedback, we elected the new menu item of ‘Contributions’.
Under the facilitation of our UX consultant Tina , we discussed the user testing and feedback and drafted ‘agreements’ based on the user testing. These could then be implemented for the next round of designs or parked for later consideration.
The agreements
Drafting agreements based on the user testing feedback helped keep us focused on moving the project forward and iterating to improve the designs, and other elements such as the IA. For this situation, we simply used a Google doc to capture the agreements. Here are some of our agreements with notes that show how this has been reached from the user testing:
Agreement: Change top nav from ‘Giveback’ to ‘Contributions’ (based on feedback on the current menu item and the user suggestion of ‘Contributions’).
Agreement: Will use Homepage 1 design and content wording as the basis for the final homepage.
Agreement: Will replace journey links for homepage 1 with journey links from homepage 2. (Most users really liked the ‘journey links’ on the second homepage.)
Agreement: Need to finalise order of sections/cards on homepage, but projects and services need to be up the top and staff lower down. (Users all nominated projects/our work and services as the highest priority items from our visual tiles/cards.)
Agreement: Will look at alternate layout for Services page, with vertical listing rather than three tiles across. (Users found our search filters confusing and complicated.)
Agreement: Staff listing page - display alphabetically. (While a couple of users had a preference for management first, most users preferred the flatter structure of alphabetical listing and it’s more in line with Salsa’s values.)
Agreement: Will keep avatars on Team page and keep photo on profile page (as per prototype)
Agreement: Need new content template for all staff profile pages. (Based on the information that users wanted to see about the staff member.)
Next steps
With the user testing results in and agreements finalised, the next step is to action the agreements and iterate the designs. We also need to turn our attention to the content strategy. This includes drafting a formal content strategy that will be informed by a content workshop.
