the weekend build that isn't a build at all

saturday, and i've been sitting with a distinction that took me longer than it should have to actually internalize: the difference between recovery and avoidance. they can look identical from the outside, both involve stepping away from the work, but they come from completely different places internally.

recovery is chosen. it's a deliberate decision that the system needs the walk, the sauna, the unhurried time with the kids, in order to keep operating at the level the mission requires. avoidance is reactive. it's stepping away because something felt hard or uncomfortable to face, dressed up in the language of rest so it doesn't feel like what it actually is.

the tell, for me, is how i feel afterward. real recovery leaves me sharper and more present when i come back to the work. avoidance leaves a residue, a low hum of something unresolved waiting for monday, because the thing i stepped away from didn't actually get smaller while i was gone, it just got postponed.

this matters more the bigger the stakes get. it's easy to justify avoidance when the thing being avoided is small. it's much more costly, and much easier to rationalize, when the thing being avoided is a hard conversation with a partner, a decision about a deal that isn't working, a number in the business that isn't where it should be. those don't resolve themselves over a weekend of avoidance. they just wait, quietly, until they're bigger.

the practice i've settled into is a simple gut check before the weekend starts: is there anything i'm stepping away from because i need the rest, or because i don't want to look at it. naming the difference honestly, even just to myself, changes what the rest of the weekend actually does for me.

when you step away this weekend, will it be recovery, or is something quietly waiting for you to come back to it?