Failure, Setbacks, and Resetting
Five hundred feet. The runway is right there.
But the approach is wrong. I am coming in too fast and too high. The numbers on the dials refusing to settle.
So I pull in the collective and push the nose forward and climb away from the very thing I came here to do, landing the helicopter safely.
Nobody of my crew gasps or logs it as a failure. A go-around is not an emergency it’s a normal, rehearsed procedure, briefed before every single approach, practiced until it’s boring.
Pilots don’t build careers on never missing an approach, but on knowing exactly what to do when they do.
Every long-term creator needs the same thing.
Because every long-term creator has a dirty secret: at some point, they stopped.
Sometimes it’s a week. Sometimes it’s three months. Sometimes it’s a whole year that quietly disappears into “I got busy», « family emergency», or «something happened».
If you’re building within constraints, a full-time job, a real life, a 10-hour or less weekly cap, this isn’t a moral failure, but pure math.
Sooner or later, your beautiful system will collide with reality:
illness,
projects,
family,
fatigue,
an overloaded season.
The question is not “Will I ever break my streak?”
Instead ask: “What will I do next?”
This post is about designing a restart ritual, so that when (not if) your system breaks, you know exactly how to come back without shame or burnout.
Why Systems Break (Even Good Ones)
We like to imagine that once we’ve found the perfect routine, we’ll sail along forever.
But even well-designed systems break for a few predictable reasons:
Life events: big projects, travel, illness, caring for others.
Invisible load: cognitive stress that doesn’t show on the calendar but drains your energy.
Scope creep: quietly adding more commitments than your 10 hours can support.
Emotional dips: seasons of low motivation, doubt, or boredom.
None of these are signs that you’re not cut out for what you do. They’re signs that you’re human, operating inside real constraints.
The danger is not the break itself, but the story you tell yourself when it happens:
“I’ve ruined it.”
“I always do this.”
“There’s no point starting again.”
That story is optional and instead you can replace it with a procedure and checklist like a pilot does.
The Shame Spiral vs. the Calm Debrief
When you miss a week or more, two paths open.
On the first path, you say nothing. You avoid your dashboard, avoid your drafts, avoid your audience. Each day that passes increases the emotional cost of returning. You quietly downgrade this project from “serious” to “something I tried once.”
On the second path, you treat the break like a pilot treats an incident: with a calm debrief.
You ask:
What actually happened?
Which parts were outside my control?
Which parts were predictable?
What did this reveal about my system?
You don’t assign blame but instead gather information.
This mindset shift is crucial. It turns a break from a verdict on your character into a data point about your system and your season of life.
A 3-Step Restart Procedure
Here’s a simple procedure you can use any time you fall off the wagon.
1. Acknowledge
First, name the break, privately, then (if appropriate) publicly.
Privately, you might write:
“I haven’t published for four weeks. I felt ashamed and avoided looking at the calendar. The reason was [project, illness, family situation, energy crash].”
Publicly, a short, honest note is enough:
“You may have noticed a gap in the usual rhythm. The last weeks were heavier than planned. I stepped back to handle [very brief context]. I’m back, and you’ll see the regular cadence resume from here.”
You don’t owe the internet your medical records or family details. You owe your readers honesty at the right level of altitude.
2. Assess
Next, calmly review:
Capacity: Was your 10-hour plan realistic, or did it quietly become 14?
Calendar: Did key creation blocks get invaded by other commitments?
Signals: Were there early signs of overload you ignored?
Emotion: Were you bored with the topics, resentful of the schedule, or just tired?
Write down what you discover and adjust accordingly to what could work better for you. It’s a small, personal after-action review.
3. Adjust
Finally, make one or two specific changes:
Reduce word counts for a season (shorter minis, tighter cornerstones).
Lower your publishing frequency slightly instead of quitting (for example, skip one mini per month for a quarter).
Move your hardest work back into your best-energy blocks.
Create a non-negotiable baseline. The one tiny action you do even in bad weeks.
Project managers have a name for this: re-baselining.
When a project slips, you don’t tear up the whole plan and you don’t pretend the original dates still hold. You acknowledge the new reality, adjust the baseline, and manage forward from where you actually are. Not where the old plan said you’d be.
The key is to avoid dramatic overcorrections. You don’t need a brand-new system. You need a 10–20% adjustment that respects what your life just taught you.
How to Communicate Honestly with Your Readers
Many creators are afraid to admit gaps. They worry readers will judge them or leave.
In practice, when you communicate with calm honesty, three good things usually happen:
1. You humanize the project. Readers see that you’re operating inside real constraints, like them.
2. You model sustainability. They realize they don’t have to be perfect to be consistent over time.
3. You reset expectations. People know what to look for next, instead of wondering if you’ve vanished.
A simple “catch-up” email might look like:
«Subject: A quick update and what’s next
The last four weeks didn’t go as planned.
> [One or two sentences of context.]
I stepped back from publishing to handle that well. The trade-off was a gap in the usual cadence.
Here’s what I’m doing differently going forward:
> - [one adjustment]
> - [another adjustment]
You can expect [summary of your new or resumed rhythm].
And to keep today’s email useful, here’s one short idea you can use this week:
> [Mini insight or practice.]
You acknowledge, adjust, and then immediately get back to serving.
Designing a System That Fails Well
A robust system is not one that never fails. It’s one that fails gracefully.
You can design for that by:
Defining a minimum viable output.
For example: “Even in bad weeks, I will publish one short note or two useful paragraphs.”
Separating identity from output.
In the dojo, failing a grading doesn’t get you expelled. You bow. You wear the same belt a few months longer. You show up Tuesday like you showed up last Tuesday, because the grade was never the practice. The practice was the practice. You are not “no longer a writer” because you missed three weeks. You’re a writer between gradings.
Building in buffer seasons.
Intentionally lightening your schedule during known heavy periods (end of year, major projects) instead of pretending they won’t affect you.
Keeping restart friction low.
Always have one half-written piece you can polish in a couple of hours. That first ship after a gap should feel as easy as possible.
Think of it like flight operations in winter: delays and reroutes are built into planning. The system acknowledges reality instead of insisting on perfection.
Your Next Step: Write It Down Before You Need It
So before your next gap, write your procedure down. One page, titled “When the system breaks”:
1. Acknowledge.
Admit the break on paper. Draft the 3–5 sentence catch-up note.
2. Assess.
Review capacity, calendar, signals, emotion. No blame. Just data.
3. Adjust.
Change one thing. Pick the smallest useful piece to ship this week. Mark a fresh start date.
Save it where you’ll see it.
Then, when the gap comes, and it will, you don’t negotiate with shame.
You fly the procedure and building a body of work on always returning.