I was maybe two miles in when I figured out the thing I’d been stuck on for two days.
Not because I was thinking about it. I was at Fall Creek Falls in Tennessee, trying not to roll my ankle on a wet root, watching the biggest waterfall I’ve ever seen pour off a cliff into a gorge below. The waterfall is 256 feet. The gorge does not care about your problems. Neither, for those two hours, did I.
That’s probably why it worked.
I’ve had this happen enough times now that I’ve started paying attention to it. Some of my best solutions — the ones that actually untangle something real, not just the obvious next step — showed up while I was doing something completely unrelated to the problem. Driving. Showering. Apparently hiking in Tennessee.
For a long time I wrote this off as coincidence. Just the way brains are. But I think there’s something more deliberate to it, and once you see it, you can actually use it.
When you’re too close to something, focused work stops helping. You’re not making progress — you’re reinforcing the same dead-end path you’ve already worn into the ground. More hours doesn’t fix this. Sleeping on it doesn’t really fix it either, at least not if you lie there running the same loop at lower volume.
What actually helps is putting your brain somewhere else. Somewhere it has to genuinely engage — not scroll, not half-work, not stare at a different screen. Somewhere the foreground is busy enough that the background can run without interference.
The background is the part people miss. Your brain keeps working on the problem when you stop staring at it. It just works differently — less focused, more connective. Pulling in things you read a while back, patterns from other contexts, angles you couldn’t see when you were nose-to-nose with it. The answer that shows up afterward usually feels obvious. That’s not a coincidence. It was obvious the whole time. You just needed a different view of it.
The part that changed how I work: this isn’t random. It’s a skill. You can get better at it.
You get better at recognizing the specific flavor of stuck that means “step away” versus “push through.” You get better at actually stepping away instead of doing the fake version — the scrolling, the browser tab loop, the meeting that doesn’t need you. And you get better at loading the problem clearly before you go, so your background processes have something real to work with.
The side effect is that the work/life tradeoff starts to feel less like a tradeoff. The hike isn’t what you get when the work is done. The hike is part of the work. You stop counting hours away from the desk as time stolen from productivity and start treating them as a different kind of input.
I got back to the keyboard Monday morning with one fewer problem than I’d left with Friday.