Back to all articlesDMS JOURNAL / INSIGHTS
Today's Me17 min

Today Me. A Decision-Fatigue Firewall That Breaks the Cycle of Stopping

Some days, you are not short of willpower; you have already spent your decision budget

Design a return that conserves willpower and reduces decisions, so an unsteady day does not become a day you abandon.

Today Me. A Decision-Fatigue Firewall That Breaks the Cycle of Stopping
DMS / VISUAL ESSAY

A broken flow is restored through fewer decisions, not greater willpower.

When a day falls apart, we usually reach for the same prescription: pull yourself together, focus, wake up.
Strangely, those words appear precisely when we are most tired: after three meetings, messaging alerts pounding at our heads, tasks piling up, and the body sinking into late-afternoon inertia. What we need then is structure, not resolve.

In CH9, we designed the interval for switching back on. CH10 asks the next question: Why can we not restart even when we know how? The answer is often simple. The return itself is less difficult than the many small decisions required before it.

The brain on a disrupted day resembles an overheated browser. There are too many tabs, notifications keep appearing, and the central task is hard to distinguish. Asking again, “What should I do first now?” delays the return. Willpower is not weak; decision fatigue has accumulated.

CH10 therefore has a clear goal: eliminate decisions that obstruct returning. Decide during calm periods so that restarting requires no deliberation. This is not distrust of today’s self, but design that protects the tired self.

Minimal abstract control panel with layered switches and cool neon glow, no people, no silhouettes, cinematic soft light, high detailMinimal abstract control panel with layered switches and cool neon glow, no people, no silhouettes, cinematic soft light, high detailView original

The Capacity to Decide Runs Out Before Willpower

We make hundreds of choices each day: which task to handle first, which message to answer, whether to have coffee or water, which file to open. Each seems small, but together they drain the energy of thought.

The problem is that important work always comes later. Mornings are full of things we can answer immediately. They are quick to handle and give a strong feeling of accomplishment. Work requiring deep focus tends to remain for the afternoon or evening, leaving us to make the hardest decisions after we are already depleted.

A common misconception appears here: “I am simply not someone who follows through.”
No. It is closer to having made too many decisions about direction before reaching the stage of following through.

Returning is a skill of budget management, not grit. Someone who conserves their decision budget can move with little energy. Someone who spends it all in the morning can remain at the starting line that evening even with a perfectly good plan.

CH10 turns this insight into structure: reduce questions, narrow options and create one return button.

The CH10 Framework: The D-1 Firewall (Default · Delay · Delete)

The decision-fatigue firewall consists of three actions.

1) Default — Fix the Default
Set defaults in advance for choices that frequently become unstable.
Examples: “The return timer is always 20 minutes,” “The starting file is today’s 1 work document,” “The first action after interruption is 90 seconds of desk tidying.”
The key is a repeatable choice, rather than an ideal choice.

2) Delay — Postpone Nonessential Decisions
Immediately after returning, defer judgments that are not important.
Examples: reorganizing folders, changing thumbnails, polishing wording or considering a different tool.
These may be necessary tasks, but they are not needed in the first 20 minutes of restarting. During the return, reentry comes before quality.

3) Delete — Remove Options
More options create more fatigue. At the moment of returning, sharply reduce tools and paths.
Examples: show only 1 work app, 1 input field and 3 checklist items.
Temporarily reducing freedom of choice raises the probability of execution.

The D-1 firewall is not an elegant productivity system. It is deliberately plain. But a plain system works on tired days. We need a system that starts under the worst conditions, rather than the best-looking system.

Abstract route map with three bright paths converging into one lane, no humans, no faces, volumetric lighting, clean modern textureAbstract route map with three bright paths converging into one lane, no humans, no faces, volumetric lighting, clean modern textureView original

Five Practical Rules for Halving Return Time

Rule 1. Fix a one-line starting sentence.
Instead of asking “Where should I begin?”, act on a predetermined starting sentence.
Example: “For now, execute for 20 minutes instead of judging.”
A short sentence simplifies thinking and speeds entry into action.

Rule 2. Keep the return checklist to no more than 3 items.
Long checklists can delay starting more than they provide reassurance.
Minimize the return checklist:

  • Start a 20-minute timer.
  • Open the core document.
  • Complete the next paragraph or task.
    Those three are enough.

Rule 3. Delay quality assessment until the second period.
Checking “Am I doing this well?” immediately after returning breaks the flow.
Produce in the first period; improve in the second. Keep that order.

Rule 4. Leave the next first action at the stopping point.
When finishing, write a sentence describing the next starting action.
Example: “Next start: write the first sentence under subheading 3.”
That one line greatly reduces the decision cost of the next return.

Rule 5. Create a mode specifically for low-energy hours.
After 4 p.m., or at night, prohibit demanding judgments.
Run only predetermined routines during these hours. Switching modes is operational competence, not a sign of weakness.

Applying these five rules does not require living with special intensity. It simply reduces the loss caused by stopping. Reduced loss brings less self-blame, and less self-blame makes the next attempt arrive sooner.

Try It Now: A 10-Minute Decision Diet

Open your notes app and write only the following:

  1. 2 periods in which you frequently stop.
  2. 3 decisions you repeatedly deliberate over during those periods.
  3. 1 default for each decision.
  4. 3 judgments to prohibit in the first 20 minutes after returning.
  5. 1 sentence describing the next first action to leave when stopping.

The exercise aims not at perfection but at reducing the total number of decisions. We always strive to make better choices. In reality, choosing to deliberate a little less and act immediately often produces better results.

CH10’s conclusion is this: consistency is not a privilege of the strong, but a skill of those who manage decision fatigue. My unsteady self is not an inferior version, but a version that needs a different operating mode.

Tomorrow, the schedule will shift again. Concentration will be interrupted. That is normal.
What is not normal is trying to endure in exactly the same way after the interruption.
Now, instead of enduring, let us design—toward making the return easier.

Geometric night workspace with reduced controls and single luminous focus point, no people, no silhouettes, cinematic contrast, ultra-detailedGeometric night workspace with reduced controls and single luminous focus point, no people, no silhouettes, cinematic contrast, ultra-detailedView original

Reedo portrait

Reedo Insights

Translating technology into practical language

With over 19 years in 3D design, optical communications equipment development, and global field training, I now connect AI automation, creative imaging, and practical channel operations to document ways of making complex work simpler.

Newsletter

New writing,
in your inbox.

Receive notes on AI, automation, and building income. The newsletter is currently sent in Korean; English articles are available here on the blog.

New articles only · Unsubscribe anytime

Start a conversation

Turn an idea into something practical.

Whether it is automation, design, training, or content, we can start with the problem you need to solve.

Get in touch