The mouse pointer is frozen over the green button. It’s a performance, a tiny hesitation I do before every important call, a deep breath before the digital plunge. But the performance is for an audience of one, and today, it fails. My thumb slips on the trackpad and in that split second of unintended contact, the world collapses. The soft, blurry placeholder icon of my initial vanishes, replaced by my actual, unscripted face-deer in headlights, hair clearly unacquainted with a comb, a background of pure domestic chaos. The system I had built to present a calm, collected professional for the first 8 seconds of the call-my little digital curtain-was not just bypassed; it was annihilated by a single, clumsy twitch.
The shock doesn’t have to be a thumb slipping on a trackpad. It can be a supply chain disruption, a key team member getting sick, a sudden market shift that makes your five-year plan look like a child’s crayon drawing. We build for the world we expect, a world of straight lines and predictable inputs. We spend 48 days creating a process map that accounts for every known variable, and then on day 49, an unknown variable shows up and snaps the entire thing in half.
It sent me into a spiral, rethinking everything I thought I knew about strength. The day after the project post-mortem, I couldn’t stand the sight of my own office. The whiteboard, covered in the ghosts of my failed diagrams, felt like it was mocking me. I grabbed my laptop, needing a complete change of scenery to even begin thinking straight. My first instinct was to find a place with no history, no memory of my failure, so I just searched for places to work remotely and picked the one with the least corporate-looking name. It was in that anonymous coffee shop, watching the world go by, that I started to dismantle my entire philosophy of work, and maybe even life.
That’s when I remembered Claire K.L.
I met Claire on a walking tour of the city’s historic district about a year prior. She was a master mason, a specialist in historic restoration, and she was working on the facade of a 238-year-old customs house. While the tour guide droned on about architectural styles, I watched her work. She wasn’t just slapping mortar into joints. She was listening to the building. She’d tap a brick with her trowel, close her eyes, and tilt her head, as if waiting for a reply. Later, I asked her what she was doing.
The old mortar was designed to be the point of failure.
– This sentence rewired my brain –
That sentence rewired my brain. The original builders knew the system would be under stress. They knew the seasons would change, the ground would shift, and the materials would swell and shrink. So they built a system where the weakest part was also the most easily repaired. The mortar was designed to crack under pressure, creating tiny fissures that could then be repointed every few decades. The cracks were a feature, not a bug. They were the building’s exhaust valve for stress. The system healed itself by being imperfect.
→
This is the opposite of how we build almost everything today. We build software that tries to handle every possible error, until an impossible one comes along and causes a total system crash. We build careers based on a single, specialized skill, and then we’re shocked when automation makes that skill obsolete. We create social personas of unflappable perfection, and then crumble when a moment of genuine, messy humanity-like an accidental camera activation-slips through.
This isn’t an argument for chaos or for having no plan at all. Claire doesn’t just splash mortar on a wall and hope for the best. Her work is incredibly precise, based on centuries of knowledge. She understands the chemistry of lime, the geology of the local stone, the specific weather patterns of the region. She has a deep, intricate plan. But the plan is not about preventing failure; it’s about gracefully accommodating it. It’s about designing for stress, for movement, for life.
After that project of mine failed so spectacularly, I stopped making Gantt charts. At least, not the kind I used to. My new plans look more like sketches, with dotted lines and open spaces. They focus on principles and objectives, not on rigid, sequential tasks. We plan for the first 8 steps, not the first 80. We build in slack. We assume things will go wrong, and we treat those moments not as catastrophes, but as information. The unexpected client request isn’t a crisis anymore; it’s data that tells us our initial assumption was wrong. It’s a hairline crack in the mortar, telling us where the pressure is.
