Is UX dead?
5 mins read ·
Your Seat at the Table: Why UX > UI
Working at Ventrata, I’ve seen firsthand how fast the travel space evolves. From AI trip planners that can turn an Instagram Reel into a full itinerary in seconds, to chat-based tools that personalize traveler experiences on the fly — user experience is being reshaped by machine intelligence. You might wonder: will travel designers soon be replaced by code?
Here’s the thing… if your role feels like dragging elements on Figma or tweaking modal styles, maybe you’re someone who hasn’t stepped out of wireframes lately. Real value in UX lies in shaping decision flows, reducing clicks per task, and helping travel operators avoid mistakes.
You’re not paid to drop UI components. You're paid to make calls. Whether users should override rates, or how to show limited availability in calendars.
That’s not UI. It's UX. You research, then you decide. No surprise that large software teams clearly separate researchers and architects, and sometimes (just sometimes) they try to combine both.
When AI Joins Your Workflow (But Doesn’t Take Over)
You know what? AI isn’t after your job. It’s begging to save you time. OTAs already let internal users type prompts like “show me unnecessary low‑cost routes” and generate itinerary suggestions or ROI forecasts. Their chatbot assistants handles 50% of inbound help‑desk questions and even flags expense overages based on patterns, and rolled out broader AI capabilities: real‑time analysis, costs, business‑rules compliance, in 2025. This isn’t sci‑fi, it's your next teammate.
But here’s the catch: AI doesn’t make value judgments. It can sketch screens or explore variations, but unless you write the right prompt - specifying roles, edge cases, error recoveries… it just guesses. Prompt engineering has turned into a high‑leverage role in the enterprise space, not just a buzzword, some companies are hiring prompt engineers as product team members.
That part is unstoppable.
UX ≠ UI
Let’s clear one thing: UI is pixels and states. UX is about decision-making, empathy, workflow mapping. And there are two kinds of UX designers:
- The researchers: the ones doodling bold red “Error” buttons on paper prototypes, then watching users fumble in lab tests.
- The architects: designers who code rules into screens, they imagine flows that users follow daily.
Many folks try to play both parts, but it becomes Jekyll and Hyde. Better to focus, one does the research, the other makes the calls.
Data‑Driven UX (with a dash of intuition)
At Booking.com, early algorithms like Naive‑Bayes lifted guest engagement by using real data instead of gut-feel alone, even a decade ago. Now imagine that at scale, with millions of travelers per day: next‑Gen travel services optimize itineraries in real time, blending constraints like weather, network speed, and personal preference into hyper‑personal plans.
Early in a project, you sketch and rely on instinct, does the workflow feel good, intuitive? Then you test with colleagues. But once user logs pile up, I mean tens of thousands or more, you switch to data tools: heatmaps, session tracking, funnel drop‑off analysis. For example, pinpointing a booking abandonment in the seat selection flow or overwhelming customer info page can save enterprise clients lot of costs. With enough patterns, your design can circle back to intuitive layouts, but now backed by behavioral proof. Patterns guide, yes, but your feel still decides.
Sure, data can mislead, maybe your CTA was busted and no one clicked despite a great layout, but patterns from analytics help train your intuition.
B2B vs. B2C Design (both UI & UX)
Designing for a business client (say, sales portals, admin dashboards, or POS devices) feels similar, but it isn’t:
- 1. Audience scales differ: B2C travel serves thousands of leisure users who need snappy, emotional journeys. B2B serves few users daily, often with deeper engagement, loyalty, and a need for efficiency and precision.
- 2. Decision‑making process: In B2C, a traveler books on impulse or social proof. B2B features often require pattern following procedures and advanced features, like capacity overrides, internal promotions, etc.
- 3. UI priorities: While B2C UI might focus on emotion and minimalism, B2B UI handles detailed data and advanced layers.
- 4. UX metric differences: B2C measures bounce rate, conversion, cart abandonment; B2B defines success by checkout time, error rate, retention.
Yes, both are people, but the intent, expectations and trust levels are worlds apart.
How to Check Your Thinking (Without Guessing)
A couple of reliable ways:
- - Contextual Inquiry: Sit beside an agent or admin, or watch them online. Watch them handle a refund or advanced checkout flow. Notice what tabs they switch to, errors they pause on.
- - Pluralistic Walkthroughs: Bring together a developer, a manager, a pilot user, and read through a task silently, then each marks what they'd do. Everyone compares.
- - Data Driven: Based on previous features, you can guess users behaviour in new situations. Patterns emerge.
Don’t rely on one method alone. Combine observation, discussion, and data, they reveal gaps you didn’t know existed.
Do We Need to Go Beyond “Best Practices”?
Sometimes yes, and travel design often calls for it. Best practice exists for a reason, but in travel or other niche industry you might need to bend the rules:
- - You might need to include special voucher scanning at a kiosk rather than checkout flows.
- - Or design for a region with sparse internet: offline booking, bright sunny day, local-payment UX, and caching strategies.
In these cases, there’s no established case study. You must make new rules. That’s not just acceptable, it’s essential for travel software providers that move fast or serve niche markets. You need to author your own internal ‘patterns’, validate them, educate clients.
Teams of Tomorrow: UX, AI & Prompt Engineers
Forget the idea of replacing designers with machines. A much more realistic future is two designers working with AI tools to produce the output of a 10‑person team. Should I be worried?
Only if you don’t adapt, and still believe design is dragging components in Figma. You're designing experiences that travel professionals rely on daily. AI might automate some tasks, but it can't replace empathy, judgement, or domain expertise. Designers become the prompt writers, the strategy holders, the syntheses of data and intuition.
So, no, don't fear AI. Fear being outpaced by someone who knows how to use it.
