Travel

Travel Makes Me Notice Things I Miss Behind a Screen

Signs, maps, tickets, menus, check-in and tourist apps: on the road I'm a user with no prior knowledge. What good signage and a good website have in common.

The Dancing House and the street life of Prague
Prague, a moment from the road.

When I travel, I can't stop noticing how things are made. Signs at the airport, the map at the station, the ticket that has to be validated somewhere, the menu in a restaurant, the app I'm supposed to book a ticket through. I didn't come to look at any of that. And yet with every one of these things I notice whether it helped me or stopped me.

Behind a computer I often don't see these things. I'm too close. I know what a button means because I built it. On the road I'm a user with no prior knowledge, in a foreign language, with limited time and a poor connection. It's the best usability test I know, and nobody charged me for it.

This isn't a travelogue. It's a note on what the physical world teaches me about the digital one.

A good sign and a good website have something in common

At a good station I don't think about where to go. An arrow, a name, a colour, and my feet go on their own. At a bad station I stand, read, compare, go back. The difference isn't how much information is on the sign. The difference is whether someone thought about the question I have at that moment.

The same goes for a website. A visitor shouldn't have to think about what the designer meant to say. If they have to guess what a button means, where a link leads or why something is hidden in a menu, the site was made for the person who built it, not the person who uses it.

That sounds obvious. On the road I see how rarely it's done.

Orientation: where am I and where am I going

The first thing I need in a new place is an answer to two questions: where am I, and where am I going. A good map has the point where I'm standing marked, and the direction I'm facing. A bad map is beautiful and completely useless, because I first have to rotate it in my head.

Websites have the same problem. A visitor who arrives from a search engine on a subpage doesn't know where they are. Breadcrumbs, a clear heading, visible navigation and a logical next step are the digital version of the marked point on the map. When they're missing, the visitor does what I do in front of a bad map: stands, reads, goes back.

Naming: words the user knows

At airports I'm surprised again and again by how differently the same things are named. One place says exit, another says gate, a third uses an abbreviation the staff know. When I'm tired and in a hurry, every such difference is a second of doubt.

On websites this happens when sections are named after the company's internal organisation. Solutions, services, products, offer: four words for the same thing that don't tell the visitor where what they're looking for is. Good naming uses the words the visitor would use, not the words in the org chart.

Tickets, bookings and forms

A pattern I recognise instantly on the road: a ticket app demands an account, an e-mail confirmation, choosing a country, and then choosing again the city that was already entered. If the connection drops in between, it starts from the beginning. The ticket costs a few euros; the process costs a quarter of an hour and some patience.

That's exactly what web forms do to site owners every day, except the owner doesn't see it. They see the number of submitted forms; they don't see the people who gave up at step two. On the road that person is me, and I remember well where I gave up.

The rules I take from this are simple. Don't require an account for something that can be done without one. Don't ask twice. Keep the entered data on an error. Say what happened after submission. That doesn't only apply to tickets.

Menus and prices

A restaurant menu is an interesting example of information architecture. A good menu has clear groups, understandable descriptions and a price next to every dish. A bad menu has poetic titles, no descriptions, prices on another page or none at all.

Service websites behave similarly. "Complete solutions" without a description is the poetic title of a dish. A price that appears nowhere is a menu without prices: some guests will ask, most will move on. Where a price can't be stated, it's at least possible to say how it comes about. That's better than silence.

The menu teaches me something about order, too. A good menu first says what it is, then what it's made of, and only then how much it costs. Websites like to start with the last, or the price never arrives at all. The order of information isn't a trifle; it's the answer to the question of what the visitor needs first.

Check-in and moments of waiting

Checking in for a flight or at a hotel, I watch how the system handles waiting. Do I know something is happening? Do I know how long it will take? Do I know what to do if it gets stuck? Good systems answer these questions without my asking. Bad ones leave me in front of a screen that doesn't move.

On the web, that's the moment after clicking a button. If nothing visible happens, the user clicks again, and now we have two orders or none. Feedback isn't decoration; it's the answer to the question "did anything happen", which the user asks every time.

Tourist websites and apps

Tourist websites are a chapter of their own. They're often beautiful, with photos that can't be shrunk, and with the information I actually need hidden three clicks down. Opening hours, ticket price, how to get there, whether I need to book. Those are the four questions every visitor asks, and a site that doesn't answer them on the first screen has missed its purpose.

City and attraction apps have a different problem: they require installation for something I'll use once. I wrote separately about when an app makes sense; on the road the question becomes very concrete. A website that works on a phone would be enough for me in most cases.

A language I don't understand

The most instructive part of travelling is using things in a language I don't speak. Then all I have left is shape, icons, position and colour. If the system works even then, it's well designed. If it falls apart the moment I don't understand the words, it was relying on my reading.

That's also an accessibility test I rarely do at my own screen. A user who doesn't understand the language is in a similar position to one who sees poorly, reads fast or uses a screen reader: they need structure, not ornament. A button that looks like a button. An error that's marked as an error, not merely coloured red. An order that follows the task.

When I come back, I look at my own pages with the same question: would someone who doesn't read the text understand them? The answer is often less comfortable than I'd like.

A poor connection as a benchmark

On the road the connection is often poor or absent. Then I see which sites and apps were made for real conditions and which for an office with fibre. A site that loads five megabytes of images before showing the opening hours doesn't exist at a station with no signal.

For work at home, that's a good reminder. A visitor looking for a piece of information often has one bar of signal and a few seconds of patience. Speed isn't a technical detail; it's the condition for the conversation to happen at all.

What I bring home

From every trip I bring a few notes that have nothing to do with the place. Signs that worked. Forms that didn't. Moments when I got lost, and why. When I get back to my work, I compare these notes with what I build myself.

Most often I find the same thing: I hadn't thought about the person who arrives for the first time. I know where things are because I put them there. The user doesn't know, and doesn't need to. Their question is the same as mine at a foreign station: where am I, where am I going, and what should I do now.

If the site answers that without making them think, it's built well. If not, it doesn't matter how beautiful it is. Travel teaches me that every time, and every time I forget it somewhere, until I'm standing in front of a sign again that tells me nothing.

Photo of the author

I build web solutions and digital products. At GE-KO I work on web design, development and SEO; with Bizko I look for simpler ways through everyday business. I am interested in how technology saves people work, and in how AI is changing the web.

One step further.