For a few years, I kept a list. Not a formal one, no spreadsheet or app, but a running mental tally of places I needed to see: the pyramids, Machu Picchu, the Northern Lights, Angkor Wat, Petra. Every trip I planned got measured against that list, and every country I crossed off felt like progress toward some finish line I never quite defined. I don't remember exactly when I started keeping it, but I remember exactly when I stopped, and it wasn't a dramatic moment — it was a fairly ordinary afternoon in a town in northern Vietnam that wasn't on any list at all.
The Trip That Broke the Pattern
I'd gone to Ha Giang because a friend mentioned the drive was supposed to be good, not because it appeared on any ranked list of things to do in Vietnam before you die. The plan was loose: rent a motorbike, follow the loop, see what happened. On the second day, the bike broke down outside a small village, and while I waited for a local mechanic to find the part, an older woman running a roadside stall waved me over, sat me down, and fed me a bowl of noodles while her grandson practiced English phrases on me with the kind of fearless enthusiasm only a seven-year-old can manage. I ended up staying three hours longer than planned. Nothing about that afternoon would show up in a listicle. There was no photo I took that would perform well anywhere. And it's the single clearest memory I have from two months of travel that year — clearer than the temples, clearer than the coastline, clearer than anything I'd actually gone looking for.
What Bucket Lists Actually Optimize For
I think the problem with a bucket list isn't the destinations on it — Machu Picchu earned its reputation honestly, and I don't regret seeing it. The problem is what the list quietly trains you to optimize for. A list rewards breadth over depth, arrival over experience, and the photographable over the memorable. It turns travel into a completion mechanic, and completion mechanics are satisfying in exactly the way a video game achievement is satisfying — a small dopamine hit, a checkmark, and then an immediate pivot to the next target rather than any inclination to sit with what you just did. I noticed I was spending less time actually looking at things and more time confirming I'd looked at them: photo taken, box checked, on to the next stop on the itinerary. The bucket list doesn't ask you to be present. It asks you to be thorough.
The Places That Stay With You Rarely Announce Themselves
Every traveler I've talked to who's been doing this long enough has some version of the Ha Giang story — a place that wasn't the plan, a detour that became the point. A wrong turn in Lisbon that led to a neighborhood restaurant with no sign and no menu in English. A rained-out day in the Scottish Highlands spent entirely in a pub listening to a stranger's family history. A flight delay in a city you'd never chosen to visit that turned into an accidental favorite. These moments share a structure: they weren't planned for, weren't optimized for, and weren't measured against anything. They happened in the gap between the itinerary items, and that gap is exactly what a bucket list has no room for, because a bucket list is, by definition, a list of destinations, and destinations are not where most of the actual texture of travel lives.
What I Do Instead Now
I still go to famous places. I'm not arguing for some purist position where popularity disqualifies a destination — that's its own kind of performance, just inverted. What changed is how I plan around them. I build in slack, deliberately, the way you'd build slack into any schedule you actually expect to enjoy rather than survive. I stay longer in fewer places instead of shorter in more, which sounds obvious written down but took me years to actually practice, because leaving a country early feels like leaving value on the table when you're thinking in checklist terms. I ask people who live somewhere what they'd do on a free afternoon, rather than what I should see, because those are almost always different answers and the second one is usually better. And I've stopped treating a trip as unsuccessful if I didn't see everything the guidebook flagged as essential — a genuinely good trip, I've come to think, is one where you leave wanting to come back, not one where you leave having finished.
The List Isn't the Enemy, the Framing Is
I don't think there's anything wrong with wanting to see specific places — wanting to stand at the rim of the Grand Canyon or watch the sun rise over Bagan's temples is a completely legitimate desire, and I still have my own version of that list tucked somewhere in the back of my head. What I've tried to unlearn is the framing that turns those desires into a scoreboard, where the value of a trip gets measured by how many named things you saw rather than how much of it you actually experienced. The bucket list treats travel as an inventory problem — how many items can I acquire before I run out of time — when the thing that actually makes travel worth doing has very little to do with inventory. It's the noodles in Ha Giang. It's the stranger's family history in a Highland pub. It's the version of a place that only shows up once you stop performing your way through it and let yourself get mildly, productively lost instead.
A Different Kind of Ambition
These days, when people ask me for travel advice, I try to give them permission rather than a list: permission to skip the thing everyone says you have to see if it's not actually calling to you, permission to spend an entire day doing very little in a place you like, permission to let a trip go somewhere the itinerary didn't account for. That's a harder kind of ambition to hold onto than "see everything," because it doesn't come with a visible scoreboard — nobody's impressed that you spent an unplanned afternoon eating noodles with a stranger's grandmother. But a decade into this, it's the only kind of travel ambition that's actually made the trips themselves better, and it's the only list I've kept that I've never once felt the need to finish.