{{ g.items }}
Pursued a BSc in Digital Media at SUSS to transition into UX, building skills in wireframing, prototyping, user flows and user research.
A plant-care companion app, designed end-to-end for NCO205: User-Centred Design: Human Factors and Design Thinking
Our brief was to pick a real user activity and take it through the full design thinking process. As a team, we chose planting and gardening.
We ran contextual inquiries and structured interviews with 5 current or former plant owners — watching their real watering, pruning, and repotting routines, then following up with direct questions about their knowledge, needs, and frustrations. This phase surfaced the pain points that helped shape the next stages of development.
Our five participants were aged 26 to 62, ranging from novice to expert growers.
| Objective | What we looked for |
|---|---|
| Understand behaviours | How users think and act during their real plant care routines |
| Identify pain points | Frustrations and challenges in their gardening process |
| Learn their context | The tools, methods and terminology they use |
| Explore opportunities | Where solutions could ease their pain points |
We then ran structured interviews with the same five participants, covering their experience, needs and concerns, to add depth to what we observed.
“A task schedule that helps me keep track of watering and fertiliser needs.”
“I watered all my plants regularly but some plants show signs of withering.”
We mapped what interviewees said, thought, did, and felt to move past surface complaints and trace each pain point back to a root cause.
| Pain Point | Root Cause |
|---|---|
| {{ pp.point }} | {{ pp.cause }} |
To solve the above pain points, we decided to design a phone app as it would be accessible to almost everyone with a phone, low-cost to produce, and easy to update and refine after launch. We then created a low-fidelity prototype to show to our users.
This is the first low-fidelity prototype we showed to our users during testing.
Main functions:
We ran in-person testing sessions with an early low-fidelity prototype to gather feedback. Each participant explored it freely, thinking aloud as they went. We only stepped in when asked for help, then used the feedback to brainstorm new features and prioritise changes.
| Page | Issue / Pain Point | Solution Implemented |
|---|---|---|
| {{ t.page }} | {{ t.issue }} | {{ t.solution }} |
This is the final high-fidelity prototype, refined through two rounds of user testing.
What participants said in our second round of user testing:
Note: Images in this prototype have been switched to simplified vectors due to file size concerns. Colours have also been edited to meet WCAG contrast requirements.
This was my very first UX project at school, and the start of my transition into UX design. Coming from a graphic design background, I learnt how important it is to always design with the end user in mind, rather than just making an app 'look good'. Keeping user feedback at the centre of every stage, especially through the two rounds of testing, meant we shipped features that solved frustrations people actually had, not ones we assumed. By the end, we had created a tool that could genuinely help gardeners, regardless of their experience level.
{{ vs.blurb }}
{{ para }}
{{ para }}
{{ para }}
{{ para }}
{{ para }}
{{ para }}
{{ para }}
A secure, simple and seamless way for everyone in MOE to access their apps.
Worked on Edupass, MOE’s Identity and Access Management System (IAMS) — a secure, simple and seamless way for staff and students to sign in and access their apps, while giving administrators a central portal to manage accounts and permissions.
Edupass serves two main groups:
One way in. One-time setup, seamless sign-ins after — a simpler, more secure passwordless way to access MOE applications for all staff and students.
One place to manage access. Through the admin portal, admins create accounts, assign roles, and control access across the whole life cycle of an Edupass identity.
Everyone in MOE, from HQ staff, school staff and students, needs access to various MOE apps daily.
With the current system, students have to remember long emails and passwords every login. This costs teachers lesson time, and admins end up resetting passwords daily.
The login is never the point. A teacher is trying to start a lesson. A student is trying to get to their work. Edupass' objective is to stop the login from being the thing that gets in the way.
The best login isn't one people remember. It's the one they barely notice.
I worked across the full brand system, from the manifesto to the logo and design system. Each item is built on the previous work done, to create a cohesive branding that effectively communicates the problems Edupass is trying to solve.
Three brand principles guide every Edupass interaction.
| Principle | What it means |
|---|---|
| Earn Trust | Confidence through security, reliability, transparency and consistency. |
| Care Ahead | Anticipate needs and quietly remove friction before it becomes frustration. This is our take on omotenashi, a Japanese concept of thoughtful hospitality: anticipating a guest’s needs before they have to ask. |
| Make Room for Joy | Access fades into the background so people can focus on teaching, learning and getting things done. |
Trust builds confidence, care creates ease, and ease makes room for joy.
Edupass speaks like a thoughtful host: calm, prepared, respectful and reassuring, never dramatic, patronising or unnecessarily technical. We guide rather than instruct, reassure rather than alarm, and explain rather than assume.
“We couldn’t recognise you. Try again, or ask your teacher for help.”
“Authentication failed. Error code AUTH_0042.”
Each element carries one part of the brand principles into the visual and behavioural identity.
An arrow is one of the few shapes that reads the same way to everyone, everywhere, with no translation needed. It is the most direct way to say “moving ahead.” Before settling on the final logo, we ran user testing on our logo variations to see which one people read most clearly.
Role: Express "Ahead"
We were questioned on why the logo needed two colours instead of one. In feedback, some people read the single-colour wordmark as “Edup-ass” instead of “Edu-pass”. Splitting the wordmark into two colours made the break clear and the name more readable for the general user.
Lexend was designed to reduce visual stress and improve readability. It began with dyslexic and struggling readers in mind, but its creator found the benefits held for everyone: generous spacing, clear letterforms and a strong hierarchy.
Role: "Care" through readability
We had our eyes set on Lexend the moment we saw it, for its round single-storey “a” instead of the usual double-storey one, and for being dyslexia-friendly. We felt this brought across our brand principle, Care Ahead, by ensuring our text is easily readable to students of all age groups.
Blue reads as trust, the feeling we want to lead with, and carries associations of calm and security. A brighter, more energetic blue keeps it feeling alive rather than flat and institutional.
Role: Establish "Trust" through colour
Care is expressed through how the experience responds to people, not through visual styling alone. Before: tell me what will happen. During: reassure me something is happening. After: tell me what happened and what I can do next.
Role: Express "Care Ahead" through behaviour
In progress.
Role: Express "Joy"
I designed the onboarding deck that gets students into Edupass for the first time.
Schools, teachers and staff have been relying on an outdated access management system that makes everyday access a struggle, but they have learnt to work around it. Edupass is set to replace it, and that familiarity makes change management trickier: even a better system asks people to give up habits they already know, so this was change management as much as onboarding. Guided by our Care Ahead brand principle, our take on omotenashiomotenashi · おもてなしA Japanese concept of thoughtful hospitality: anticipating a guest’s needs before they have to ask., we wanted the deck to answer each question before a teacher even realised they had it, to ease their mental load.
One flow, tailored for every school type and device: Multi-factor authentication is a core part of what makes Edupass secure, but secondary students don't have their phones with them in school, while JC students do. This changes the setup steps for each group, which is why every school type and student needed its own tailored deck. On top of that, students use three device types — iPad, Windows laptop and Chromebook — and each one renders the same screen differently, so every combination needed its own walkthrough. In total, I created 4 decks to tailor to each use case. Each step also has its own dedicated GIF detailing the flow, so the reader always knows where to go next.
Together, these led to 4 tailored decks instead of one generic guide.
Each step is paired with a GIF of the actual flow, so students always know what to do next. Drag to compare the first version with now.
I was tasked to take ownership of the end-to-end flow of the student admin portal, starting from the ground up.
I am now at the exploration stage, mapping out the flows behind the actions a student admin can take. This work will feed directly into the screen development stage.
Nail down the student admin flows, which are still under discussion, then proceed with early screen development.
Work in progress, check back soon!