UX Design | Final Compilation & Reflection

on

24.4.2026 - 24.7.2025 (Week 1 - Week 14)
Caitlin Ong Lynn Dee / 0343801 / Bachelor of Design (Hons) in Creative Media
UX Design
Final Compilation & Reflection

INSTRUCTION



Important Link:


Week 1 (24/05/26)

From the very first week, we are tasked to form a group. We are encouraged by Mr Sylvain to have team members from different specializations. So, we can build on each other's strengths. 

Group Members:

  • Caitlin Ong Lynn Dee (0343801)
  • Chika Clarissa Widjaja (0378636)
  • Brendan Fedya (0376283)
  • Samuel Keane (0376236)

In class we are tasked to analysis on each other bag and pointed the good and the bad in with the design and drawing the improved version of the bag.

Fig 1.1 Bag Design Sketches uploaded into Teams


Week 2 (01/06/26)

*Public Holiday*

Week 3 (8/06/26)

In class we did an exercise on navigating an app on ordering nasi lemak and we had to break it down into a 2x2 matrix.

In this task we write down all of the steps needed to order nasi lemak and categorized them on high impact, low impact, high effort, low effort.

Fig 1.2 Nasi Lemak Ordering Breakdown Sketches uploaded into Teams


Week 4 (15/05/26)
For this week, we were tasked to create task analysis breakdown on the steps necessary for users to use our app. We also did our individual competitor analysis. For my part, I did an analysis on the app OpenTable. This is to make us more familiar with the competitors that are similar to our app. From this analysis, we saw a lot of similar patterns and insights that helped us on building our app.

You can see the slides here: 
https://canva.link/g97k2mfjm7gn9c7


Week 5 (22/05/26)
In week 5, we interviewed students from Taylor’s university about their eating habits and experience in Syopz. Each of us interviewed 2 people. In total, we interviewed 8 Taylorians.

These are the interview questions we asked:

  1. What do you do when you want to settle for lunch during short breaks?
  2. What usually influences your decision when choosing where to eat on campus?
  3. What specific factors affect your choice of restaurant on campus?
  4. Can you tell me about the last time you queued or ate at Syopz?
  5.  ⁠How do you feel about the current environment and overall vibe in Syopz?
  6. How long would you typically tolerate waiting while trying to find seats at Syopz?
  7.  ⁠How do you feel when you are unable to secure seats?
  8.  What do you usually do afterward when you can't find a place to sit?
  9.  Looking back at those crowded moments, what information do you wish you knew before deciding where to eat?


Week 6 (29/05/26)

After interviewing our participants, we transcript the data of our interviews and sorted it in our FigJam: https://www.figma.com/board/hzlU08VMdqf2ZVFGR3NMZB/UX-Design---QuickEase?node-id=0-1&t=o77ZPRhmxiTL8Ldr-1

Then, we extract the useful information from the interviews for faster reading. From there, we did card sorting, which is sorting the useful informations into groups that were similar with each other. For this task, we all worked together to sort it.

Fig 2.1 Interview Transcripts

Fig 2.2 Card Sorting


From there, we created I-statements from the organized information to spot similarities with one another.

Fig 2.3 I-Statements

After understanding more on what the students are experiencing/feeling, we created 3 user personas based on the I-statements. Chika did Daniel lee, Sam did Victor, and Brendan did Rebbeca.

Fig 2.4 User Persona #1: Victor

Fig 2.5 User Persona #2: Rebecca

Fig 2.6 User Persona ##: Daniel


Week 7 (05/06/26)

During class, we write down a series of questions on sticky notes, to gather information of about what kind of features does our app need. We passed the sticky notes to the other teams, and they write their answers in a blank sticky note. Samual, Breandan and I gather all the sticky notes answers and categorized them using the MoSCoW method.

Fig 3.1 Physical Moscow Analysis 

Sam created a storyboard on how it would look like in a typical day of Taylorians when trying to find food.

Fig 3.2 Storyboard

From this, we really understood what usually happens when someone tries to find food in Syopz, and how difficult it is. We can keep in mind about this information and struggles when creating our app later on.


Week 8 (12/6/26)

Unfortunately, in Week 7 class was interrupted, as the whole entire campus is going through a bomb threat crisis, so we have the evacuate. During the commotion the original MoSCoW method sticky note was lost so I was task to write all of the answers in Figma using the last photo reference given by Brendan.

Fig 3.3 Digital Moscow Analysis 

Fig 3.4 User Journey Features

Fig 3.5 App Features Plan

We had our briefing for project management on how to delegate our tasks, who is responsible, accountable, or consulted, and then started to breakdown the tasks needed for the upcoming weeks—especially we need to deliver our first version of the app to the business team already on week 12.


Fig 3.6 Project Management RACI Matrix


Week 9 (19/6/26)

Samuel and Chika started on putting in information and working on slides, while I did brainstorm with the logo designs, by sketching out various logo designs based various idea I tossed around. Brendan began planning on Lo-fi designs and deciding on MVP features. Click here to see what we’ve proposed to the business team: QuickEase Research Deck for Business Team - Presentation


Fig 4.1 MVP Features

Fig 4.2 QuickEase Logo Design Sketches 

The business team gave some feedback to remove some ‘extensive’ niche features that people might not use. Such as the 360-degree camera, and we felt it made sense and heeded the advice.


Week 10 (26/6/26)

I finished the Gantt Chart, and everyone is in the same stage as last week. Samuel came up with a new idea for the logo, where it is derived from people icons, then converted to vectors—seemingly like a queue. Brendan did user tests on lo-fi and did some changes accordingly before actually proceeding to high fidelity designs.

Fig 5.1 Gnatt Chart


Fig 5.2 Lo Fi Wireframe


Week 11 (3/7/26)

This week, Brendan worked on the app design mostly as the business team deliverable is required to submit the next week. Click here to see the construction of the prototype in Figma: https://www.figma.com/design/tTAqogoXK8rJEWTqO41tKt/QuickEase---Prototype?node-id=0-1&t=OFFiCtxbJYs1ZuHk-1


Fig 5.3 Hi Fi Wireframe Progress

Fig 5.4 Hi Fi Wireframe Draft Preview

Week 12 (10/7/26)

This week, the business team is going to have their presentation. Since previously, it was still on the lo-fi stage, we continued working on the prototype of the app. We tried to meet the business team's expectations, so we tried the best we can and send the prototype to them on time.

Fig 5.5 Final Prototype Design Preview


Week 13 (17/7/26)

On week 13, we (Sam) continued working on the slides and made a "brand identity for the slides to create visually consistency throughout the whole presentation.

Fig 6.1 Final Presentation Slides Preview


Week 14 (24/7/26)

Week 14 was the most hectic week for UX Design, since we have to pretty much finalize everything, the prototype, slides, everything. We (mostly Brendan) also improved the prototype, changed some aspects to make it a smoother experience for users. 

Fig 6.2 Final Prototype Design Navigation Maping


Preview of the final prototype:
https://www.figma.com/proto/tTAqogoXK8rJEWTqO41tKt/QuickEase---Prototype?node-id=1-3&p=f&t=fnlXmtkedW7ToSHh-1&scaling=scale-down&content-scaling=fixed&page-id=0%3A1&starting-point-node-id=106%3A841

Final Presentation Deck:
https://canva.link/46ltgr2glhtw40t


Week 15 (31/7/26)

After everything is done, now it's time to do our presentation. It could've been better, but what matters the is the efforts and the contributions we have poured into this project, most and I think it's pretty darn good.

FEEDBACK

Week 11
  • Monetization can be benefited from the vendors that pay more, they get better placements on the app (the top)
  • Don't create grids first. Create cards, and then arrange it, then settle the grids. Its like you wont know which rack to put on if you dont know what books you have.(Feedback from teammate)

Week 12
  • Put icons on our shops (e.g. non halal logo etc the ones that people use often)
  • Logo that represent the shops from we first look at it on the map
  • Highlight activity bar, so we know where we are right now.
  • Main features need to be more highlighted, Estimated waiting times, queueing numbers (e.g. now how many queue in line)
  • Another home page after an order has been created. How to highlight that the order is urgent? Orders countdown attached to the navbar for example.
  • (Feedback from teammate) Put numbers on orders
  • mimic shopee orders, where we put shop name so we can go back to order from that restaurant again(Feedback from teammate)
  • Cut down quantity popup

Week 13
  • 35 mins estimate on the restaurants page should be on another layer to signify importance.
  • Use QuickEase logo instead of taylors logo
  • Add payment page after confirming order as an extra layer of error prevention. People will be more cautious during paying.
  • Your queue and customers in line should be more emphasized.
  • Emphasize that there is a problem to solve, through pictures, etc. on the slides
  • Profile page showing gamification, how many minutes have we saved etc.

Week 14
  • Break down wordy slides to multiple slides

REFLECTION

Experience
To be honest, the UX Design Group is the module in which I have been the least active. I often feel anxious that I have not contributed enough, and I sometimes think that the work I completed was not as significant as that of my teammates. The most stressful part of this module was conducting user interviews. Asking strangers questions made me feel self-conscious and nervous. However, I was fortunate to have patient and understanding teammates who supported me, even when I was slower to keep up with certain tasks.

Observation
Through the class activities, I developed a better understanding of what makes an app feature useful and how different interface elements should work together to create a smooth user experience. I also learned the importance of designing intuitive user flows so that every button and interaction feels seamless and natural.

Findings
I enjoyed the class activities because they taught me how to identify and prioritize the most important features in an app and understand how these decisions affect the overall user experience. One exercise was especially helpful for another module I am currently working on. For example, when analysing the problem of long queues, we organised the key points from interview responses into sticky notes. This activity showed me how affinity mapping can simplify large amounts of qualitative data, making it easier to identify patterns and develop effective design solutions.

Comments

Post a Comment