Rules

 The One-Hour Rule

I opened a hard problem on my laptop: a data pipeline that kept dropping records under load. I stared at it for a few minutes, then reached for my phone. One notification became a scroll through social media. When I came back to the laptop, the problem felt unfamiliar again. I reread the same notes, felt the resistance, and closed the screen before anything real happened.

Nothing dramatic had gone wrong. I had simply watched a slow leak of attention drain my focus, the same way I have watched it drain a hundred times before.

That pattern led me to the one-hour rule: I choose one thing and sit with it for a protected hour. No phone beside the laptop. No switching to an easier task when the work becomes uncomfortable. No pretending that checking messages is part of solving the problem. The hour is small enough to begin, but long enough to get beneath the surface.

At first, I treated the rule as a productivity technique. Over time, it became something more. The hour gives me solitude, solitude makes restraint possible, and restraint gives me enough attention to aim my work outward.

Solitude comes first because noise can make any direction feel important. When I move continuously between meetings, messages, code, and the phone, I absorb whatever is most urgent around me. I can stay busy without knowing whether the work deserves my effort.

A quiet hour changes that. During one recent session, I sat with the same pipeline failure that had survived several quick attempts. The first twenty minutes produced almost nothing. I wanted to search for another task where progress would be easier to see. Instead, I stayed. Eventually I noticed an assumption buried in my approach, tested it, and found the actual failure.

The useful insight did not arrive because I pushed harder. It arrived because I stopped leaving.

Protecting that hour requires restraint. The phone is one threat, but it is not the only one. Anger can consume the hour just as easily. So can frustration, envy, or the urge to chase a quick reward. These impulses often feel important in the moment, but most of them are forms of self-soothing. Reacting gives me immediate relief. Scrolling gives me stimulation. Reacting to an annoying email is not urgency. It is the same comfort wearing a different coat.

Each one turns my attention inward. The hour disappears into managing my mood instead of doing work that could help someone else.

This is where purpose enters. I used to think purpose was something I had to find, as if the correct answer were hidden somewhere inside me. I now think purpose is something I aim. I can aim it toward adding value, and I can also aim it wrong.

Giving effort is not automatically useful. I once spent a protected block polishing an internal tool I was proud of: refactoring it, documenting it, adding options nobody asked for. I told myself I was serving the team. When I finally shipped it, two people used one feature and ignored the rest. I had given real effort, but I had aimed it at producing something impressive rather than something someone needed.

That distinction matters. Purpose cannot be measured only by effort or intention. I have to ask: useful to whom, and judged how?

The most practical tool I have found is the question-swap. When I feel resistance, I stop asking, "What do I get from finishing this?" I ask, "Who does this actually help?"

On another difficult afternoon, I used that swap before opening the laptop. Finishing the pipeline investigation would not make the day more exciting. But the honest answer to who it helped was the on-call engineer at 3 a.m., staring at a dropped batch. Resolving it would remove their uncertainty. That answer gave the hour a clear shape. I wrote down the one question that needed resolving, closed everything unrelated, and worked until I had a fix small and sharp enough to hand over.

The problem did not become easier. It became worth staying with.

I do not protect every hour perfectly. Some days I react too quickly or lose more time than I intended. I am learning not to turn one bad day into a verdict. A day can be lost and recovered through two patient weeks of returning. The point is not a flawless streak. The point is rebuilding the ability to stay.

Tonight, the laptop is open again. The phone is in the other room. For one hour, I will remain with one useful problem and try to aim my attention well.