Ritesh Yadav Product Designer

Ritesh Yadav — designer by role, systems owner by habit.

Reel 01 / R. Yadav01 / Title
Scroll ↓

each one starts with what was going wrong

  1. 01
    WanderOn · Booking

    The booking flow that needed a phone call

    In 2024 you could pay for a trip on our website and still not have a booking — a sales executive had to call you and make it by hand. The brief was a facelift. Website bookings have since grown from about 7.8% of the total to about 30%.

    Role
    Product Designer · with 2 developers, founders, sales and ops
    When
    2024 — present
    Status
    Phase 1 live since Jul 2024 · Phase 2 confidential
  2. 02
    WanderOn · Discovery

    The chatbot that turned out to be a search bar

    People were typing “Bali” into our support chat. They weren’t asking for help — they were searching. 28,323 conversations later, the problem wasn’t the chatbot at all.

    Role
    Product Designer · With 2 PMs and a team of 10 engineers
    When
    Q4 2025 — Q1 2026
    Status
    Research complete · fixes on the roadmap
  3. 03
    WanderOn · Research

    Reading the room before redesigning it

    Average session time looked healthy and bounce rate looked normal. Both were hiding the people who wanted to book and couldn’t. What I found shaped the booking work that followed.

    Role
    Product Designer · With 2 PMs and a team of 10 engineers
    When
    Q3 — Q4 2024
    Status
    Complete · fed the booking redesign

Also

  1. 04
    Practice

    How I actually use Claude at work

    A running log of what AI does well in my day, where it gets things confidently wrong, and the parts of the job I don’t hand over.

    Role
    Personal practice
    When
    Apr 2026 — ongoing
    Status
    Updated as I go

Weekend builds

Things I code when nobody needs them from me.