UX Design - Task 3: User Journey Map & Ideation
02 June 2025 - 13 June 2025 (Week 7 - Week 8)
Additionally, the "must-have" features currently proposed do not fully address the core problems faced by our user personas. They still reflect high-level thinking rather than practical solutions. It’s advisable to revisit the user personas and problem statements to better align the app features with users' real needs.
Moreover, due to the complexity of train and bus schedules, it's important to categorize occasions and features thoughtfully. The information design for scheduling must be carefully planned and structured to ensure clarity and ease of use.
The process of completing the journey map was smooth and straightforward, thanks to how familiar we were with the collected data. However, due to a heavy workload and time management issues, I only managed to finish the task quite late, just before our ideation discussion.
Despite the confusion, we managed to work through it without further issues.
Looking back at the ideation, it was filled with fun and exciting ideas. But we also reminded ourselves to stay relevant and within the scope of User Experience, and to consider our actual skill sets. There was no point in planning something beyond our capabilities if we couldn’t make it happen or explain how it should work. So in the end, we thought it would be best to propose one or two realistic ideas, along with one that may seem ambitious now but could be possible in the future.
In sum, it was a relief to have the first seven weeks completed. But at the same time, the most important part of the project is just about to begin and will continue until the end of the semester. I genuinely hope — and believe — that we will gain a lot of experience and learn from each other, especially in terms of design perspectives and practical insights.
This is something I’ve really been craving after years of studying UI and UX. Honestly, I’ve started to feel a bit stuck and disconnected from it. So I truly hope that this collaboration between different specialisations will give each of us the chance to share our work and our thinking, and maybe even reignite that passion again.
Vincent Lee // 0359386
UX Design // Bachelor of Design (Hons) in Creative Media // Taylor's
University
Task 3: User Journey Map & Ideation
Instructions
MIB
<iframe
src="https://drive.google.com/file/d/1rgJw-kz3JflGH9Gupzo7ZHW9mu_jM3Nx/preview"
width="640" height="480" allow="autoplay"></iframe>
Task 3: User Journey Map & Ideation
As a group, we are required to develop a User Journey Map based on the User
Personas and Empathy Map we’ve created. This involves identifying and defining
the user’s journey across different touchpoints and phases, from start to
finish.
|
|
|
|
|
|
User Journey Map
|
| Figure 1.3 - User 1: Sasha (Close Distance Commuter), Week 7 (02 June 2025) |
|
| Figure 1.4 - User 2: Brice (Far Distance Commuter), Week 7 (02 June 2025) |
|
| Figure 1.5 - User 3: Fatima (Public Transport Commuter), Week 7 (02 June 2025) |
MoSCoW Method
 | |
|
Our app features have been prioritised using the MoSCoW Method as shown below.
[updated on 16 June 2025)
MUST HAVE (Core
features essential for functionality)
- Transport Schedules and Nearest Stops & Stations
- Transport Schedules and Nearest Stops & Stations
- Display up-to-date schedules for: BRT, buses, vans.
- Nearest bus stops and train stations.
- Real-Time Vehicle Tracking
- Live location updates for all transportation modes.
- Estimated arrival times (ETAs) and delays notifications.
SHOULD HAVE (Important
features that enhance the user experience)
- Parking Availability for Multi-Storey Facilities
- Parking Availability for Multi-Storey Facilities
- Real-time parking space availability tracker.
- Smart suggestions for nearest available parking.
- multi-storey parking (future implementation)
COULD HAVE
(Useful additions to improve accessibility and convenience)
- Scooter Sharing & Charging Stations
- Scooter Sharing & Charging Stations
- Map of scooter availability and charging port locations around campus.
- Ride-Hailing Integration with Community Feature
- Enable students to connect with others heading to similar destinations and share Grab rides together, promoting cost-saving and community bonding.
- Expanded Van Services
- Van service for nearby residential students.
- Access to secondary entry points to reduce congestion.
WON'T HAVE
(Features excluded from current development scope)
- Buggy Routes for Parking Pickup
- Buggy Routes for Parking Pickup
- Specific buggy routes from parking zones to campus building.
- Interactive Walkway Features
- Motivational quotes, distance counters, or emergency call buttons on walkways.
- Better suited for physical infrastructure improvements, or interactive animations video.
- Gamification
- Features such as point collection, fitness goals, or step tracking.
Features Lists
 |
| Figure 1.7 - General Features and Inspirations, Week 9 (17 June 2025) |
1. Home Page
- Quick access to services (e.g., car, scooter, ride sharing)
- Current location detection
- Clear call-to-action (e.g., "Where are you going?" / "End Ride")
 |
| Figure 1.8 - Feature 1: Home Page |
2. Search Bar
- Prominent search input field with icon
- Recent searches or suggestions
3. Parking Locator Features
- Map pins with availability of parking slots
- Type of parking (Basement or Open Lot)
 |
| Figure 1.9 - Feature 2 & 3: Search Bar & Parking Locator |
4. Live Map & Tracking
- Real-time vehicle or location tracking
- User and destination markers
- Route preview with animation or progress bar
- Zoom/pan-friendly interface
 |
| Figure 1.10 - Feature 4: Live Map & Tracking |
5. Parking Availability
- Real-time parking space availability tracker
 |
| Figure 1.11 - Feature 5: Parking Availability |
6. Push Notifications for:
- Bus/van delays
- Arrival reminders
- Emergency or traffic announcements
 |
| Figure 1.12 - Feature 6: Push Notifications |
7. Schedule Page
- Daily/weekly transport timetables
- Option to favorite specific routes or transport types
- Alerts for route-specific updates
 |
| Figure 1.13 - Feature 7: Schedule Page |
Task 3 Submission
 | |
|
Figure 1.15 - Group Progressive Presentation Slides, Week 8 (13 June 2025)
Feedback
Week 9 - User Journey Map
The current situation should be addressed realistically. Implementing
multi-storey parking appears more like a long-term solution or future plan,
making it less relevant to present needs. While it may not resolve the current
parking challenges, the idea of incorporating parking availability features is
valuable. Therefore, it’s recommended to revise the MCSW method and clearly
define these features within the app.Additionally, the "must-have" features currently proposed do not fully address the core problems faced by our user personas. They still reflect high-level thinking rather than practical solutions. It’s advisable to revisit the user personas and problem statements to better align the app features with users' real needs.
Moreover, due to the complexity of train and bus schedules, it's important to categorize occasions and features thoughtfully. The information design for scheduling must be carefully planned and structured to ensure clarity and ease of use.
Reflection
Week 7
Each of us was tasked with creating one user journey map based on our
familiarity with the personas. While working on mine, I kept referring to the
interview transcript to help put myself in the users’ shoes and better
understand what they go through daily. It might have been more accurate if I
had imitated their routine. That way, I could have thought more out of the box
and come up with a plan or design that truly supports commuters.
The process of completing the journey map was smooth and straightforward, thanks to how familiar we were with the collected data. However, due to a heavy workload and time management issues, I only managed to finish the task quite late, just before our ideation discussion.
Week 8
The ideation process was not too difficult, mainly because we had already
worked on the "How Might We" statements and Crazy 8s earlier. That helped us
generate plenty of ideas for our app and eventually develop three MVPs.
However, I would say the instructions for ideation were not very clear. For
example, what exactly were the specific requirements for this stage? Were we
supposed to include both the MoSCoW method and a prioritisation matrix? They
seemed similar, even though we knew there had to be a difference between them.
Also, were sketches required? Was that something Dr. Wong expected from us?
Despite the confusion, we managed to work through it without further issues.
Looking back at the ideation, it was filled with fun and exciting ideas. But we also reminded ourselves to stay relevant and within the scope of User Experience, and to consider our actual skill sets. There was no point in planning something beyond our capabilities if we couldn’t make it happen or explain how it should work. So in the end, we thought it would be best to propose one or two realistic ideas, along with one that may seem ambitious now but could be possible in the future.
In sum, it was a relief to have the first seven weeks completed. But at the same time, the most important part of the project is just about to begin and will continue until the end of the semester. I genuinely hope — and believe — that we will gain a lot of experience and learn from each other, especially in terms of design perspectives and practical insights.
This is something I’ve really been craving after years of studying UI and UX. Honestly, I’ve started to feel a bit stuck and disconnected from it. So I truly hope that this collaboration between different specialisations will give each of us the chance to share our work and our thinking, and maybe even reignite that passion again.
Week 9
The feedback we received is valuable and highlights important areas we need
to address before moving forward with wireframing and prototyping. Although
it does not drastically affect the features we selected last week, it raises
major concerns that prompt us to rethink how we can design solutions that
truly meet the needs of our real users, the students who rely on Taylor’s
campus transportation system.
Looking back, we realize that Miss had already anticipated some of these issues during our proposal stage, especially since two group members are not regular public transport users. This may have limited our understanding and contribution to a project focused on commuting. Additionally, the features we have chosen are quite similar to our initial ideas, which shows a lack of deeper exploration.
With only three weeks left to complete the design process, we are definitely feeling the pressure. However, this feedback is a timely reminder for us to reflect carefully and refine our approach so we can create an application that truly benefits the students of Taylor’s University.
Looking back, we realize that Miss had already anticipated some of these issues during our proposal stage, especially since two group members are not regular public transport users. This may have limited our understanding and contribution to a project focused on commuting. Additionally, the features we have chosen are quite similar to our initial ideas, which shows a lack of deeper exploration.
With only three weeks left to complete the design process, we are definitely feeling the pressure. However, this feedback is a timely reminder for us to reflect carefully and refine our approach so we can create an application that truly benefits the students of Taylor’s University.
Quick Links
Task 1: UX Audit
Task 2: User Personas & Empathy Map
Task 3:
User Journey Map & Ideation
Final Project: Prototype & Concept Training
