Minimum Viable Day protocol for trying to build consistency
The Minimum Viable Day Recovery Protocol — trying to build consistency as a protocol 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 trying to build consistency as a protocol.
What this page recommends
The Minimum Viable Day Recovery Protocol — trying to build consistency as a protocol is a named operating pattern in the Billionaire High Performance Coach system.
- Next step: Buy
Minimum Viable Day Recovery Protocol — trying to build consistency as a protocol
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. Write the floor version: what running this looks like on the worst plausible day, small enough that it is never missed.
Do not do this. Do not raise the target. The target is not the problem; the absence of a floor is. The metric that misleads here: days completed. It cannot distinguish a practice that survives a bad week from one that has not met one yet.
The practice works for a stretch and then stops, and the stops are not caused by anything in particular. Do not raise the target. The target is not the problem; the absence of a floor is.
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.
Reading the state: trying to build consistency
| Element | What it is here |
|---|---|
| How you know you are in it | The practice works for a stretch and then stops, and the stops are not caused by anything in particular. |
| What is actually scarce | A floor. There is a target and no defined minimum, so bad days have no version to run. |
| The unit that matters | The floor version, run on the worst day. |
| What looks like progress and is not | A higher target, which makes bad days impossible rather than small. |
| What not to do | Do not raise the target. The target is not the problem; the absence of a floor is. |
| The opening move | Write the floor version: what running this looks like on the worst plausible day, small enough that it is never missed. |
| What changes if it works | Bad days have an action instead of a decision, and the practice survives them. |
Common misreadings: a reader who is trying to build consistency
| Element | What it is here |
|---|---|
| What it is usually mistaken for | Needing more willpower. What is missing is a floor: a version small enough that bad days have an action rather than a decision. |
| The metric that misleads | Days completed. It cannot distinguish a practice that survives a bad week from one that has not met one yet. |
| What to do in the first week | Define the floor and run only the floor, including on the days you could do more. |
| Where this stops | Organizational support only. It is not clinical, legal, or financial advice. |
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: running Minimum Viable Day Recovery Protocol while trying to build consistency
The practice works for a stretch and then stops, and the stops are not caused by anything in particular. A floor. There is a target and no defined minimum, so bad days have no version to run.
Do not raise the target. The target is not the problem; the absence of a floor is. Write the floor version: what running this looks like on the worst plausible day, small enough that it is never missed.
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.
What to measure. Record the one output and whether you stopped at the stop condition. Two fields, same two every time.
Running Minimum Viable Day Recovery Protocol for a reader who is trying to build consistency
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.
Where it goes wrong
Declaring a minimum day and then doing a normal one. It teaches you the minimum day was a lie, so the next time capacity drops you will not use it. Stop at the stop condition. If capacity returned, bank it as an early finish, not extra scope.
Choosing an output that is not actually meaningful. A trivial output makes the day technically non-zero and practically empty, which is worse than admitting a rest day. Pick the item you would be relieved to have done tomorrow morning.
Using it every day. A recovery protocol running as the default is just a smaller normal day, and capacity never gets rebuilt. Count the days you invoked it this month. Above roughly a third, the normal plan is the thing that needs resizing.
Evidence to record. Record the one output and whether you stopped at the stop condition. Two fields, same two every time.
A line you can paste. Today is a low-capacity day. Ask me for my capacity as a fraction, then help me pick exactly one output and write its finished state.
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.
Write the floor version: what running this looks like on the worst plausible day, small enough that it is never missed.
Bad days have an action instead of a decision, and the practice survives them.
Frequently asked questions
What if I am too trying to run the whole protocol?
Run the first move only and stop. Say the capacity out loud before you look at the list: what fraction of a normal day is actually available.
When is this the wrong protocol?
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. Do not raise the target. The target is not the problem; the absence of a floor is.
What should a reader do in the first week on trying to build consistency?
Define the floor and run only the floor, including on the days you could do more. Needing more willpower. What is missing is a floor: a version small enough that bad days have an action rather than a decision.
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.