Directory · C
Not sure this is the right entry? Run the check · New here? Start with the premise
Cycles
1 min read · 305 words
You run on cycles, not on a flat line. Expecting constant output from an oscillating system is what makes every trough feel like something going wrong.
Is this you?
Check whatever lands. Nothing is sent anywhere.
The machinery runs on cycles, not lines.
Energy rises and falls. Motivation peaks and troughs. Emotional weather moves through in patterns that repeat — not identically, but recognizably. The body cycles through hormonal rhythms, sleep rhythms, seasonal shifts, and longer arcs of capacity and recovery. The system was not built for constant output at a fixed level. It was built to oscillate.
The mind, which prefers linear models, resists this. The software expects: effort should produce consistent output. Monday’s productivity should match Tuesday’s. This month’s motivation should match last month’s. The linear expectation, imposed on a cyclical system, produces the persistent sense that something is wrong when the trough arrives — that the decline is a problem rather than the other half of the cycle.
To work with cycles rather than against them: observe the pattern. The system has rhythms. Energy has a daily arc — when it rises, when it peaks, when it drops. Motivation has a longer arc — weeks or months of engagement followed by a period of reduced drive. Even creative output cycles — periods of productivity followed by periods of apparent fallow that are, mechanically, the system restocking.
The trough is not a failure. It is the system in its recovery phase. The organism that forces output during the trough degrades the next peak. The organism that rests during the trough — that recognizes the decline as the other half of the cycle and adjusts the demand accordingly — returns to the peak with a fuller reserve.
The cycles cannot be eliminated. They can be observed, respected, and planned around. The one at the controls who knows where the system is in its cycle can match the demand to the phase — high demand during the peak, maintenance during the trough, recovery during the decline.
A cyclical system judged by a linear expectation
Energy rises and falls. Motivation peaks and troughs. Emotional weather moves through in patterns that repeat — not identically, but recognisably. There are hormonal rhythms, sleep rhythms, seasonal shifts, and longer arcs of capacity and recovery underneath all of it. The system was built to oscillate, not to hold a fixed level.
Your mind prefers linear models and resists this. The expectation is that effort should produce consistent output — Monday should match Tuesday, this month's motivation should match last month's.
Impose a linear expectation on a cyclical system and every trough reads as a problem rather than as the other half of the cycle. Which is where most of the damage happens: not in the trough itself, but in the conclusion drawn from it.
And the conclusion is usually that something has been lost — the ability, the drive, the person you were in the peak. That generates exactly the wrong response: pushing hardest during the trough, which deepens it, and then reading the deepening as confirmation.
Find your own pattern
You can't work with a cycle you haven't measured. Most people have never looked.
Real questions
Why can't I be consistently productive?
Because you're a cyclical system being judged against a linear expectation. Energy, motivation and capacity oscillate on several overlapping rhythms, and constant output at a fixed level was never the specification. The inconsistency isn't the failure — treating it as one is, because it produces the response of pushing hardest exactly when capacity is lowest.
Why does a bad week make me think I've lost it?
Because a trough doesn't present as a phase, it presents as an accurate assessment — and from inside it, the peaks look like flukes rather than the other half of the same pattern. That reading is systematically wrong in one direction. It's the main argument for not making structural decisions during one: the instrument is reliably miscalibrated at that point in the cycle.
How do I work with my cycles instead of against them?
Measure first, because you can't plan around a pattern you haven't identified — a month of daily ratings usually reveals something. Then plan asymmetrically: demanding work in the peaks, low-demand work in the troughs, rather than distributing evenly and failing half the time. That feels like cheating and it's just matching the load to the capacity that actually exists.
Should I push through a low period?
Push gently, and don't make it the moment for your hardest work or your biggest decisions. Hard pushing during a trough tends to deepen it and then supply apparent evidence that something is wrong with you. The useful distinction is between maintaining a floor — small versions, kept going — and demanding peak output from a system that currently hasn't got it.
Is this just an excuse for inconsistency?
It would be if it were applied to everything indiscriminately. The check is whether there's an actual pattern — measured, with a shape — or whether cycles is being used to describe not doing things. A real cycle has peaks in it. If there's been no peak for a long time, that's not a trough, and treating it as one delays looking at what it actually is.
Why do I always start things at the top of a cycle?
Because the peak supplies the energy and optimism that make starting feel easy, and the commitment gets sized to that capacity. Then the trough arrives, the plan becomes impossible, and the whole thing lapses — which is the standard shape of an abandoned attempt. Designing for your worst week rather than your best is the single adjustment that most often fixes it.