You Don’t Need a Better Protocol. You Need to Stop Switching.
The Standard Stack Protocol - Optimization has become procrastination. The real advantage is a system you can execute for 90 days without interruption.
You have read enough about optimization. Cold plunges at 5 AM. Twelve supplements before breakfast. Sleep scores tracked to the third decimal. You adopt a new protocol every three weeks because the last one “stopped working”—or more accurately, you stopped doing it.
The search for the perfect system is a distraction. It keeps you busy enough to avoid running a boring, reliable one.
Protocol 03 is not about peak performance; it is about floor performance. It is the baseline output you can guarantee on your worst day, not just your best. That requires a stack so locked-in it requires zero decision-making.
Published by Performance Protocol
The Real Problem Is Not Your Protocol
Most people are not under-optimized. They are under-consistent.
Under-optimized: Your inputs could be better calibrated—slightly adjusted sleep timing, higher protein density, or a different training split. This is a real problem, but it is a second-order one.
Under-consistent: Your inputs change based on how motivated you feel, what you read last, or how “busy” the morning got. This is the actual performance killer.
Variability in inputs produces variability in output. You cannot performance-manage a system you keep changing. James Clear puts it directly: “You do not rise to the level of your goals. You fall to the level of your systems.” The more accurate reading is: Stop dismantling the one you have. The “audit cycle” is a trap. You run a protocol for two weeks, decide it isn’t working, and switch. You aren’t measuring the protocol; you are measuring your mood. The Standard Stack is about stopping the search long enough to actually build a data set.
The Architecture of the Standard Stack
The Standard Stack consists of four non-negotiable categories. Every input has a default. These defaults are not audited mid-week. They run until there is a structural reason to change them—not a motivational one.
1. Sleep: The Anchor
Consistency of wake time is the primary lever for sleep quality, more reliable than bedtime. You are not optimizing sleep by tracking it obsessively; you are optimizing it by anchoring it.
The Lock: A fixed wake time. Not a “target,” a fixed time.
The Rule: Set it and do not move it for weekends or travel unless absolutely unavoidable.
The Insight: Peter Attia is unambiguous in Outlive: sleep is the most powerful longevity lever available, and timing consistency is more important than duration.
2. Nutrition: The Template
Defaults reduce decision fatigue and eliminate the “I’ll figure it out later” problem that turns into poor choices by 7 PM.
The Lock: Three “template” meals with known macros.
The Rule: You should be able to reconstruct what you ate in a given week without looking at an app because you ate the same core meals you always eat.
The Insight: Use “Modular Eating”—the same base proteins and fats, varying only the seasoning or greens. High compliance lives in low variety.
3. Movement: The Maintenance
The goal is not the “best” training program; the goal is the one you will actually run for twelve consecutive weeks without revision.
The Lock: 3–5 sessions per week with a fixed, repeatable structure.
The Rule: If you are still on the same program in month three, it is working.
The Insight: Progress is a byproduct of repetition, not novel stimulation. Stop “confusing the muscles” and start convincing the mind to show up.
4. Cognition: The Routine
Whatever puts you into focused output before email, Slack, or other people’s agendas reach you.
The Lock: A fixed 20–45 minute start-of-day sequence.
The Rule: The same sequence, every day, before reactive work begins.
The Insight: Marcus Aurelius ran one for decades: “Confine yourself to the present.” It wasn’t a meditation on ambition, but a discipline of attention.
Why Boring Systems Outperform Sophisticated Ones
The Standard Stack works because it removes willpower from the equation. Willpower is a finite resource that depletes across the day. Systems that depend on it will fail when it runs low—which is exactly when you need them most.
The best system is the one that runs when you feel terrible, not just when you feel ready.
Ryan Holiday frames it simply in Discipline Is Destiny: “Routine is a form of freedom.” It sounds paradoxical until you understand what it actually frees you from: the daily negotiation with yourself.
High performers do not have better willpower; they have fewer decisions to make. When your sleep, fuel, and movement are decided in advance, your cognitive resources are fully available for the work that actually moves the needle.
Where the Stack Breaks
There are three predictable failure modes predictable enough to name in advance:
The Exception Becomes the Rule: One disrupted day becomes a disrupted week. Disruptions are not data—they are just disruptions. Run the default the next day. As Epictetus noted: “It’s not what happens to you, but how you react to it matters.” The stack does not care about your bad day. Run it anyway.
Complexity Creep: More inputs feel like more commitment. They aren’t. They are more points of failure. The Standard Stack should fit on a single index card. If it doesn’t, simplify it.
Optimization as Procrastination: You spend more time refining the stack than running it. This is the hardest to self-diagnose because it feels productive. If you have changed your program in the last four weeks, ask yourself: Did I complete the last one, or did I just get bored?
The Single Action Required: Lock the Stack
Do not refine. Do not optimize. Lock it.
Write down your current defaults across the four categories. Put them somewhere you see them daily. Treat them as closed decisions for the next 90 days.
When you read about a “better” supplement or a “superior” split, note it in a separate file. Review it at the 90-day mark. Do not implement it mid-cycle.
The stack you run consistently for 90 days outperforms the perfect stack you run for two weeks and replace. There is no protocol so good that inconsistency cannot break it.
Stop auditing your stack. Start locking it.
Part of the Performance Protocols series. Protocol 03 of 06.
Published by Performance Protocol