Product Design Case Study

Extending Otaghak from stays to full trips

Designing a new Tours & Experiences line that sits alongside bookings — without feeling like a bolt-on product.

Role
Product Designer
Duration
1 month
Collaboration
Engineering & Product
Status
Ready to launch
Desktop view of Otaghak's Tours & Experiences line
Mobile view of Otaghak's Tours & Experiences line

The business case

01

Otaghak was a stay-booking platform. Four signals pointed to the same gap: users wanted a full trip, not just a room.

  • MarketRising demand for trips that bundle experiences, not just lodging
  • UsersDirect requests for add-ons alongside stay bookings
  • CompetitorsOther players already moving toward multi-service trip platforms
  • BusinessOpportunity to raise order value and retain users longer
Core design challenge

Ship a new product line that looks and feels native to Otaghak — without forcing the frontend team to build a wave of new components.

Process

02
01
User research
Studied current user behavior to identify which tours would resonate and where they fit into the existing booking journey.
02
Wireframes
Mapped the information architecture and flows, reusing existing design system patterns instead of starting from scratch.
03
MVP
Scoped to the core loop — discover, filter, book — and cut everything non-essential to ship faster.
04
Engineering collaboration
Worked closely with frontend throughout to keep every screen buildable with components already in production.

The result

03
otaghak.com/tours
Full desktop page of Otaghak's Tours & Experiences line
Scroll to see the full page

Activity-based filtering

Tours filtered by nature, forest, cave, and desert activities, using the same filter pattern as stays.

Local guides, not just tours

Guide profiles with ratings and experience build trust in a category users didn't know yet.

Tied to the stays experience

Destinations and reviews reuse the same cards and rating format users already trust.

Full mobile page of Otaghak's Tours & Experiences line

Mobile carries the same hierarchy as desktop, with touch-friendly spacing and no separate mobile-only components for engineering to build.

Current status

04

Not yet publicly launched — currently ready for final handoff and release.

1

Design complete

All core discovery, filtering, and booking screens are finalized.

2

Component-driven

Most of the page is built from Otaghak's existing design system.

3

Dev-ready

Specs and files are already in the frontend team's hands.

Takeaways

05
New vs. consistent
Launching a new line inside a mature product means constantly trading off novelty against consistency — a call worth making early, not discovering late.
Engineering earlier
Looping frontend in at the wireframe stage was the single biggest lever for cutting build time and avoiding duplicate components.
MVP means real cuts
Shipping in one month only worked because non-essential features were cut on day one, not near the deadline.