Connected around the trip.
Discovery, planning, booking, payments and post-booking experiences were improved as related journeys.
LUXTJ Extranet · Product & UX case study
Designing the operations behind a luxury trip.
The extranet connects the customer promise to the partner work required to fulfil it, from listing content and availability to bookings, offers, staff and payments.
- Role
- Lead Product & UX Designer
- Scope
- UX, UI, workflows, component library
- Context
- B2B partner operations
- Platforms
- Web, extranet and mobile
- Team
- Stakeholders and developers
- Status
- Implementation-ready design
One ecosystem across customer and internal workflows.
I designed the complete Luxury Travel website and extranet, connecting customer and internal workflows across web, extranet and mobile.
A shared component library.
Reusable patterns improved design consistency and made developer handoff more efficient.
Requirements made concrete.
Close stakeholder and developer collaboration helped resolve edge cases before launch.
The challenge
The interface had to serve work, not just display data.
Partners need to move between content, bookings, people and money while preserving the context of what they are managing. A dashboard can look clean and still fail if ownership, status or the next action is unclear.
Design questionHow might the extranet make complex partner operations feel predictable without hiding the detail people need to do the work?
Core modules
Six areas. One operational language.
The navigation follows the partner's responsibilities instead of mirroring the internal organisation of the business.
Listings
Create and maintain property information, imagery, amenities and experience details.
Bookings
Keep reservation context, status and required partner actions visible.
Staff
Support clear roles and access without exposing unnecessary controls.
Offers
Manage discounts and promotional availability as structured product content.
Payments
Connect earnings, payment status and operational follow-up.
Support
Give partners a predictable route to guidance and issue resolution.
Selected interface
Listings combine rich content with clear operational control.
Property imagery and customer-facing details remain recognisable, while administrative actions, settings and states are organised around the job the partner needs to complete.
Consistency lowers the cost of complex work.
Progressive complexity
Frequent actions stay visible; specialist settings appear only when relevant.
Operational context
Status, ownership and next actions travel with each booking or listing.
Safe changes
Destructive and financially meaningful actions explain their consequence before commitment.
Shared language
Components and labels stay consistent across customer web, extranet and mobile.
Shared component library
One system across three platforms.
Buttons, cards, filters, forms, statuses and summaries use the same interaction logic across customer web, partner extranet and mobile. The visual expression adapts; the behaviour stays familiar.
Design to delivery
Resolve ambiguity before it becomes rework.
I worked closely with stakeholders and developers to turn business requirements into clear, implementation-ready designs. Reviews focused on behaviour, missing states and edge cases, not only visual matching.
What the handoff made explicit
- Role, status and permission states
- Validation and recovery behaviour
- Empty, loading and incomplete states
- Responsive component behaviour
ScotCare: designing from panic to plan.
An evidence-informed university project about safer, clearer care navigation in Scotland.