Last March I had a week where everything went wrong simultaneously. A client project stalled because of factors outside my control. A product shipment was delayed at customs. I got sick — not seriously, but enough to drain my energy to about 40% of normal. My daughter was home from school with the same bug. And the quarterly tax payment was due.
On my best days, I’m productive, creative, and energized. On that week, I was none of those things. And yet the business didn’t stall. Customer emails got answered. Orders got processed. Content was published. The tax payment went out on time. Not because I heroically pushed through — because the systems I’d built didn’t need me at my best. They needed me at 40%, following checklists and templates that my best-day self had created for exactly this situation.
Most founders build their businesses for their best days. They design workflows that require full energy, sharp focus, and available time. When a bad day hits — and bad days always hit — the whole system breaks because it was designed for conditions that don’t exist.
The alternative: design your systems for your worst day. If your business can function when you’re at 40%, it’ll thrive when you’re at 100%. That’s a much better foundation than a business that requires 100% every day and collapses when reality intervenes.
The Bad-Day Inventory
Before you can design for bad days, you need to know what your bad days actually look like. Not theoretically — specifically.
I tracked my energy, focus, and productivity for three months and identified four distinct categories of bad days:
The Low-Energy Day. You’re physically depleted — sick, sleep-deprived, or just running on empty. You can think but you can’t create. You can follow instructions but you can’t generate ideas. Your body is present but your creative capacity is near zero.
The Distracted Day. Your energy is fine but your attention is fractured. Personal issues, family demands, a crisis in another area of life. You’re physically at your desk but mentally somewhere else. You can do mechanical tasks but can’t sustain focus on anything complex.
The Emotional Day. Anxiety, frustration, discouragement, or self-doubt is dominating your mental state. A rejected proposal, a lost client, a critical comment, or just the general weight of uncertainty. Your technical capacity is intact but your confidence and decision-making quality are compromised.
The Overwhelm Day. Too many things need attention simultaneously. Every task feels urgent. You don’t know where to start, so you don’t start anywhere. You spend the day trying to figure out what to do rather than doing anything.
Each type of bad day requires different system design. A system that works for low-energy days might not help on overwhelm days. The specificity of your bad-day design determines how effective it actually is when you need it.
The Minimum Viable Day
For each bad-day type, I’ve defined a “minimum viable day” — the absolute minimum productive output that keeps the business moving forward without requiring anything close to peak performance.
Low-Energy MVD: Process the inbox (respond to anything urgent, file or defer everything else). Run through the daily operations checklist (a one-page document that lists every task that must happen daily). That’s it. Two hours of low-intensity work that keeps the wheels turning.
Distracted MVD: Handle three pre-defined priority tasks from the weekly plan (the tasks are chosen in advance during the weekly review, so no decision-making is required). Each task should take no more than thirty minutes and require no deep focus.
Emotional MVD: Do one thing that rebuilds confidence — send an invoice, publish a piece of content, or reach out to a past client. Then do maintenance work that feels productive without requiring emotional risk. Avoid making any strategic decisions on emotional days.
Overwhelm MVD: Open the priority list and do item number one only. Not items one through five. Item one. Complete it. Then decide whether to do item two or stop for the day. The overwhelm MVD is about reducing the scope of attention to a single thing, which breaks the paralysis that comes from trying to hold everything at once.
The MVD concept connects to the ship it ugly philosophy. On bad days, you’re not producing your best work. You’re producing minimum viable work that keeps the business alive until your capacity returns. Ugly output on a bad day beats zero output on a bad day, every time.
Designing Systems That Don’t Need Your Best Self
The systems that survive bad days share three characteristics:
Characteristic 1: They rely on checklists, not judgment.
When your cognitive capacity is reduced, judgment suffers first. Checklists bypass judgment by converting “figure out what to do” into “do this, then this, then this.” The thinking was done when the checklist was created (on a good day). The execution is mechanical (on the bad day).
My daily operations checklist has twelve items. On a good day, I work through them in about ninety minutes while simultaneously handling other things. On a bad day, the same twelve items take two and a half hours because I’m slower, but they still get done because no single item requires creative thinking or complex judgment.
Characteristic 2: They have built-in defaults.
Defaults are pre-made decisions that eliminate the need to think when thinking is hard. My content system has a default: if I can’t write original content this week, I republish a popular older piece with a new introduction. My customer service system has a default: if an inquiry is complex and I can’t handle it today, I send an acknowledgment template (“Thanks for reaching out. I’ve received your message and will respond in detail within 48 hours”) that buys time without leaving the customer hanging.
Defaults aren’t ideal. They’re minimum acceptable outcomes that prevent zero output. On good days, you exceed the defaults. On bad days, the defaults keep you functional.
Characteristic 3: They separate decisions from execution.
The weekly planning session (which happens on Sunday evening when I’m rested and clear-headed) makes the key decisions for the week: what are the priorities, what gets done each day, what can wait. The daily execution simply follows the plan. On a bad day, I don’t have to decide what to do. I open the plan and do the first thing on the list.
This separation means my best-day self is making the strategic decisions and my worst-day self is only responsible for execution. The execution is still productive because the decisions were made when I was sharp enough to make them well.
The Pre-Built Bad-Day Toolkit
Beyond the system design, I maintain a literal toolkit — a collection of resources prepared in advance for specific bad-day scenarios:
The “I can’t write” folder. Ten to fifteen pre-drafted social media posts, email drafts, and blog outlines that only need minor editing to publish. When creative writing is impossible, I can still publish by polishing work my good-day self created.
The “I can’t think” task list. Twenty mechanical tasks that need doing but never feel urgent enough to prioritize: organizing digital files, updating contact records, cleaning up bookmarks, processing receipts. These tasks require zero creative energy and produce genuine (if unglamorous) progress.
The “I can’t people” templates. Pre-written responses for common email types: new inquiries, follow-ups, scheduling requests, referral thanks. On days when drafting even a simple email feels exhausting, the templates turn communication from a creative task into a fill-in-the-blanks task.
The “I can’t decide” protocol. A one-page document that says: defer all non-urgent decisions to tomorrow. For urgent decisions, use the simplest available option. Don’t make strategic decisions on bad days. This protocol has saved me from several decisions I would have regretted — decisions made from a place of anxiety, exhaustion, or frustration that seemed urgent in the moment but weren’t.
Building this toolkit takes about four hours of good-day time. That four-hour investment has saved me dozens of hours of bad-day struggling and prevented the worst outcome of all: bad days that produce nothing, which then create guilt and frustration that make the next day worse, creating a downward spiral that can eat an entire week.
The Recovery System
Bad days aren’t just about surviving them. They’re about recovering from them efficiently so they don’t cascade into bad weeks.
My recovery system has three components:
Physical recovery. After a bad day, the priority is sleep and rest. Not “catching up” on work. Not staying late to compensate. Rest. The most reliable predictor of tomorrow’s performance quality is tonight’s sleep quality. Sacrificing sleep to compensate for a bad day guarantees two bad days instead of one.
Mental recovery. After a bad day, I review what got done (the MVD output) and explicitly acknowledge it as sufficient. Not great. Not what I wanted. Sufficient. This prevents the self-criticism spiral where a bad day’s output is judged against a good day’s standards, creating guilt that drains the next day’s energy.
System recovery. After a particularly bad stretch (three or more bad days in a row), I do a brief system review: did the systems work? Were the checklists followed? Were the defaults adequate? Did the bad-day toolkit have what I needed? Any gaps get fixed immediately while the experience is fresh.
The compound effect of consistent showing up, even on bad days, vastly outperforms the pattern of brilliant good-day performance followed by zero bad-day output. Five mediocre days produce more total progress than three brilliant days and two zeros. The systems are what make the mediocre days productive enough to count.
Why This Matters for Long-Term Success
Over a year, a typical founder has roughly 200 good or average workdays and roughly 50 bad ones (weekends and vacation excluded). If bad days produce zero output, that’s 50 lost days — almost 25% of your productive capacity, gone.
If bad days produce even 40% of normal output (thanks to systems designed for it), those 50 days now produce the equivalent of 20 good days. That’s 20 additional productive days per year that would otherwise have been lost.
Twenty days of work is roughly a month. A month of additional productive output per year, every year, compounds into a significant competitive advantage over founders who lose that time to unproductive bad days.
The velocity principle isn’t just about moving fast on good days. It’s about maintaining movement on every day. Systems designed for bad days are what make that possible.
Takeaways
- Identify your four bad-day types (low-energy, distracted, emotional, overwhelm) and design a minimum viable day for each — the absolute minimum productive output that keeps the business functioning.
- Build systems that rely on checklists (not judgment), built-in defaults (pre-made minimum-acceptable decisions), and separated decisions from execution (plan on good days, execute on bad days).
- Maintain a pre-built bad-day toolkit: pre-drafted content, mechanical task lists, communication templates, and a decision-deferral protocol. Four hours of preparation saves dozens of hours of bad-day struggling.
- Prioritize physical recovery after bad days — sleep and rest, not catching up. Sacrificing sleep to compensate for a bad day guarantees two bad days instead of one.
- Over a year, systems that turn zero-output bad days into 40%-output bad days recover the equivalent of a full month of productive work. That compound advantage separates builders from dreamers.
