Minimum Viable Day for decision fatigue Glossary
The Minimum Viable Day Recovery Protocol — decision fatigue as a defined term is a named operating pattern in the Billionaire High Performance Coach system. It applies Minimum Viable Day Recovery Protocol, which shrinks the day to one meaningful action when capacity is low, to decision fatigue as a defined term.
What this page recommends
The Minimum Viable Day Recovery Protocol — decision fatigue as a defined term is a named operating pattern in the Billionaire High Performance Coach system.
- Next step: Buy
Minimum Viable Day Recovery Protocol — decision fatigue as a defined term
Use it on a day where the honest read is that the normal plan is not going to happen, and the choice is between a smaller day and no day.
Minimum Viable Day Recovery Protocol shrinks the day to one meaningful action when capacity is low.
Do this first. Convert recurring low-consequence choices into standing defaults with written override conditions.
Do not do this. The metric that misleads here: hours worked. A day can be full and still end with nothing decided, and the hours will not show you that.
How do I stop spending the day's judgment on choices that repeat? Convert recurring low-consequence choices into standing defaults with written override conditions.
When this framework is the right one. Use it on a day where the honest read is that the normal plan is not going to happen, and the choice is between a smaller day and no day.
- Say the capacity out loud before you look at the list: what fraction of a normal day is actually available.
- Pick exactly one output that would make today non-zero, and define its finished state in a sentence.
- Delete or defer everything else in writing, so the deferral is a decision rather than a failure.
- Stop when the one output is done, even if energy returns. Stopping on purpose is what makes the smaller day repeatable.
Decision fatigue support, broken down
| Element | What it is here |
|---|---|
| The question behind it | How do I stop spending the day's judgment on choices that repeat? |
| The operating move | Convert recurring low-consequence choices into standing defaults with written override conditions. |
| The unit that matters | A day, measured in decisions rather than hours. |
| What looks like progress and is not | Deciding faster, which saves seconds on something that should not be decided at all. |
| Evidence that it is working | The list of converted decisions, and how often each override fired. |
| Where this stops | Fatigue that persists regardless of decision load is a health question, not a system question. |
Common misreadings: decision fatigue support
| Element | What it is here |
|---|---|
| What it is usually mistaken for | Being disorganised. The list is usually fine; it is the number of times a day you consult it that is not. |
| The metric that misleads | Hours worked. A day can be full and still end with nothing decided, and the hours will not show you that. |
| What to do in the first week | Keep a tally of every decision you make twice. Do not change anything yet; a week of tallies is what tells you which three to convert. |
| Where this stops | Fatigue that persists regardless of decision load is a health question, not a system question. |
Minimum viable day card
| Field | What goes in it | Why it is bounded |
|---|---|---|
| Capacity read | A fraction, stated before the list is opened. | Reading capacity after seeing the list produces a number that flatters the list. |
| The one output | One deliverable with a written finished state. | Two outputs is a normal day wearing a smaller name. |
| Explicit deferrals | The items you are not doing, listed by name. | Unlisted work does not go away; it stays as background pressure all day. |
| Stop condition | The moment the one output is finished. | Without a stop condition the small day expands and the next low day has no template. |
Worked example: Minimum Viable Day Recovery Protocol applied to decision fatigue
Use it on a day where the honest read is that the normal plan is not going to happen, and the choice is between a smaller day and no day.
How do I stop spending the day's judgment on choices that repeat? Convert recurring low-consequence choices into standing defaults with written override conditions.
Say the capacity out loud before you look at the list: what fraction of a normal day is actually available.
What to measure. The list of converted decisions, and how often each override fired.
Running Minimum Viable Day Recovery Protocol for decision fatigue support
Most low-capacity days are lost to negotiating with a plan that was written for a different day. Naming a smaller day up front, in advance of the negotiation, removes the negotiation. The day still counts, and the system stays installed.
The full set of failure modes for this framework, the evidence to record, and a prompt you can paste are on its framework page. This page covers the part specific to decision fatigue support.
What this is not. It is not permission to do less indefinitely, and it is not a treatment for exhaustion or illness. It is a way to keep a system installed across a bad day.
Evidence that it is working: the list of converted decisions, and how often each override fired.
Fatigue that persists regardless of decision load is a health question, not a system question.
Frequently asked questions
What does Minimum Viable Day Recovery Protocol actually mean?
Most low-capacity days are lost to negotiating with a plan that was written for a different day. Naming a smaller day up front, in advance of the negotiation, removes the negotiation. The day still counts, and the system stays installed.
When does it stop applying?
It is not permission to do less indefinitely, and it is not a treatment for exhaustion or illness. It is a way to keep a system installed across a bad day. Fatigue that persists regardless of decision load is a health question, not a system question.
What should a reader do in the first week on decision fatigue?
Keep a tally of every decision you make twice. Do not change anything yet; a week of tallies is what tells you which three to convert. Being disorganised. The list is usually fine; it is the number of times a day you consult it that is not.
Does this page diagnose, treat, or replace professional advice?
No. It is educational and organizational only. It does not diagnose or treat anything, and it is not a substitute for a clinician, a lawyer, or a financial professional. If the situation involves health, safety, legal exposure, or money at stake, that is the moment to use qualified human support.
Boundaries
Billionaire High Performance Coach is educational and organizational. It is not medical, psychological, legal, financial, therapeutic, or diagnostic advice, and it does not diagnose or treat anything.
If the situation involves safety, health, legal exposure, financial decisions, or crisis-level distress, use qualified professional support. A written framework is not a substitute for a clinician, a lawyer, or a financial professional.
Where this fits in the system
Checkout is handled through Gumroad for instant digital access after purchase.
Sources and review basis
This page was reviewed against the following sources on . Third-party products change their features, terms, and pricing, so verify current details with the provider.