Robustness
Last week I wrote about load. The weight that accumulated over the holidays and into January. The shifted baseline. The system under pressure.
This week I want to ask a different question: what held?
Because something always does. Even under stress, certain parts keep functioning. The pattern of what holds versus what collapses tells you how your life is actually designed.
Here is what held.
I get up early. Every day. Typically two hours before anyone else in the house, sometimes more. This is not discipline. It is architecture. The dogs enforce it; they whine if I don't get up, so I get up. I let them out of their cages, let them into the yard, feed them. The morning begins whether I am ready for it or not.
Then coffee. Early January was a lot of experimentation with a new espresso machine, a Breville Barista Express Impress. I chose it partly because it's approachable enough for Cecili to use if she wants to, and partly because I wanted to learn the craft from a real starting point before upgrading. Dialing in the grind, adjusting the dose, learning to read the shot. The machine responds to inputs, not intentions.
The marriage held. It always does. Cecili and I have been together since the first night of our first pre-orientation at New College of Florida, back when it was one of the top-rated public colleges in the country. We are a good couple. She balances my intensity in ways I still don't fully understand. Being apart for a month doesn't weaken that; it just changes the communication channel.
And World of Warcraft held. That sounds trivial. It isn't. WoW is the only space in my life that asks nothing of me except presence. No output. No performance. No growth narrative. Just a world that exists on its own terms, where I can turn off the part of my brain that is always designing, always solving, always managing load. Mine happens to be Azeroth.
Here is what did not hold.
Writing. I started a new role at Wider Circle as VP of Enterprise Assurance and Governance and Chief Compliance and Privacy Officer. The learning curve is steep and the bandwidth it requires is real. Writing was the first thing I dropped because it demands sustained attention, and sustained attention was the scarcest resource I had.
Training. The bike remained untouched for another week. I told myself it was about time. It was partly about time.
And anger. I have always had a difficult relationship with anger. I work on it constantly. I fail at it constantly. I work on it some more. Under load, the margin shrinks. The fuse shortens. I did not handle every moment of January with the patience my family deserves.
Now, here is what the pattern reveals.
The things that held are the things with external scaffolding. The dogs create the morning. The espresso machine creates the ritual. The marriage has decades of structural depth. WoW has no stakes, which is precisely why it survives stress.
The things that collapsed are the things that depend on discretionary energy. Writing requires choosing to sit down. Training requires choosing to get on the bike. Patience requires choosing restraint in real time, with no cue and no ritual to support it.
This is not a willpower problem. It is a design problem.
Robust systems don't rely on motivation. They function independent of mood, energy, or circumstance. Fragile systems depend on everything going right inside the person running them.
I am not going to fix this in a week. But I can start noticing which parts of my life have scaffolding and which parts are running on willpower alone.
That distinction is the beginning.
Ken Wake is the author of Thinking Design (forthcoming) and a Professor and Entrepreneur in Residence at Georgetown University. His work explores systems, technology, design, and meaning. Tour de Ken is his weekly log.
