I cleared a big chunk of my to-do list once.
Felt good for about a day.
By the end of the next day it was full again, like the space had never existed.
That used to bother me. Now I think it's the whole point.
Recently I was on a train, reviewing some workforce data on my laptop, half-watching the scenery blur past.
I'd been wanting to look at it for days, and the train was finally a quiet enough stretch of time to do it properly.
I went in expecting one thing. Confirmation. I'd been sensing, for a while, that people around me were stretched thin, and I assumed the data would simply agree with what I already suspected.
It didn't. Not exactly.
Some of it lined up. Some of it didn't. And the parts that didn't line up turned out to be far more interesting than the parts that did.
When I actually sat with the numbers, something didn't match.
On paper, most people weren't overloaded in the way I expected. The math, once you accounted for everything fairly, said there was room.
But in conversation, in the open-ended comments, in the things people typed in their own words, a different story showed up. People described feeling stretched. Overwhelmed. Like there wasn't enough of them to go around.
Both of those things were true at the same time.
That contradiction sat with me longer than either number on its own would have. Because it raised a question I hadn't expected to be asking: were we even measuring the right thing?
I started wondering if some of what people were calling overload wasn't really about the amount of work at all. It was about the shape of it. Constant small interruptions. Switching between five different things before lunch. Spending most of a day responding to other people instead of doing the work that was actually theirs to do.
None of that shows up cleanly in a spreadsheet. But it shows up everywhere else.
I noticed something similar happening in myself around the same time.
It was a hard week. New responsibilities I was still learning. Decks due for meetings that mattered. Regular work stacking on top of all of it. A couple of things slipped a day or two late, nothing dramatic, just enough to feel the weight.
And people around me started naming it before I did.
"You're so busy." "You have so much on your plate."
I heard some version of that more than once, and I noticed how quickly it started to settle into me, like hearing it enough times made it more true.
I almost said it myself.
I'm overloaded.
I didn't.
Here's something I believe and say often, to my kids, and to myself.
What you tell yourself becomes true.
Not because saying it makes it real, but because once you say it, you start acting like it already is.
So I've learned to be careful about which labels I let in, even the well-meaning ones other people hand me. Just because someone else names how I look from the outside doesn't mean I have to accept it as the truth of how I am on the inside.
Late one night, still working, I told myself something different instead.
We're not doing this again.
Not the lateness.
Not the version of me that lets everything pile up until it's loud.
And underneath that, a quieter realization:
All I have to do is my best.
If my best hits a deadline, that's what you get.
It won't always be the version I pictured in my head.
But if I gave it everything I had, I have to be okay with that.
That sounds simple written down.
It did not feel simple at the time.
That's the moment I keep coming back to.
Not the week itself, but what happened right after it.
I caught up.
Cleared a real chunk off my list.
Felt that brief, satisfying lightness you get when something heavy finally lifts.
It didn't last.
By the next day the list was full again, like the space had never opened up at all.
I used to read that as a problem to solve.
Now I read it as information.
The work is not going to stop.
It was never going to stop.
There is no version of this job, or probably any job worth having, where the list reaches zero and stays there.
If it did, that might mean we'd stopped growing.
Stopped being trusted with more.
Stopped being given the opportunity to provide value and make an impact.
So if finishing everything was never actually possible, the real question becomes different.
Not how do I get to empty.
How do I decide, every day, what actually deserves my attention?
Because attention might be the real currency here, more than time.
Anyone can technically be present for eight hours.
Far fewer people can give something their full, undivided focus for even one.
And the work that actually requires that kind of focus, the specialized thinking we were brought in to do, the thing that's genuinely ours to offer, is the first casualty when the day gets crowded.
Once I started seeing it that way, I had to redesign how I actually moved through a day.
Not by department.
Not by project.
By mode.
I think of it almost like driving.
The highway
Fast, focused, high intensity. No room for distraction because everything is moving at speed. That's where I build and execute, where the actual work gets done. Decks, reports, system updates, the things that require real momentum once I'm in them.
The city
Buses, subways, rideshares. You're moving toward something, but you're also constantly interacting with people along the way. Some of it you want. Some of it pulls your attention somewhere you didn't plan to go. Nobody expects to draft a real strategy in the back of a cab, and I stopped expecting that of myself too. That's where communication lives — email, follow-ups, quick check-ins. Necessary, but a different kind of driving entirely.
The country road
Early morning, top down, nobody else out yet. Quiet enough that my mind can actually wander somewhere useful. That's where thinking happens, before anyone else is awake to interrupt it. It's protected not because I block it on a calendar, but because the road is genuinely empty at that hour.
There's a reason separating these matters as much as it does.
Researchers at UC Irvine found it can take over twenty minutes to fully refocus after a single interruption, and some studies put the broader cost of switching between unrelated tasks as high as 40 percent of a person's productive time in a day.
Every time we switch lanes without intention — highway to city to country road and back again — there's a silent, invisible toll being charged against our attention.
We rarely see it being paid.
We just feel poorer by the end of the day.
So I stopped switching without intention.
I batch what belongs together.
Two decks due around the same time get built in the same sitting, because I'm already in that headspace.
Emails get drafted the evening before and sent in a single window the next morning, not answered piecemeal every time something lands.
And whatever doesn't fit anywhere yet — an idea, a deprioritized ask, something real but not urgent — goes into what I've started calling the parking lot.
Not lost.
Just not blocking the road right now.
None of this makes the list shorter.
It just makes the driving make sense.
I think about that day on the train, and the chunk of my list that refilled itself within twenty-four hours, and I keep landing in the same place.
We're afraid of the list never ending.
We treat it like evidence that something is broken.
That we're behind.
That we're failing to keep up.
But maybe that fear is pointed at the wrong thing.
The first time we do anything, it's rough.
The second time, we already know more than we did.
The tenth time, we're somewhere we couldn't have gotten to any other way.
A list that never empties isn't proof we're failing to keep up.
It's proof we're still in motion.
That's not a flaw in the system.
That's the system working exactly as it should.
Nothing is ever really finished.
Not the list. Not the role.
Not the version of ourselves we're building.
And I've started to think that's not the bad news.
It's the invitation.
The work that lights you up was never going to run out.
It's just going to keep asking more of you, in ways you couldn't have predicted from where you're standing right now.
What would change if we stopped waiting for the list to end, and started paying attention to who we're becoming while it doesn't?

