The short version: Most productivity systems collapse under real health pressure because they assume a stable body. The ones that survived mine were ruthlessly flexible, brutally honest about capacity, and built around damage control not optimization.
Worth reading next: Best Productivity Tools and Apps for Small Business: What Works (Not t.
What breaks when your health breaks
Five years ago my body stopped cooperating. Not dramatically. Not a single crisis day where everything changed. Instead, a slow cascade: fatigue that didn't lift, infections that lingered, cognitive fog that made email feel like reading Russian. For two years I tried to run my business using productivity systems designed for healthy people with stable energy.
I failed spectacularly.
Every system I'd built (and I'd built many: time blocking, Kanban boards, the Pomodoro Technique, theme days) assumed a constant supply of fuel. None of them worked when the fuel tank was unpredictable. I'd wake up with energy and make plans for the day, then hit a wall at 2 PM that hadn't been there at 9 AM. I'd commit to weekly themes and be unable to execute them. I'd block time for deep work and spend it staring at the screen unable to think clearly.
The real discovery wasn't that I needed a new system. It was that I needed the opposite: systems designed to fail gracefully when capacity changed hour by hour.
System one: the three-bucket method
Standard productivity advice tells you to identify your three to five highest-impact tasks each day and focus there. That's nonsense when your energy is unpredictable. Instead, I built three buckets and assigned everything I needed to do to one of them.
Bucket one: things that must happen today. Not "would be nice." Must. I kept this list to one to three items. For my business, this might be responding to a paying client's urgent question or hitting a firm deadline. No more than 90 minutes of work total.
Bucket two: things that would be great if I did them but won't break anything if I don't. These were the 60 to 70 percent of my actual workload. Content I wanted to write, internal improvements, research, relationship building. I aimed to do two to four hours of this if I had the energy.
Bucket three: things that could wait indefinitely. Filing, reading industry newsletters, learning new tools, attending optional meetings. These were my surplus energy tasks, and on bad weeks, I'd do none of them for two months straight.
The critical piece: I wrote these buckets down every Sunday. Not optimistically ("I'll finish the deep work project this week"). Honestly. Looking at my energy average for the past two weeks, I'd decide what was realistic. On weeks where I'd had four good days, bucket two got more ambitious. On weeks where I'd averaged one good day, bucket two shrunk to one or two items.
This method survived because it didn't require me to be consistent. It required me to be honest.
System two: the 40-minute work block
I ditched 90-minute deep work blocks the moment I realized I rarely had 90 minutes of clear thinking available. Instead, I built my work around 40-minute blocks.
Here's the specifics: I'd set a timer for 40 minutes, work on one task, and then take a 10-minute break. The break was non-negotiable: walk, water, stare out the window, chat with my partner. Not email. Not Slack. Not thinking about the next task.
The reason this survived my health crisis is counterintuitive. By shortening the block, I could do more. If I told myself "I have four hours for deep work," my brain would panic about whether I had four hours of mental fuel. I'd procrastinate. If I told myself "I have forty minutes," something in my nervous system would relax. I could do one forty-minute block on a bad day. I could often do three or four on a good day.
Over a week, that's 40 minutes times 15 to 20 blocks, depending on my health. Even on my worst weeks, I'd get one or two blocks done. On good weeks, I'd stack them and get genuine momentum.
I still use this. It's 2026 and I'm healthier, but I haven't changed it because it works regardless of my state. The system doesn't care if I'm well or unwell. It just asks: can you give me 40 minutes?
System three: the "done list" not the to-do list
This is the one point I find almost nowhere in productivity writing, and it's why most systems fail under health pressure: people track what they haven't done.
Every productivity app defaults to showing you tasks you haven't completed. That's motivating when you're healthy and making steady progress. It's demoralizing and literally unhelpful when you're ill. During my worst year, I'd look at my to-do list and see 47 uncompleted tasks stacked up. The list was supposed to be motivating. Instead, it was evidence of failure.
I stopped maintaining a to-do list. Instead, I kept a done list.
Every single day, I'd write down what I completed. Monday: responded to three client emails, wrote 600 words on the AI productivity piece, attended one meeting. Tuesday: took it easy, did one bucket-one task, read two industry articles. Thursday: worked three 40-minute blocks, completed one paid project.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
I kept this in a simple Google Doc, one line per day. At the end of each week, I'd scroll up and count the lines. In my worst weeks, I'd see five to six lines. In good weeks, ten to 12. But what I saw was evidence. Not of failure, but of work that happened.
This sounds like a small shift. It isn't. There's a neurological difference between "I still have 40 tasks left" and "I completed seven things this week including one that pays my rent." One is a wound. One is data.
The system survived because it measured reality instead of hope.
The honest point nobody writes about
Here's what most productivity advice skips: sometimes the most productive thing you can do is stop.
I spent my first two years of illness fighting it. I'd take a day off and feel guilty. I'd have low energy and try harder. I'd fail to hit my targets and blame my systems instead of my capacity. This is what sick people do in a culture obsessed with optimization: we blame the method.
The turning point wasn't finding a better system. It was accepting that some weeks I would produce 10 percent of normal output and that was the honest number, not a failure of discipline.
Once I accepted that, everything changed. I could plan around it. I could set expectations with clients that were real. I could stop writing frantically on good days to make up for bad ones. I could just do the work that was possible.
The systems that survived weren't impressive. They weren't optimized. They were built around the question: what gets done when everything is difficult? And the answer, often, was: less. But less that was real.
How I'd rebuild these systems today
I'm not going to pretend I use all of these now. I'm healthier than I was. But pieces of all three remain because they work when things get hard again, and they know they will.
If you're starting today, here's the practical version:
- Sunday planning: spend 30 minutes reviewing your actual output from the past week. Not what you aimed for. What you did. Then set next week's buckets based on that honest number.
- Time blocks: set a timer for 40 or 50 minutes. Don't negotiate during the block. Don't check email or messages. When the timer goes off, stop completely.
- Done documentation: keep a simple list (Google Doc, notebook, Slack channel) of what you finish each day. Don't plan what you'll do. Record what you did.
- Capacity conversation: be honest with someone about your realistic output. A partner, a mentor, a therapist. Say the number out loud. "I think I can do 15 hours of real work this week." Not 40. Not 20. Your actual honest estimate.
These aren't original ideas. They're repackaged versions of what good leaders already know works: honesty, boundaries, and celebrating actual progress instead of imagined potential.
The crisis part was just the forcing function that made me stop pretending.
Frequently asked questions
What do you do when a bucket-one task doesn't get done?
You find out why and adjust next week. Usually, it means either that task wasn't bucket-one critical (it can move to bucket two), or you had less capacity than expected (and next Sunday's buckets need to shrink). I don't carry incomplete bucket-one tasks forward. I either do them or I reclassify them.
How do you handle client work with unpredictable energy?
I build buffer time into all deadlines and I'm honest about my turnaround. Instead of promising three-day turnaround on a project, I say five to seven. I then deliver on day three or four most weeks, which feels like a win. On bad weeks, I'm still on time. No crisis, no client anger, no emergency pressure.
Does the done list ever feel like you're celebrating the bare minimum?
Yes. On bad weeks, absolutely. And that was the entire point. I needed to learn that completing three tasks on a low week and 12 tasks on a high week were both acceptable and both honest. Once I made peace with that, the shame lifted and I could think clearly about what was realistic.
Can these systems work if you're not dealing with health issues?
Completely. They work better for healthy people because you get more capacity to work with. The systems just don't pretend your capacity is unlimited or unchanging. You'll find yourself doing more work in less time because you're working within your actual energy envelope instead than fighting against it.
Related reading: The AI Tools I Use to Run My Marketing Business and What Each Replaced and A Realistic Social Media Schedule for a Busy Founder.
For the bigger picture, see my full guide to productivity.
