All case studies

Login creation and password recovery

Designing three focused authentication journeys—sign up, log in, and recover access—for a long-running events platform refresh.

Context

A Buddhist events booking system, in use for over a decade, needed a full rebrand and experience update across front- and back-office.

This case study covers one slice of that work: standardising user creation, login, and password recovery for front-office bookers.

Problem framing

Where the experience breaks down today—and what good looks like after.

01

What's missing

No consistent design process for:

  • User login
  • Password recovery
  • Account creation
02

The question

How do we deliver strong UX while stripping everything non-essential from these three journeys?

03

Who it's for

Front-office users booking international Buddhist festivals.

04

Success criteria

  • Minimum clicks to log in
  • One predictable pattern across all three flows
  • Fewer support tickets after launch

Flow mapping

How login, account creation, and password recovery connect—mapped before any UI work.

Low fidelity design

Four shared UI patterns: base screen, credentials box, notification box, and form box.

High fidelity design

Login and account creation on the shared base screen—same structure, different states.

Journey 1: Account creation

User taps Create an accountEnters email — system checks availabilityIf available, form opensUser completes form and confirmsVerification email sent — user confirms account

Journey 2: Password recovery

User taps Forgot passwordConfirms email (pre-filled or entered)Receives reset link by emailValid link → new password screen · Expired link (10 min) → request againSets new password — confirmation with log-in prompt

Outcome

Predictable, low-friction authentication

Three distinct journeys sharing credentials, notification, and form patterns—so behaviour feels consistent across the product.

Fewer steps where possible, aligned copy and layout. The goal: less friction for festival bookers and fewer login-related support tickets after launch.