For about three years I treated my weekends like a project. Not in a corporate, time-blocked way — I'm not that person — but in a softer, more insidious way. I tried to "use" the weekends well. I tried to recover properly from the week. I tried to do the right number of social things and the right number of solo things. I tracked my sleep, sort of. I had a vague mental scoring system for whether the weekend had been "good" or "wasted." I would, on Sunday evening, do a small unconscious accounting of how restored I felt, and the answer was almost always: less than I should have, given how carefully I'd planned this.
I was, in essence, working on my rest. The thing I'd been told to optimize for — being properly recovered, properly present, properly ready for the next week — had become its own kind of labor. By the time I noticed this, the weekends were running on the same anxious operating system as the weekdays. Just with different content.
This essay is about what happened when I stopped doing that. It is not a productivity essay in disguise. It is just an honest report on a small but real change.
What I'd been doing, in retrospect
Here is what an "optimized" weekend looked like, in my version of it:
Saturday morning: a long walk, ideally including some kind of nature, ideally without earbuds. A "real" breakfast, slowly cooked. Reading. A planned activity in the afternoon — a museum, a friend's place, a coffee with someone I hadn't seen. A quiet evening at home with my partner, ideally a meal we cooked together, no screens after a certain hour. Sunday similar but slightly slower. A few hours on a creative project. Some kind of intentional recovery activity — a bath, a stretch, an unrushed cup of tea. Bed by ten.
None of those things were bad. Most of them were lovely. But the structure had become, without my quite noticing, a checklist. I was rating each weekend, by Sunday evening, against a model of how a weekend was supposed to go. If the long walk hadn't happened — if it had rained, or I'd been tired, or my partner had wanted to do something else — there was a small low-grade dissatisfaction that the weekend hadn't been "right." I had taken a thing that should have been the absence of work and quietly turned it into a domain in which I could fail.
The week the framework broke
I don't remember the exact week. Sometime last spring, I was tired in a way the optimized weekend couldn't fix. I had slept fine. I had eaten fine. I had done all the right things. But Monday morning came and I was still tired in some other way that the framework wasn't reaching. Sunday evening, sitting on the couch, I noticed that the weekend's planned recovery activities had felt as much like obligations as the work week's emails. The walk had been a thing I had to do. The bath had been a thing I had to do. Even the tea, ridiculously, had been a thing I had to do.
The thing I had not done, all weekend, was anything I actually felt like doing in the moment. I had done the things I had decided, the previous Sunday, would be restorative. The decisions had been pretty good ones. But by the time the moment arrived, the decision had calcified into a plan, and the plan had calcified into a schedule, and the schedule had stripped most of the restoration out of any of it.
I had taken a thing that should have been the absence of work and quietly turned it into a domain in which I could fail.
What I tried instead
The next weekend I did almost nothing. I had been planning, in some background tab of my mind, to "optimize" the weekend — meaning, again, the long walk, the slow breakfast, the museum visit. Instead I sat on the couch and read for three hours. I made eggs at noon, which is not breakfast or lunch. I went outside, briefly, but not for a walk. I watched part of a movie and then turned it off because I was bored. I called a friend, briefly, then hung up because she was busy. I made dinner from things that were already in the fridge.
By Sunday evening I felt better than I had in weeks.
This was, I'll be honest, mildly horrifying. I had been doing the elaborate version of weekend recovery for three years. I had read books about rest. I had, briefly, used a sleep-tracking app. I had genuinely believed that my weekends were a finely tuned recovery instrument that I was, against odds, executing correctly. And the weekend that worked was the one in which I more or less did nothing on purpose.
I want to be careful about what I'm saying here, because "do nothing" is its own brand of advice now, and I don't really mean it in the trendy sense. What I mean is something more specific: I stopped imposing a structure on the time and let the time fill itself in.
What I think happens when rest is "designed"
I have a theory about this now and I'll try to state it clearly. Rest, when it is designed in advance, becomes another kind of execution. The mind, even on the weekend, stays in the mode of completing tasks against a plan. Even if the tasks are pleasant tasks — long walks, slow meals, baths — the underlying mental motion is the same one that exhausted me at work all week. The motion of moving through a list. The motion of evaluating, at the end of each segment, whether I am on track.
That motion is, I now think, the actual exhaustion. Not the work itself. The constant background process of checking yourself against an internal plan. When the weekend has its own plan, the process never stops. It just changes its content.
What letting the weekend be undesigned does, by contrast, is shut down that process for forty-eight hours. The mind has nothing to check itself against. It does what it wants, badly. It reads for three hours and then can't focus and watches a stupid show. It sleeps in until eleven. It eats lunch at four. None of this is restorative according to anyone's framework. All of it, somehow, restores me. I think because none of it engages the part of me that is tired.
How I do weekends now
I will not turn this into a method. The whole point is that there isn't one. But, briefly:
I make almost no plans before Saturday morning. If a plan needs to be on the calendar, I make sure it doesn't dominate the day. I don't track anything about the weekends. I don't decide, in advance, what counts as restorative. I let the days be what they end up being. Some of them are slow and lovely. Some of them are weirdly unproductive in a way I would have flagged, three years ago, as "wasted." I have stopped flagging anything as wasted.
I am, on average, more rested. I am, on average, more present at the things I do choose to do during the week. I have published more, not less, since I gave up trying to design my weekends, which is funny if you know how seriously I'd taken the recovery framework.
This is, I think, the single largest under-the-radar shift I've made in the last few years. Not a habit added. A habit removed. The habit of treating rest as something I had to be good at. Rest does not, it turns out, want to be optimized. It just wants to be allowed. The weekends I let alone are, by some quiet margin, the weekends that work.