“It was just a twelve-minute sync, Sarah. How are we suddenly behind on the whole sprint delivery?”
“It wasn’t twelve minutes. It was the forty-five minutes of mental recovery afterward. And the three ‘urgent’ Slack pings that happened while we were in the room. And the follow-up thread that I had to read just to make sure I didn’t miss a change in the requirements.”
“Twelve minutes is twelve minutes on the grid.”
– “The grid is a liar.”
I was thinking about that conversation this morning at when my phone buzzed on the nightstand. I reached for it, heart hammering because at that hour, a phone call usually means a hospital or a fire. It was a wrong number. Some guy with a raspy voice asking if “Mister Henderson” had finished the plumbing invoice.
I told him he had the wrong person and hung up, but the damage was done. I lay there staring at the ceiling, the dream I’d been having-something about a stone archway in a storm-dissolving like salt in water. I couldn’t get back to the archway. My brain was already calculating my own invoices, my own deadlines, the rattle in the truck’s engine.
That 5am call is exactly what an “urgent” post feels like to a creative team. It’s a colonial force. It moves into a quiet territory, plants a flag of “Right Now,” and demands that the locals stop what they’re doing to pay tribute.
We used to have these afternoons. I remember them from maybe . Tuesdays and Thursdays, mostly. The calendar looked like an empty field. No blocks, no colorful rectangles representing “Touchpoints” or “Alignment Sessions.” We just sat there.
Unstructured time. Space for stone archways and stormy dreams.
Every void settled by pioneers of the mundane.
Sometimes we’d play with a new piece of software, or I’d spend three hours looking at the way a specific shadow fell across a piece of masonry I was trying to replicate. We stumbled into the oddest, most brilliant ideas during those gaps. We once solved a structural problem because two of us were bored enough to start throwing pebbles at a bucket.
Now, those gaps are gone. They didn’t disappear in a landslide; they were settled by pioneers of the mundane. One urgent post claimed an hour for a client emergency that wasn’t actually an emergency. Then a status meeting claimed forty minutes because the manager felt “disconnected.” Then a “quick” review claimed another thirty.
Each intrusion, on its own, was perfectly reasonable. If you looked at any single one of those calendar invites, you’d say, “Yeah, that makes sense. We should probably do that.” But in aggregate, they are a famine.
The Mortar and the Void
I spend a lot of my time working with historic buildings. People think masonry is just about the stones. They look at a wall and see the granite, the limestone, the heavy things. But as a mason, I’m mostly concerned with the mortar joints-the space between. If you don’t leave enough room for the mortar, or if you use the wrong kind of “fill” because you’re in a hurry, the wall will eventually explode.
The structural integrity of the wall depends on the void between the stones.
There’s a process we call repointing. Most people think you just smear some new mud over the cracks. If you do that, you’re an amateur and you’re ruining the building. To do it right, you have to take a hammer and a thin chisel and rake out the old, failing material.
You have to go deep-usually twice the width of the joint itself. You are quite literally creating a void. You are making the wall look “worse” for a while. You’re removing material. But without that deep, clean void, the new mortar has nowhere to bite. It’ll just sit on the surface like a scab and fall off after the first hard frost.
Teams are exactly the same. Your “slack time” is the joint. It looks like a void. To a project manager looking at a spreadsheet, that four-hour block of “nothing” on a Tuesday looks like a failing. It looks like a place where money is leaking out of the company.
They want to fill it with bricks. They want to pack every square inch of the calendar with “work.” But when you pack a team that tight, there’s no room for the ideas to bite. Everything becomes a surface-level “scab” of a solution.
You produce work that is reactive, thin, and entirely forgettable. You meet the deadline, sure, but you produce nothing original. You’ve colonized the void, and in doing so, you’ve ensured the wall has no structural integrity.
The frustration is that we treat this colonization as a virtue. We’ve been conditioned to think that an empty inbox or a cleared notification badge is the same thing as progress. It’s not. It’s just housekeeping. And if you spend all day cleaning the house, you never actually live in it.
The Cost of Artificial Speed
I’ve made this mistake myself. Last summer, I was working on a chimney for a client in the valley. I was behind schedule because of the rain, so I started skipping the “void” stage. I stopped raking out the joints properly. I figured I could just “urgent post” my way through the masonry-quick fixes, fast applications, no breathing room.
The Spall Effect
By , the face of the chimney started to spall. The bricks were literally popping off because I hadn’t given the structure the “slack” it needed. I was trying to save an hour a day and ended up losing .
We see this in the digital space all the time. Brands and creators feel the pressure to be “on” every second. They see the empty spaces in their social proof as a threat. They think they have to manually grind out every single follower and every single interaction, colonizing their own creative hours with the mechanical labor of visibility. They forget that visibility is a tool, not the work itself.
Sometimes, the smartest thing you can do for your team’s sanity is to outsource the mechanical parts of growth so you can protect the quiet hours where the actual “value” is created. If you’re an Italian creator trying to break through the noise, you don’t necessarily need to spend three hours a day chasing the algorithm’s tail.
You can choose to comprare follower instagram to build that initial layer of social proof, effectively buying back the slack time you need to actually make something worth following. It’s about deciding which “bricks” are worth your manual labor and which parts of the structure can be handled by a reliable system.
But most teams don’t do that. They treat every notification like a sacred command. The stream of consciousness in a modern office is a jagged thing. (Did I send that PDF? Sarah’s typing… wait, the coffee’s cold. Why is the printer making that sound? Henderson… who the hell is Henderson?)
We are living in a state of constant, micro-interruption. We’ve lost the ability to go deep because we’ve allowed our “commons”-that shared resource of unstructured time-to be privatized by whoever has the loudest “ping.”
Think about a park in the middle of a city. It’s “waste” land. You could put a skyscraper there. You could put a parking lot there. Every developer looks at that grass and sees lost revenue. But if you build over the park, the city starts to die. People have nowhere to breathe, nowhere to clear their heads, nowhere to simply exist without being a consumer.
Slack time is the park in your team’s calendar. And right now, we’re letting “Urgent Posts” build parking lots over all our grass. We tell ourselves we’re being “agile.” We tell ourselves we’re “responsive.” But responsiveness is often just a fancy word for having no plan.
If I spend my whole day responding to the stones that are falling out of the wall, I never have time to mix the mortar that keeps them in place.
The Virtue of Rhythmic Insolence
I’ve noticed that the teams who actually produce the “odd, brilliant ideas” are the ones who have a certain level of rhythmic insolence. They ignore the first ping. They don’t check the thread until the afternoon. They protect their “voids” with a ferocity that looks like laziness to the uninitiated.
They understand that a full calendar is a sign of a team that has stopped thinking and started just… vibrating. The mortar of a team is the silence that everyone treats like a vacancy until the entire structure cracks under the weight of too many urgent bricks.
I still think about that call. It wasn’t the caller’s fault, really. He just had the wrong number. He was just trying to get his plumbing invoice settled. But his “urgency” became my “disruption.” That’s the nature of the beast. Your urgency is almost always someone else’s colonization.
If we want to get back to the brilliant ideas, we have to start saying “no” to the reasonable intrusions. We have to stop treating the grid as the ultimate truth. We have to remember that the most important work often happens when it looks like nothing is happening at all.
I’m going back to that chimney in the valley next week. I’m going to take my time. I’m going to rake out those joints deeper than I think I need to. I’m going to leave the void.
Because I’ve learned the hard way that if you don’t make room for the silence, the stones won’t stay where you put them. And if the stones don’t stay, all the “urgent” work in the world won’t keep the roof from coming down.