What I've Learned About My Own Operating Limits

The Observation

Everyone has operating limits—the boundaries of how they work best. These aren’t abstract. They’re specific patterns: when energy peaks, how long focus sustains, what recovery looks like, where quality degrades.

I’ve spent years learning mine, mostly by violating them and observing what broke.

What follows isn’t productivity advice. It’s not generalizable. It’s an honest account of my own patterns, written mostly to remind myself what I keep forgetting.

The Burst Pattern

I don’t work steadily. I work in bursts.

A burst might last a few hours, a day, occasionally a week. During a burst, output is high, quality is high, and momentum feels effortless. Ideas connect. Problems solve. The work feels like it’s working.

Between bursts: not much. Maintenance tasks. Low-intensity work. Nothing that requires deep engagement.

I spent years trying to eliminate the low periods. Wake up earlier. Create routines. Force consistency. None of it worked. The bursts didn’t become more frequent; they became less intense. Forced consistency produced consistent mediocrity.

The pattern I’ve accepted: bursts happen when they happen. My job is to be ready when they arrive and not waste them on the wrong things.

What Degrades Under Sustained Load

When I try to maintain high output continuously, specific things break:

Quality goes first. Not visibly at first. The work still looks okay. But the thinking becomes shallower. The ideas become more conventional. The output lacks the precision that makes it valuable. I don’t notice until I review it later and realize: this is just noise.

Judgment follows. Tired judgment is bad judgment. I make decisions that seem reasonable in the moment but look obviously wrong afterward. I commit to things I shouldn’t. I miss problems that should be obvious.

Then health. Sleep suffers. Exercise stops. The physical foundation that supports everything else erodes. This creates a cycle: degraded health produces degraded output, which creates pressure to work more, which further degrades health.

Finally, relationships. When I’m running at capacity, relationships get what’s left over. Which is nothing. People notice. This accumulates.

None of this is unique to me. But knowing it abstractly doesn’t help. I have to feel it failing before I remember to back off.

The Schedule Trap

“Publish weekly” sounds reasonable. Regular cadence builds audience. Consistency builds trust. The productivity literature is clear: commit to a schedule and stick to it.

For me, this is a trap.

When I commit to a schedule, I start producing to meet the schedule rather than producing when I have something worth producing. The deadline creates pressure. The pressure creates compromise. The compromise creates mediocrity.

The articles I’m proud of weren’t written on schedule. They emerged when thinking had stabilized—when I actually had something to say. Forcing that process to meet an arbitrary timeline produces articles I’m not proud of.

My rule now: publish when clarity stabilizes, not on a schedule.

This means long gaps sometimes. That’s okay. The audience I want prefers intermittent quality over consistent mediocrity. (And if that’s not true, I don’t want that audience anyway.)

What Rhythm Actually Works

Through experimentation, I’ve found patterns that don’t break:

Morning for difficult thinking. The window is about three hours after waking, if nothing interrupts it. This is when hard problems can actually get solved. The rest of the day is for everything else.

Batch similar work. Switching contexts is expensive. A day of writing is productive. An hour of writing between meetings is almost worthless—the setup cost exceeds the output value.

Protect recovery. Recovery isn’t wasted time. It’s the foundation for the next burst. Shortcutting recovery shortens the next productive period. I’ve learned this repeatedly and forget it every time.

Track energy, not time. An hour at high energy is worth five hours at low energy. The question isn’t “how many hours did I work” but “where did I spend my high-energy hours.”

Respect the limit. When quality starts degrading, stop. The additional hours produce negative value—output that will need to be redone, decisions that will need to be reversed. Stopping earlier is stopping at the right time.

The Honesty Requirement

This only works if I’m honest with myself.

It’s easy to rationalize laziness as “respecting limits.” It’s easy to call avoidance “waiting for clarity.” The patterns I’ve described can become excuses if I’m not careful.

The check is simple: am I actually producing during the bursts? If the bursts are productive, the low periods are legitimate. If the bursts are also low-output, something else is wrong.

Another check: am I avoiding difficult work by calling it “not the right time”? Some work is genuinely better done later. Some work is uncomfortable and I’m just procrastinating. Being honest about which is which matters.

What This Means for Commitments

I’m careful about commitments that require sustained output.

Some work legitimately requires it: ongoing client relationships, projects with external timelines, collaborative efforts where others depend on my contributions. I take these commitments seriously—they’re obligations, not suggestions.

But I’m selective about which commitments I make. Knowing my patterns means knowing what I can reliably deliver. Overcommitting because I imagine I’ll work differently than I actually do—that’s not ambition, it’s dishonesty.

Better to commit to less and deliver it well than to commit to more and deliver it poorly.

The Outcome

Publish when clarity stabilizes, not on a schedule.

Work in bursts. Protect recovery. Be honest about limits without using them as excuses.

None of this is advice for anyone else. Your patterns are different. But I suspect everyone has patterns they keep ignoring, limits they keep violating, rhythms they keep overriding. The question isn’t whether you have limits but whether you’ve bothered to learn them.