The Overnight Bus to Nowhere

The bus left Cusco at nine at night and was supposed to arrive at six. It arrived at eleven the next morning, which everyone except me seemed to have expected.

There was no signal for most of it. Not weak signal. None. The phone became a clock and then, once the battery went, not even that.

I have done a lot of deliberate focus work. Blocked calendars, notifications off, the whole apparatus. None of it has ever produced what fourteen hours on that bus produced, and I have thought since about why.

The difference between choosing and not having

When you turn off notifications, the option remains. You know you could check. Some part of your attention stays allocated to not checking, and that allocation is the cost. It is why an afternoon of deep work still feels like effort.

On the bus there was no option. Not restraint, absence. Within about two hours something released that I had not known was held, and my thinking changed shape. Longer. Less jumpy. I followed one problem for what must have been ninety minutes without the reflex to look something up.

The reflex to look something up is the thing I did not know I had.

What actually got solved

A pricing structure I had been circling for months. Not because I had a flash of insight, but because I had enough uninterrupted time to follow the bad versions all the way to why they were bad, which is a slow process that any interruption resets.

Three of the four versions I had been considering died on that bus, and they died for reasons I could not have reached in a forty-minute block. Each one needed to be carried far enough to fail properly.

I wrote none of it down until morning. It was all still there, which told me something about how much of what I normally capture is capture-anxiety rather than memory failure.

Each bad idea needed to be carried far enough to fail properly. A forty-minute block cannot do that.

What the fourteen hours were actually like

I want to be honest that most of it was not profound. The first two hours were irritation. I checked a dead phone four times out of pure reflex, which is a humiliating thing to notice about yourself.

Somewhere around Abancay the road turned into a sequence of switchbacks and the man across the aisle shared a bag of dried corn without either of us having a language in common. That took twenty minutes and required nothing from me. I think that stretch mattered more than it looks, because it was the point where I stopped treating the time as an obstacle between two places.

After that the thinking started, and it did not feel like effort. It felt like the state you get an hour into a long walk, where the problem is turning over on its own and you are mostly watching.

I have chased that state with tools. Timers, focus apps, a noise machine, one memorable week of waking at five. None of it produced this. What produced it was fourteen hours in which nothing was expected of me and nothing could reach me.

The part I resist

The obvious lesson is to build this deliberately. Go somewhere without signal, on purpose, on a schedule.

I have tried and it does not work the same way. The manufactured version has an exit, and knowing the exit exists keeps a thread of attention on it. The bus worked because I could not have got off, and because the fourteen hours were not mine to spend, so there was no ledger running about whether I was using them well.

That last part might be the whole thing. The reason unstructured travel time produces thinking that scheduled thinking time does not is that nobody is measuring it, including you.

What I do now

I do not have a system. I have a preference: on any trip, take the slow option once. The train instead of the flight, the bus instead of the transfer, the long way around.

It costs hours that look wasted on the itinerary and it has returned more usable thinking than any productivity structure I have tried. Not because slow travel is romantic, but because it is the only remaining context where being unreachable is normal rather than a statement.

The pricing question that died on that bus eventually became a straightforward answer, and the reasoning is in SaaS pricing is a positioning decision.