Team Ludo WUX App Design - Monday Meeting 22th August 2022

Date: 22nd August 2022

At this meeting we covered the following points:

Anjileen, Beste and I each contributed options for a name, which I used to populate a survey asking the user which of the options they liked and felt suited the application best.
I distributed this survey among the Web and User Experience Design Diploma student body, and asked my teammates to distribute it further, to friends and family.
Our options are as follows:

Anjileen and I have so far created one set of wireframes each, for each page our application will have.
Because of our differing approach, we decided that we will each use our wireframes to build a set of mockups, based off our own wireframes. These will then be used to conduct A/B testing to judge which layout performs best.
These will be constructed in Adobe XD, with no coding performed at this stage.
Adobe XD was chosen for compatibility reasons, as Figma (an application that serves the same purpose) cannot run reliably on Anjileen and Beste's computers.
The most effective mockup will then be used as a base to add functionality and behaviour when building the prototypes (essentially, interactive mockups).

As mentioned, A/B testing will be conducted after the mockups are built. This will assess qualitative data, such as whether the user likes the layout and aesthetic of the mockups presented to them, if they look and feel coherent, and if they fit with the overall aim of the application.
A version of the most effective mockup with behaviour and interactive elements added - in short, a prototype - will then be generated based off of the feedback given.
Minor adjustments to layout and visual elements will be performed throughout the design process, so the final product may not match initial, planned screens.
When a prototype is available, I will conduct in-person interviews as part of the testing process, and follow up with testees when adjustments are made, to perform successive testing and gather more qualitative data.
As before, A/B testing will also be performed using the prototype to assess functionality (quantitative data).
When testing using the prototype, users will be asked to perform a list of tasks, both sequentially (a chain of consecutive tasks) and serially (individual tasks performed one-by-one).
Anjileen and I will be responsible for collecting test data; Beste will be responsible for creating a Test Plan that outlines what tasks users will perform in order to assess which features, elements or pages.

Beste noted that our documentation needs to be more consistent and meaningful, suggesting that we create a timeline of tasks we need to complete, with an expected and actual completion date attached to each. This will be maintained by all members of the team, in addition to the Trello board currently in use to track tasks.