For years my trips followed the same basic shape: land somewhere, cover as much ground as the schedule allowed, move on before the jet lag had fully cleared. A ten-day trip to a region usually meant four or five cities, each one a rushed highlight reel rather than an actual visit. The trip that broke that habit wasn't a grand realization so much as an accident of logistics — a flight cancellation that stranded me in Oaxaca City for ten days instead of the two I'd planned, with nowhere else on the itinerary left to salvage. It turned into one of the best trips I've taken, and it's changed how I plan almost every trip since.
The Math of Multi-City Itineraries
A typical multi-city itinerary loses more time to logistics than most travelers account for when they're building it. Every city change costs the better part of a day once you count checkout, transit to the airport or station, the journey itself, arrival, check-in, and the disoriented first few hours of figuring out a new place well enough to function in it. A five-city, ten-day trip can easily burn three or four of those days on logistics alone, leaving something closer to six productive days spread across five places rather than concentrated in one — an average of barely a day per stop once travel time is subtracted, which is enough to see a handful of landmarks and almost nothing else.
What Ten Days in One City Actually Buys You
The unplanned week in Oaxaca gave me something a rushed itinerary never had: enough time to develop an actual routine. By day three I had a coffee place, and the woman who ran it had started having my order ready before I finished ordering it. By day five I'd found a mezcal bar three streets back from the tourist zone with no sign and no menu, recommended by the coffee place owner, where I ended up back four more times. By day eight I could walk from my rental to the Zócalo without checking a map, a small thing that nonetheless marks a genuinely different relationship to a place than the one you have when you're still consulting directions on day two of a two-day stay. None of this shows up on a highlight list of things to do in Oaxaca. All of it is the actual texture of what makes a place feel like somewhere you've been, rather than somewhere you've passed through.
You See the Same Places Differently
Visiting a major site once, in a single rushed pass, gives you one version of it — usually the crowded, midday, everyone-else-is-here-too version, since that's when a tight itinerary usually has you passing through. Staying in one place long enough to visit somewhere multiple times, at different hours and in different moods, reveals how much a single visit actually distorts a place. Santo Domingo church in Oaxaca at the golden-hour rush of a first-timer's itinerary is a beautiful building crowded with photographers; the same church on an ordinary Tuesday morning, with nowhere else to be and no photo quota to fill, is a completely different experience — quiet, half-empty, and considerably more affecting for it. A rushed trip doesn't have room for a second visit to anything. A slow one does, and the difference in what you actually come away with is larger than it sounds.
The Restaurants You'd Never Otherwise Find
Restaurant discovery on a short visit almost always defaults to whatever ranks highest on a search or gets recommended most often, which produces a reasonably good but fairly predictable set of meals clustered around the same well-reviewed handful of places everyone else is also eating at. Ten days gives you time to work through that initial list and then keep going once it's exhausted — asking the coffee place owner, asking the mezcal bartender, asking a stranger at the market who's clearly a regular rather than a tourist. Some of the best meals of that Oaxaca trip came from places with no online presence at all, recommended verbally by someone I'd built enough of a rapport with, over several days, to ask. That kind of recommendation simply isn't available to a two-day visitor moving too fast to become a recognizable face anywhere.
The Case for Boredom
A slower trip inevitably includes stretches of unstructured time that a packed multi-city itinerary is specifically designed to eliminate — an afternoon with nothing planned, an evening with no reservation, a morning where the obvious tourist activities have all been done and nothing new presents itself. These stretches feel, in the moment, like wasted time, and the instinct on a tightly scheduled trip is to treat any gap as something to fill. But unstructured time is exactly when the unplanned, unlisted experiences happen — the wrong turn that leads somewhere interesting, the conversation that only starts because you're sitting somewhere long enough for someone to strike one up, the afternoon nap that leaves you rested enough to actually enjoy the evening instead of running on fumes. A little boredom, it turns out, is doing real work.
When Multi-City Trips Still Make Sense
None of this is an argument that every trip should collapse into a single city — some regions genuinely reward covering more ground, particularly on a first visit to an unfamiliar country where the goal is orientation rather than depth, or when the specific sites that matter to you are simply spread across real distance with no way around it. A first trip to Japan covering Tokyo, Kyoto, and Osaka makes sense precisely because you don't yet know which of the three you'd want to return to for a slower, deeper visit. The distinction worth drawing isn't "multi-city trips are wrong" but "not every trip needs to maximize ground covered," and recognizing when you're defaulting to a packed, many-stop itinerary out of habit rather than because the destination actually calls for it.
How I Plan Differently Now
The practical change since that accidental week in Oaxaca has been simple: on any trip longer than a week, I now deliberately build in at least one multi-day stretch in a single place with no planned activities for at least half the days, treating unstructured time as a real part of the itinerary rather than a scheduling failure to be filled. It produces trips that look, on paper, less impressive — fewer countries, fewer cities, fewer photographed landmarks per day — and that consistently turn out to be the ones I remember most specifically a year later. The itinerary that covers the most ground is rarely the one that produces the most vivid memories; more often it's the slower one, the one that gave a single place enough time to stop being a destination and start being, briefly, somewhere you actually lived.