BackPerspectives

Build for the traveller’s worst day

In travel, your brand isn’t the smooth booking—it’s how you behave when plans fall apart. Design priorities, culture, and systems for those moments, and growth follows.

5 min read

Your brand shows up when the day goes wrong

Most travel experiences are invisible when they work. The search is fast, the booking confirms, the wallet pass appears, and life moves on. Nobody tells their friends about a confirmation email. We all talk about the day the trip went sideways—the delay that broke a connection, the hotel that over‑sold, the visa that didn’t clear, the storm that moved in. That’s the moment a company’s brand becomes real. Not the color of the app icon. Not the clever copy. How you behave when the traveller’s day breaks.

I’ve spent enough time building for this industry to see a pattern: we over‑optimize for the happy path because it’s easier to demo. The bad day feels like an edge case. It isn’t. It’s the place customers form a permanent opinion about you. And as more of the normal journey is handled by automation, the differentiator compresses into those few hard hours where judgement, preparation, and design meet reality.

Automation makes the “good day” boring—by design

Over the next decade, assistants will plan and book more of our travel. That’s a win for everyone. It also changes what matters. When AI takes care of ordinary steps, the front stage looks calmer. The backstage either gets stronger—or it shows seams. The companies that win won’t be the ones with the flashiest chat. They’ll be the ones that built their operating posture around recovery: clear promises, fast options under stress, and a human lane that works without drama.

This isn’t a call to turn every customer interaction into an emergency drill. It’s a call to accept that reliability—the ability to keep commitments when conditions change—is the real brand in travel. If you’re a founder, it’s your job to make that reliability boringly dependable.

What “build for the worst day” looks like in practice

When I say “build for the worst day,” I mean a few simple, durable behaviors:

  • Make promises explicit and close the loop. If a fare isn’t final until ticketed, say so and update quickly. If a room is on request, confirm or replace without asking the customer to chase. Brand is the distance between what you say and what happens.
  • Offer options, not apologies. When a delay risks a misconnect, present real alternatives that respect constraints (arrival time, seat preference, no overnight layovers) and act decisively once confirmed. Apologies are posture; options are care.
  • Keep context attached to the trip. If a person needs to step in, they should see the full state—what changed, what matters to the traveller, what was tried. No retelling, no ping‑pong.
  • Treat refunds, credits, and receipts as aftercare, not errands. Follow through without friction and show progress without making people do paperwork.

None of this is glamorous. That’s the point. Reliability is a product choice expressed a thousand small ways. It’s not a campaign.

Set founder priorities around recovery, not just conversion

Most roadmaps lean toward surfaces: a better search, a cleaner checkout, a loyalty widget. Useful, but incomplete. If your brand is decided on the worst day, your priorities should reflect that. A few I hold onto:

  • Design with stress in mind. Write flows that assume a customer is at a gate, on poor wifi, or on the move. Short words. Clear outcomes. One‑tap choices.
  • Time to finality beats time to click. Measure how quickly a commitment becomes real (ticket issued, room secured), and make the system tell the truth about where things stand.
  • Escalation is a product. The “talk to a person” lane should exist, be fast, and land that person in the right place with the right authority.
  • Shine a light on the dull parts. Reconciliation, change propagation, and status are not back‑office chores; they are how trust survives contact with the real world. Make them visible and automatic where possible.

If you hold yourself to these, your conversion work gets easier, not harder. People come back to the products that treat them well when life happens.

Culture matters: rehearse, write down, celebrate the save

Reliability is a cultural posture before it’s a technical one. A few habits change the slope of a company:

  • Rehearse chaos. Don’t wait for a storm to find your holes. Run table‑top drills: a mass delay, an over‑sell, a system outage. Make the playbook real, and make sure systems—not just people—carry the load.
  • Write the promises. Decide what “we will do” actually means in common failure modes. Put it where product, operations, and finance see the same words. Vague promises die in handoffs.
  • Celebrate the boring save. Don’t only reward new features. Reward the engineer who made after‑care automatic or the operator who removed a weekly reconciliation ritual. These choices compound into brand.

Teams act on what leaders praise. If you treat recovery as first‑class, your company will ship for it.

Architect for calm under change

The worst day is when fragmented systems show their cost. When three tools disagree about the state of a trip, recovery becomes a negotiation. The antidote is coherence. One system of record for the trip. Clear responsibilities between products. Interfaces that don’t surprise each other. When the model is consistent, automation can do more of the right work and people can do the judgement.

I’ve written about why I think advantage in travel comes from architecture, not inventory. If the core represents the truth once—and everything else respects it—you can scale care without adding headcount. For that view, read: The future of travel is architecture, not inventory.

What not to do

  • Don’t confuse brand with marketing. On a bad day, no slogan saves a broken process.
  • Don’t hide reality. “We’re checking” without a timeline becomes anger. Say what’s true and what happens next.
  • Don’t paper over with heroics. If a person has to memorize the workaround, fix the system so the next person doesn’t.
  • Don’t optimize the happy path so hard that recovery becomes impossible. A clever checkout that paints you into a corner is not a win.

The founder’s job: reorder the backlog

If you’re building in travel, ask a blunt question: “On the day our customer’s plan breaks, are we the company they’re glad they chose?” If the answer is “sometimes,” reorder the work. Put finality ahead of flourish. Put options ahead of apologies. Put context ahead of ticket numbers. Make the human lane great and rare. The rest of your brand will take care of itself.

If you’re new here and want a sense of my background and what I’m building, the About page has more.

Closing

The next decade won’t be won by companies with the prettiest booking. It’ll be won by the ones that show up on the traveller’s worst day with calm, clear action—and then quietly make sure tomorrow goes better. That’s the work I care about.

Get in touch →

Continue the conversation
Have a travel systems problem like this? I’d love to help.