Tutor Oriel
Sign-up and course selection, redrawn so a student can judge the tutor before booking.
- Role · Sole designer
- Year · 2023
- Tools · Figma
Problem
Create an account, answer four questions, book and pay. Sign-up lost people; course selection lost their trust.
A student is buying an hour with a stranger. They need the right information at the moment they choose.
Goals- Fewer drop-offs, faster sign-up.
- A stronger, more readable brand.
- Functions easy to find and use.
Research
Interviews, then a usability test on the mid-fi prototype: one person, one task, watching where they stopped.
Every request was about the tutor, not the subject.
“Maybe you can add captions for each tutor that include name and experience?”
“The customer would like to know the price and rating at the beginning.”
“Perhaps enabling users to sort price per lesson, popularity, number of reviews and rating. Also search by tutor’s name?”
Decisions
One change per leak, small enough to test.
| Change | Why |
|---|---|
| Create an account | |
| Email field | The booking arrives by mail. |
| Password strength | The rule written out. |
| Course selection | |
| Background and experience on the card | Judge the tutor, not the subject. |
| More subjects | The list was too thin. |
Design
Three screens carry the flow: register, choose a tutor, pay. Green on grey and white.
- Mintevery action
- Greythe words
- Whitethe ground
Outcome
A clickable prototype of the whole path, never built.
ReflectionStart from where people stop, not from the brief. Each round changed only what the last test exposed.