The Work of Returning to Work

Coming back from vacation, the inbox is the easy part.

The hard part is invisible. It's remembering what I knew before I left.

Which questions were still open. Which problems were waiting on more information. Which conversations were unfinished. I was carrying a hundred small things without even realizing I was carrying them.

Then I left.

When I came back, the work was still there. But the context around it had faded.

The first few days back aren't really about getting things done. They're about reconstruction. Rereading old messages. Digging through notes. Opening a project I was halfway through and trying to remember what I was even doing. Why this decision mattered. Why I left that thing unfinished.

It turns out a lot of knowledge work runs on context you don't realize you are carrying. And the moment you step away, that context starts to evaporate.

You notice this especially with systems: a script, a workflow, a page of documentation. While you're working on it, the logic feels obvious. A few weeks later, you're squinting at your own choices like they belong to someone else.

Why is this field mapped this way? Why does this report exclude those records? Why did I add this one extra check?

The answers are usually in there somewhere, buried in old conversations, experiments, and mistakes I have mostly forgotten I made.

Coming back after time away makes something obvious: the finished thing is never the whole story.

A few lines of code. A diagram. A short note on a ticket. Small, clean, final.

But behind each one is a trail of decisions, wrong turns, and discoveries that nobody wrote down.

Coming back from vacation isn't just catching up on tasks.

It's catching up on your own thinking.