Most rushed trips are not ruined by seeing too little.
They are ruined by changing hotels too often.
A place can look easy to add on a map and still cost you half a day in real life. Before I add a city to an itinerary, I make it pass these three tests.
1. Does it give me a better evening or morning?
This is the simplest test for deciding between a day trip and an overnight.
Nara is an easy day trip from Kyoto for most first trips. You can see the main sights, have lunch, and return without packing again.
Miyajima is different. Staying overnight gives you a quieter evening and early morning after the day visitors have left. That is the value of staying.
Hoi An is similar. The lantern-lit evening and slower morning are part of the experience, not just an extra stop on the map.
2. What does the move really cost me?
Do not count only the train or flight time.
Count packing, checking out, getting to the station, finding the hotel, leaving your bags, waiting to check in, then getting settled.
A journey that looks short on Google Maps can still take most of an afternoon.
If moving hotels means losing a good afternoon in Tokyo, Kyoto, Hanoi, or anywhere else, the new stop needs to earn that time back.
3. Does it improve the route or create backtracking?
Here is a quick example from a seven-night Japan trip.
More rushed
Tokyo, 3 nights → Hakone, 1 night → Kyoto, 2 nights → Osaka, 1 night
Usually calmer
Tokyo, 3 nights → Hakone, 1 night → Kyoto, 3 nights
You can still visit Osaka from Kyoto without another check-in, another suitcase day, and another night spent settling into a hotel.
My rule is simple:
If a place does not give you a better evening, a better morning, or a better route, it probably does not need its own hotel.
Reply and tell me the place you are currently debating between a day trip and an overnight. I will include a few of the most useful answers in a future issue.