UX Design - Task 1: UX Audit
21 Apr 2025 - 16 May 2025 (Week 1 - Week 4)
Data was collected through in-depth interviews with three university students,
all of whom primarily commute by driving to Taylor's University.
Vincent Lee // 0359386
UX Design // Bachelor of Design (Hons) in Creative Media // Taylor's
University
Task 1: UX Audit
INDEX
Task 1(a): UX Audit
Task 1(b): User Research (Interview)
Instructions
MIB
<iframe
src="https://drive.google.com/file/d/1rgJw-kz3JflGH9Gupzo7ZHW9mu_jM3Nx/preview"
width="640" height="480" allow="autoplay"></iframe>
Task 1(a) Criteria
<iframe
src="https://drive.google.com/file/d/1gXD4NudwhFBs2HqlR8mlGiiAwAwB-CeI/preview"
width="640" height="480" allow="autoplay"></iframe>
Task 1(b) Criteria
<iframe
src="https://drive.google.com/file/d/1T9eV567WbeZ4eKoHo29KXOYGbnMZYzN0/preview"
width="640" height="480" allow="autoplay"></iframe>
Task 1(a): UX Audit
We'll prepare content based on the given topic and evaluate the overall website
or mobile application by analysing its UI/UX elements, then perform a UX audit
accordingly.
- Comprehensive Libedex Website Analysis [Link]
- Task 1(a): UX Audit Submission [Link]
Figure 1.1 - Task 1: UX Audit, Week 3 (05 May 2025)
Task 1(b): User Research (Interview)
We must conduct at least 2 user interviews to gather primary data based
on our chosen topic. This research will help define target users and develop
user personas.
Drafting Interview Questions
|
| Figure 1.3 - Constructing of Interview Questions, Week 2 (28 Apr 2025) |
By completing the User Research Document, we were able to align our
understanding of the project's purpose and goals, which helped us stay
focused and collect more relevant data effectively.
|
| Figure 1.4 - Consolidating User Research Document, Week 3 (05 May 2025) |
The interview questions, along with the User Research Document, were
shared with Dr. Wong to review the overall structure and ensure our
approach aligned with the project objectives.
|
| Figure 1.5 - Feedback_Draft Interview Questions [Link], Week 3 (08 May 2025) |
Interviews and Transcripts
The interview questions were refined then finalised after Dr. Wong’s
feedback, and we quickly proceeded to carry out the interview process.
Figure 1.6 - Finalised Interview Questions, Week 3 (08 May 2025)
- Interviews Audio and Transcript Folder [Link]
- add the explanation of our projects, and try to find the patterns
between the interviewees
- need to organise our Figma more nicely
Figure 1.7 - Interviews Transcript, Week 4 (13 May 2025)
Affinity Map and User Research Synthesis Finding
Figure 1.8, the data were then clustered into groups based on
similarities and relevance.
Figure 1.10 presents a summary of the data, divided into four
categories: user demographics, preferred transport methods, commuting
frustrations, and improvement suggestions. Each category highlights key
insights gathered from the interviews to support further analysis and
solution development.
|
| Figure 1.8 - [Individual] Affinity Map_User Interview Data, Week 4 (13 May 2025) |
Figure 1.9 presents the grouped user interview data, clustered under
specific titles for further extraction, analysis, and comparison.
|
|
|
|
| Figure 1.10 - User Research Synthesis Finding, Week 4 (14 May 2025) |
Task 1 Submission
 | |
|
Figure 1.12 - User Research Document, Week 4 (14 May 2025)
Figure 1.13 - Group Progressive Presentation Slides, Week 4 (14 May
2025)
Feedback
Week 2 - UX Audit
The category of the website or mobile application doesn't matter. As
long as it's a website or mobile application, I can proceed with
completing it.
Week 3 - Interview Questions
It’s good that we have a general idea of the final features for our
app, but this shouldn't limit what the final outcome could be. The
purpose of conducting interviews is to uncover the real pain points
of the users, and from there, we should brainstorm solutions that
still align with our overall theme, mobility within Taylor’s.
However, the current interview questions seem to lead the interviewees toward our already-decided solution: the shuttle bus app. This approach may unintentionally restrict our ability to explore other valuable directions or problems that users actually face. It’s important to keep the interviews open-ended so we can gather genuine insights rather than validate a predetermined idea.
Additionally, since neither Yuu nor I use the Taylor’s shuttle bus service ourselves, it might be challenging for us to frame relevant and unbiased questions, or to fully understand the users' experience. We should also consider that shuttle bus issues often stem from broader problems like traffic congestion and campus exit points, things that may go beyond the scope of just a bus-tracking solution.
However, the current interview questions seem to lead the interviewees toward our already-decided solution: the shuttle bus app. This approach may unintentionally restrict our ability to explore other valuable directions or problems that users actually face. It’s important to keep the interviews open-ended so we can gather genuine insights rather than validate a predetermined idea.
Additionally, since neither Yuu nor I use the Taylor’s shuttle bus service ourselves, it might be challenging for us to frame relevant and unbiased questions, or to fully understand the users' experience. We should also consider that shuttle bus issues often stem from broader problems like traffic congestion and campus exit points, things that may go beyond the scope of just a bus-tracking solution.
Week 4
- need to organise our Figma more nicely
- still need to work on the affinity diagram first
Reflection
Week 1
It’s been a while since I’ve been back to studying, but the warm-up
and classroom atmosphere really made me feel better and lighter (not
as bad as I initially thought). For this task, I decided to work on a
website design because I’ve done quite a bit of application design,
and since I’ve already completed Application Design 1 and 2, I thought
this would be a good time to switch things up. The topic I chose might
seem a bit kinky and revealing, but I wanted to make progress rather
than doing nothing in the first week. It was a bit hard to take the
first step (I'm a severe procrastinator), but I pushed through and did
it anyway. I hope to receive good feedback next week, and by then, I
plan to continue by redesigning the UI and UX with sketches and
references, then compiling everything into a document and PDF file.
Week 2 - UX Audit
The work was easy to complete, but it still took me some time
because I struggled with how to summarize my findings and present
the data. Additionally, exporting and converting files to images for
uploading to Canva made the process less flexible. I initially used
my tablet to point out issues and provide redesign suggestions, but
moving to Canva required me to redo some parts and cut down the
text. Overall, it was a great experience conducting this research,
especially with the assistance of ChatGPT to help with wording
issues. It also helped me better understand what constitutes good
design (I used examples I like and that I believe are really good),
and the knowledge (UIUX terms and design wise) I gained will be
helpful in the future if I’m tasked with something similar again.
Week 3 - Interview Questions
The process of creating our interview questions was relatively fast and smooth, as we all shared similar views on traffic congestion during peak hours. After further discussion, we decided to narrow our focus to bus commuting issues within Taylor’s. I’ve experienced this first-hand, Arnusha is a frequent user of the shuttle service, and although Yuu drives to campus, he also faces traffic congestion.
Following our consultation, we held a second meeting to revise our interview questions based on the feedback received. We aligned them with the problem statement and target audience, with the plan to first present them to Dr. Wong before proceeding with the interviews and completing the task requirements.
Using a script felt a bit rigid and awkward, especially when interviewing friends, but I recognize its importance as a framework for collecting consistent data, both for the group’s qualitative findings and for any future quantitative analysis.
After reviewing the provided materials, I realized that an affinity diagram might be particularly helpful for our case. The range of responses and the complexity of the issues shared by users suggest that visual grouping and theme identification would support a deeper understanding of patterns that might not be obvious at first glance.
Overall, this session not only offered valuable user insights but also helped me grow in managing conversations, refining question delivery, and thinking more structurally about data analysis.
The process of creating our interview questions was relatively fast and smooth, as we all shared similar views on traffic congestion during peak hours. After further discussion, we decided to narrow our focus to bus commuting issues within Taylor’s. I’ve experienced this first-hand, Arnusha is a frequent user of the shuttle service, and although Yuu drives to campus, he also faces traffic congestion.
Following our consultation, we held a second meeting to revise our interview questions based on the feedback received. We aligned them with the problem statement and target audience, with the plan to first present them to Dr. Wong before proceeding with the interviews and completing the task requirements.
Reflection on User Interviews
Conducting the user interviews gave me a clearer understanding of
both the users’ commuting experiences and my own role as an
interviewer. One challenge I faced was keeping the conversation on
track, as interviewees often drifted off-topic. I tried not to
interrupt them to maintain a natural flow, but occasionally had to
rephrase questions to guide them back. This made me more aware of
the balance between structured questioning and allowing space for
organic insights.Using a script felt a bit rigid and awkward, especially when interviewing friends, but I recognize its importance as a framework for collecting consistent data, both for the group’s qualitative findings and for any future quantitative analysis.
After reviewing the provided materials, I realized that an affinity diagram might be particularly helpful for our case. The range of responses and the complexity of the issues shared by users suggest that visual grouping and theme identification would support a deeper understanding of patterns that might not be obvious at first glance.
Overall, this session not only offered valuable user insights but also helped me grow in managing conversations, refining question delivery, and thinking more structurally about data analysis.
Week 4
It sounded complicated at first, but once we started working on it,
it didn’t feel that way. I think it’s because everyone contributed
and handled their part well, so even during the interviews and
creating the affinity map, the execution felt smooth. However, the
feedback given seemed a bit vague. Anyway, we’ve submitted Task 1
for now. What needed to be done is done, and I’m happy and grateful.
Additional Reading:
Affinity Diagramming for Collaboratively Sorting UX Findings and
Design Ideas
Affinity Diagram and Card Sorting
Quick Links
Task 1:
UX Audit
Task 2:
User Personas & Empathy Map
Task 3: User Journey Map & Ideation
Final Project: Prototype & Concept Training
