Farul Haziq · case study

PropertyGuru listings needed a location you could trust.

turning listing creation from form filling into search and checks.

Role
Product designer, PropertyGuru
I owned
the end-to-end redesign
Duration
8 months
Platform
web and mobile
Markets
Singapore and Malaysia
A property agent on the phone at her laptop, beside a map of Kuala Lumpur and Petaling Jaya with a pinned property.

the brief

why it existed

The problem

property agents, PropertyGuru's customers, post listings through AgentNet. creating one was a long form: free-text property names, no location check and no duplicate detection. wrong listings had to be corrected by hand, and buyers lost trust in what they saw.

The goal

treat listing creation as a search and validation problem, not form filling, so every listing starts from accurate data.

My part

  • led the end-to-end redesign of the listing creation flow.
  • improved the property search, so agents pick a verified property.
  • designed the AI description step, with limits that stop scams.
  • facilitated about 20 agent interviews (run by a UX researcher) and the stakeholder workshop that set the direction.
  • validated the design with agents, through to a beta with 200+ of them.
  • worked with a PM, a design manager and the dev team, and added new components to design system 3.0.

the journey

how it actually went

  1. Step 1 · the old flow

    Where the bad data came from

    across Malaysia and Singapore, custom locations were often fake or scams. our team had to check each one by hand, which was slow and hard.

  2. Step 2 · interviews

    Hearing from agents first

    about 20 interviews in a month, run by a UX researcher, with me facilitating. one thing stood out: agents race to list first, so speed comes before everything. we designed around that.

  3. Step 3 · workshop

    Four rules for every screen

    the stakeholder workshop cleared up the direction, and gave us four rules: accuracy over convenience, guide instead of restrict, use the white space, build confidence through clarity.

  4. Step 4 · the new flow

    Fewer pages, less typing

    we merged pages, cut fields that no longer mattered, and let a verified property fill in its own details. one click writes the description.

  5. Step 5 · beta

    200+ agents before everyone

    real use showed edge cases no prototype could. short feedback loops fixed them before the full rollout.

the mess in between

what we were up against

the work

what actually shipped

the calls

the decisions behind it

the outcome

what changed

measured over the 3-month beta with 200+ agents, against the 3 months before. those results gave leadership the confidence to roll it out to every agent.

reflection

what I'd tell past me

"i'd get everyone clear on the direction first."
early on, the direction was unclear, for design and for the business. it only became clear after we ran the stakeholder workshop.