Chapter One: The Groundhog Day Traps
The alarm goes off at 7:45 AM.
You don’t get up right away. You reach for your phone, lying there on the nightstand, and start doing the exact same thing you did yesterday: clearing the screen.
There are thirty-something unread alerts waiting for you. Most of them are just white noise—"sounds good," "on it," thumbs-up emojis. But tucked between them are three items that actually require your brain. Someone wants to know where you got a specific data point for yesterday's report. Someone else is reminding you about a 10:00 AM meeting. Then there’s a direct message from a coworker that just says, "Hey, you free?"
You tap out a reply to the first one, pasting the link to the spreadsheet. You acknowledge the meeting reminder with a quick "See you there." You pause over the third one, wondering what they want, before typing, "Yeah, what's up?"
They reply instantly: "Oh, nothing major. Just making sure you’ll be in the office this afternoon."
"Yep, I'll be there," you write.
Next is email. Seventeen new messages since you went to sleep. Eleven are automated system notifications and newsletters you keep meaning to unsubscribe from. Three are threads where you’ve been CC’ed just so people can cover their bases. Two require a quick read before you archive them. One is a bottleneck—a project approval that's sitting on your desk, metaphorically speaking, waiting for you to click a button.
You open it, skim the details, decide it looks fine, and hit "Approve." Then you archive it and keep scrolling.
Fifteen minutes pass. The lock screen is clean. Everything has been read, handled, or acknowledged.
You finally slide out of bed to brush your teeth. Twenty minutes later you’re out the door, followed by a forty-minute commute to the office. You sit down, open your laptop, and log in.
There are eight new emails.
The chat app has a dozen new unread badges.
The person whose approval you cleared twenty minutes ago has already sent a follow-up, asking if you could "just double-check one more thing real quick" on a different part of the project.
You take a breath.
And you start over.
This isn't an exceptional day. It’s just how the days go now.
It’s not a temporary rush because of a big launch, and it’s not going to ease up when the quarter ends or when the team finally hires that extra person you've been asking for.
Tomorrow is going to look exactly like today.
The day after that, too.
You’ve reached a kind of fragile equilibrium where your speed at processing information matches the speed at which it hits you. It feels like being on a treadmill where someone else controls the dial. You have to keep your legs moving at this exact pace. Going faster doesn't mean you get to leave early; it just means you run in place harder. Going slower means you fall off.
Sometimes you try to beat the machine. You have a highly focused Tuesday where you blaze through the unread messages, organize your calendar, and even manage to read that long-term strategy document you’ve been ignoring for a month. You feel a rare spike of momentum. You think you might actually walk out the door at 5:00 PM.
Then, at 4:59 PM, a little gray box pops up in the corner of your screen: "Hey, one quick thing before you log off..."
You look at the text.
You know that whatever follows those words means you aren't leaving. Or if you do leave, the problem will just ride shotgun in your head all the way home. It will sit at the dinner table with you, hang around while you're trying to read or talk to your family, and pop back up during those quiet hours when you’re supposed to be resting.
It’s hard to describe this feeling to older people.
If you try, they usually say something like, "Well, that’s just a job. Everyone works hard. We used to stay late at the office too."
But they’re talking about a different kind of exhaustion. They’re measuring volume, not texture.
Work used to be mostly task-oriented. If you worked in a factory or a machine shop, your goal for the day might have been to finish five hundred parts. You made them, they sat on the pallet, and they were still there tomorrow. The effort left a physical footprint. It stayed in the world.
If you worked a piece of land, you cleared a field. The cleared field didn't secretly grow trees overnight while you slept. The work stayed done.
Information work doesn’t behave like that.
You spend three hours answering questions, clarifying details, and writing a comprehensive summary that lays out a solution to a recurring problem. Then, next Tuesday, someone else asks you the exact same question. The shared document you spent all afternoon updating gets overwritten by an older version because of a sync error. The alignment you achieved during a stressful afternoon meeting dissolves by the following week because people simply forgot what they agreed to.
You do the thing, it exists for a moment, and then it vanishes.
Then you do it again.
There’s an old psychology experiment involving Legos that comes to mind.
Researchers asked two groups of participants to build small plastic figures. For the first group, every time they finished a figure, the researcher took it and placed it under the table, promising they would all be kept together until the end. For the second group, the rules were slightly different. The moment they finished a figure, the researcher immediately began pulling it apart in front of them, tossing the bricks back into the bin for the participant to use for the next one.
Both groups were paid the same amount. Both groups were doing the exact same physical labor.
But the second group quit much earlier. They didn’t stop because their hands hurt; they stopped because the purpose had been drained out of the room. It’s an exhausting thing to watch your own hands build something that you know will be disassembled three seconds later.
Most office work feels like the second group, except the person dismantling the Lego structure is invisible.
You spend your days organizing chaos, smoothing over friction, and establishing order, only to watch the chaos seep back in by morning. No one is doing it maliciously. It’s just that the natural state of an office—and maybe the world—is a steady drift toward noise.
You don't see the hands tearing down your work. You just wake up and find yourself back at the starting line, wondering if you're the one who messed up.
Think about how a standard Wednesday actually functions.
You have a meeting at 10:00 AM. The invite says it’s an "alignment session" across three different teams. What that actually means is that Team A doesn’t know what Team B is building, Team B doesn’t understand Team C’s constraints, and Team C assumed Team A already knew something that Team A has never heard of.
You spend forty-five minutes walking everyone through the same timeline. People nod. Someone says, "Makes sense." Someone else says, "Glad we clarified that."
We like to think meetings are for making decisions, but mostly they’re just expensive ways to sync data. People gather in a room to lay their individual pieces of information on a table so everyone can look at the same reality for an hour.
It feels necessary while you're doing it, but it shouldn't be.
If there were a single, reliable place where every team’s status, blockers, and changes lived—and if people actually trusted it and read it—the meeting wouldn’t exist. Everyone would just know.
But that place doesn't exist. Or it exists, but nobody updates it. Or it’s updated, but nobody checks it. So you have to gather everyone together. You have to use your own voice to repeat the words. You have to watch their faces to make sure the information actually lands. You spend forty minutes buying yourself a temporary window of shared understanding.
Key word being temporary.
By next month, the drift happens again. Team A pivots a little without telling Team B; Team C loses track of a dependency because things moved too fast. And then you need another meeting to fix the alignment.
It's a loop that never really closes.
There's a reason so many teams have a mandatory "sync" every single Monday or Friday.
It’s an admission of failure, in a way. It’s a confession that over the course of five business days, information degrades so rapidly that people will inevitably end up working on three different versions of the same project if you don't drag them into a room to reset their compasses.
Those meetings aren't usually about moving forward. They're about clawing your way back to the baseline—figuring out what actually happened over the last week before you can even begin to talk about what happens next.
By the time you finish sorting out the past, everyone is too tired to think about the future anyway.
This constant need to re-verify things isn't confined to work, either. It leaks into your house.
You know where the extra trash bags are kept. You’ve lived in the same place for two years, and they’ve always been in the second drawer in the kitchen, inside the white container. But your partner still stands in the kitchen every few weeks, looking around, and asks, "Hey, where are the trash bags?"
You say, "Second drawer, on the left."
They say, "Oh, right."
Then, a month later, the exact same question.
You start to wonder if it's a communication issue. Did you say it wrong? Are they doing it on purpose?
Probably not. It’s just that their brain is already redlined by their own stream of inputs, deadlines, and minor details. The specific location of the trash bags is just one more low-priority data point buried under an avalanche of things they actually have to remember today.
They care about you, but their container is full.
Yours is too.
If you look at the sheer volume of data we process, the numbers get weird.
Think about how much information an average person had to track twenty-five years ago. You needed to remember a few phone numbers, a handful of birthdays, and a couple of key deadlines at work. You weren’t managing six different messaging clients simultaneously, or tracking five cross-functional projects across three time zones, or changing eight different alphanumeric corporate passwords every ninety days.
The volume hasn't just doubled or tripled. It’s a completely different scale. And more importantly, the shape of the information has changed.
It used to be blocky. You handled a task, closed the file, and put it on a shelf. It stayed there. Tomorrow you picked up a new file.
Now, information is a web. Every single thing you're working on is tethered to five other things. The progress of Project A depends on a response from Team B, which is waiting on feedback from Client C, who needs data from System D, which happens to be broken because Employee E didn't realize a legacy setting had changed.
To fix Project A, you have to hold B, C, D, and E in your head all at once.
You tweak one side of the web, and three other nodes twitch. You think you've settled Project A, but then Client C changes their mind, and suddenly you're back at the beginning. You aren't checking off a list of tasks anymore. You're trying to maintain the tension of a massive net, rushing from one corner to another to make sure the whole thing doesn't sag into the dirt.
That's why the concept of "leaving the office" feels so outdated.
It used to be a physical event. You walked through a set of doors, the building closed behind you, and the work stayed inside the walls.
Now you leave the building, but the net comes with you in your pocket. The pings keep arriving. The emails keep landing. You can physically be sitting on your couch, but if that screen lights up, you're still expected to maintain the net.
If you don't reply, a node goes slack. Someone on the other side is blocked, a process stalls, and someone else gets frustrated.
But if you do reply, you’re working at 9:30 PM on a Thursday.
You try to set boundaries. You tell yourself you’ll only answer things during business hours. But the incoming flow doesn't care about your schedule. A problem drops into your inbox late at night, and you know that if you leave it alone, it will sit there mutating for ten hours. What could have been resolved with a two-sentence email at 10:00 PM becomes a three-hour fire drill by 9:00 AM the next morning.
So you check the phone. You send the reply. You aren’t doing it because you love the company; you're doing it because you're trying to protect tomorrow-you from a worse morning.
The strangest thing about this kind of day is that it leaves you with no evidence of your own life.
What did you actually achieve today?
You cleared sixty messages. You sat through two hours of syncs. You approved a couple of requests. You unblocked a colleague. You filled out a tracker.
If you close your eyes and try to picture those things, which of them will still be there tomorrow?
The message you sent was read and instantly replaced by five others. The meeting synchronized everyone for forty-eight hours before the drift started again. The tracker will need to be updated with new numbers by Monday.
It’s like building sandcastles at low tide. You look back at the beach after the water comes in, and the sand is completely flat again. You ask yourself why you bothered building it in the first place.
The answer is simple: if you don’t build the castle, you don’t have anywhere to sit today. You aren’t building for permanence. You’re building just to have a tiny, temporary space where things work long enough for you to get through the afternoon.
But that brings up a weird contradiction.
If all human effort naturally evaporates like this, how did we ever build anything that lasted? How did we get roads, or libraries, or flight, or code that runs for twenty years without human intervention? If everyone was just carrying water in leaky buckets every morning, everything should have reverted to chaos a long time ago.
Someone, at some point, figured out how to stop the leaking.
They figured out a way to freeze today's effort so it didn't melt by tomorrow.
We call those things structures.
But before we can look at how structures work, we have to accept the reality we're currently swimming in. The world you inhabit wants to be messy. Information wants to rot. Memory wants to fade.
It isn't happening because you lack discipline or focus.
It’s just gravity.
Realizing that doesn't fix the problem, but it stops you from blaming your own character for a mechanical reality. If you think the problem is your own lack of stamina, your only solution is to try to carry more buckets. You wake up earlier, you stay up later, you reply faster, you try to hold more variables in your head until you hit a wall.
But your capacity isn't the issue. The issue is the container.
You don't need to run faster on the treadmill. You need a different way to stand.
But to see that clearly, we have to look at another side of this—why so much of what we do every day feels like it leaves no trace at all.