What Traveling Reminded Me About Systems

I came to Seoul to travel, not to study systems.

But once you spend enough time building things, it becomes difficult to turn that part of your brain off. You start noticing how things work. Not just the surface experience, but the structure behind it. The steps someone designed. The assumptions that shaped the process.

Over the past few weeks here, I’ve caught myself paying attention to small operational details in places most people would probably ignore. A cafe’s ordering flow. How people move through a store. The way self-service machines guide customers through a task.

Some of these systems are impressively efficient.

Others are surprisingly inefficient.

Both are interesting.

Because every system reveals something about the thinking behind it.

One example that stood out to me was something simple: the ramen stations along the Han River.

You walk into a convenience store, grab a packet of ramen, and they give you a bowl. Outside, there’s a cooking machine. You scan the bowl, and the machine automatically measures the weight, fills it with water, and begins boiling.

Within a few minutes, you have freshly cooked ramen without needing instructions or staff assistance.

The experience feels natural, almost obvious. But it only feels that way because someone carefully designed the process. The system anticipates what the user wants to do and removes unnecessary decisions along the way.

From a builder’s perspective, that kind of design is satisfying to see. The complexity is still there, but it’s hidden behind a flow that makes the interaction feel simple.

Good systems often work this way. When they’re well designed, you barely notice them.

The opposite situation is just as revealing.

Now and then, I’ll walk into a place where the workflow feels oddly complicated. Extra steps. Staff are doing tasks manually that could easily be automated. Small delays that seem unnecessary.

When that happens, I start wondering why.

Sometimes the reason is cost. Sometimes it’s tradition. Sometimes the system simply evolved over time, and no one has stepped back to redesign it.

In software, we often refer to this as legacy complexity. Processes accumulate layers over time, and eventually, the workflow becomes heavier than it needs to be.

The same thing happens in physical businesses.

Travel has a strange way of sharpening your awareness of systems because you’re constantly encountering unfamiliar environments. When everything around you is new, you naturally pay closer attention to how things work.

Transportation systems, ordering kiosks, cafe layouts, ticket machines, and checkout flows all start to look like small product designs.

You begin to see experiences not just as moments, but as sequences.

-How does someone enter the system?

-What decisions do they need to make?

-Where might they hesitate?

-What part of the process creates friction?

These are the same questions builders ask when designing software.

The most impressive systems I’ve encountered here share a similar quality: they respect the user’s time.

They assume the user doesn’t want unnecessary complexity. They guide people through the experience with clarity instead of forcing them to figure things out.

When that happens, the system becomes almost invisible.

Things simply work.

And when things work smoothly, people rarely stop to think about the design behind it.

But for builders, those moments are fascinating.

Because behind every efficient system is someone who once asked a simple question:

How could this be simpler?

-Surukode