You built the perfect system. Color-coded, app-synced, beautiful. It worked for nine days. On day ten you forgot it existed, and by day fourteen you were back to sticky notes and dread, feeling like the failure was you.
It wasn’t you. The system was built for a brain that runs on steady fuel and reliable memory. Yours doesn’t. So the system was always going to break the first time your executive function dipped, and your executive function dips. That’s not a flaw to fix. It’s a fact to design around.
This is a guide to building systems that survive that dip. Not pretty systems. Not motivating systems. Systems with so little overhead that even your worst-functioning day can still run them. We’re going to trade chaos for cadence. Cadence is just a rhythm low enough that you can keep it.
Why your systems keep collapsing
Here’s the pattern almost every neurodivergent adult has lived. You hit a wall of overwhelm, you research hard, you build an elaborate system, and you feel a rush of relief and hope. Then maintenance starts. And maintenance is the part your brain wasn’t built for.
Most productivity advice assumes a brain that remembers to check the system, feels motivated to update it, and has steady enough capacity to do that every single day. That’s the neurotypical default the advice was written for. It quietly asks executive function to be the engine. For you, executive function is the exact thing in short supply. (If you want the full picture of what executive function actually is, start here.)
So the system you built was secretly running on borrowed fuel. As long as you had a good week, it held. The moment your capacity dropped, the whole thing needed more of you, right when you had less of you to give. That’s backwards. A system that demands the most maintenance on your hardest day is a system designed to fail you exactly when you need it.
And then comes the shame. You don’t blame the system. You blame yourself. You decide you’re lazy, or that you “can’t stick to anything,” and you brace yourself before building the next one, half-expecting to fail again. The collapse wasn’t a character problem. It was a design problem. You can fix design.
The Skeleton System: build for the bad day, not the good day
Here is the reframe that changes everything: stop building systems for the version of you that’s rested, focused, and motivated. That version is real, but she’s not the one who needs the system. Build for the version of you who’s flat, foggy, overstimulated, and running on empty. If the system works for her, it works for everyone. If it only works for your best day, it’s not a system. It’s a hobby.
I call this the Skeleton System. It’s the smallest possible structure that still does the one job you need it to do, built on three rules.
Rule 1: Externalize, don’t memorize. Your working memory is not storage. Every time a system relies on you to remember to check it, update it, or carry a step in your head, it’s leaning on the weakest part of your wiring. So put it outside your head. On the wall. On the counter. In a single place your eyes already land. If it lives in your memory, it doesn’t exist. This is the same principle behind a cognitive holding space: a trusted place outside your brain so you stop paying rent on remembering.
Rule 2: Minimum viable, not maximum optimal. The more steps a system has, the more places it can break. Each step is a fresh demand on task initiation, and task initiation is often the first thing to go on a low-capacity day. So cut. Then cut again. A three-step system you actually run beats a twelve-step system you admire and abandon. You’re not building the best system. You’re building the one that survives you.
Rule 3: Design for the dip. Assume your capacity will drop. Not “might.” Will. So build a floor. What’s the bare-minimum version of this system that still counts on a day when you’ve got nothing? That floor is the real system. Everything above it is a bonus.
Cadence over discipline. Discipline asks you to force the same output every day through willpower, and willpower is not a resource your brain restocks reliably. Cadence asks for a rhythm light enough that even a bad day can keep it. A rhythm you can keep beats a standard you can’t.
How to build a system that holds
Here’s how to put the Skeleton System into practice. Pick one area of life that keeps falling apart. Just one. Not your whole life. We’re building a single working system before we build five.
Step 1: Name the one job. What is the single thing this system has to do? Not five things. One. “Pay bills so nothing gets shut off.” “Know what’s for dinner so 5pm isn’t a crisis.” Write the one job in a sentence. If you can’t, the system is trying to do too much.
Step 2: Find the breakage point. Where did your last attempt at this die? It’s almost always one of two places: a step that asked you to remember something, or a step that asked you to start something on a low day. Circle that spot. That’s the part you’re going to externalize or shrink.
Step 3: Externalize the memory. Take everything the old system asked you to hold in your head and move it out. A visible checklist on the fridge. A standing alarm that does the remembering for you. A single notebook that holds it all. If you run multiple clients, projects, or roles, one external page per client beats one overloaded brain. (That exact approach is laid out in organizing on paper across multiple clients and the two-pen method.)
Step 4: Cut to the floor. Look at every step and ask: would this survive a day when I have nothing? If not, it’s not part of the floor. Strip the system down to what runs on empty. Maybe that’s “open the bills folder and pay anything red.” That’s allowed to be the whole system.
Step 5: Anchor it to something that already happens. A new system floating in space dies. A system tied to an existing habit holds. Stack the new step onto something automatic: while the coffee brews, after you brush your teeth, when you sit down at your desk. The existing habit becomes the trigger so you don’t have to generate the start from nothing.
Step 6: Add a co-regulation layer. Here’s the lever most advice skips. For a lot of ND folks, starting a hard task alone is the wall, not the task itself. Doing the boring or activation-heavy parts of your system alongside another person, in the same room or on a screen, seems to borrow their steadiness and make starting easier. This is the idea behind body doubling, and it isn’t just a vibe people report. A 2024 peer-reviewed study in ACM Transactions on Accessible Computing found that neurodivergent participants overwhelmingly used body doubling to help them initiate, stay with, and finish tasks (Tang et al., “Investigating Body Doubling,” ACM TACCESS, 2024). This isn’t accountability. It’s company. It’s why so many people finally run their system in a body-doubling session when they couldn’t run it solo. If the system keeps stalling even after you’ve shrunk it, the missing piece usually isn’t more discipline. It’s a person.
Step 7: Plan the recovery, not the streak. You will miss days. The question isn’t whether the system breaks. It’s how fast you get back in. Build the re-entry on purpose. One line: “When I fall off, I do the floor version once, and that counts as back on.” No starting over. No clean slate. You re-enter at the floor. A system you can fail and resume beats a streak you can only break. (If a single step is the thing you can’t make yourself start, the 5 executive function blockers will help you find which blocker is in the way.)
What this looks like in real life
Let me walk one all the way through, because the steps can feel abstract until you see them land on a real problem. Take laundry. Not glamorous, but it’s the system that quietly breaks more ND households than almost anything else.
The one job (Step 1): “Have clean underwear and clean work clothes.” Not “keep up with all the laundry.” Not “sort by color and fold within an hour of the buzzer.” One job. The breakage point (Step 2) is almost never the washing. It’s the gap between done and put away. The basket of clean clothes that lives on the chair for nine days while you dig through it every morning. That gap is where the old system died, every time.
So you externalize the memory (Step 3): the clean basket goes in your path, not in the laundry room you forget exists. You cut to the floor (Step 4): the floor version is not “wash, dry, fold, sort, and put away.” The floor is “run a load and dump the clean basket on the bed.” That’s it. A dumped basket of clean clothes beats a tidy hamper of dirty ones. You anchor it (Step 5) to something that already happens: you start a load every Sunday while the coffee brews, because the coffee always happens. And you add the co-regulation layer (Step 6) if it still stalls: fold during a body-doubling call, or on the phone with a friend, because the folding was never hard, the starting alone was. Then you plan the recovery (Step 7): when you skip a Sunday, you don’t owe two loads. You run one load the next chance you get, and that counts as back on.
Notice what we did not do. We did not buy a hamper system. We did not download a chore app. We did not build a rotation schedule that assumes you’ll feel the same every week. We built the smallest thing that survives the week you feel like nothing, and we let that be enough.
What this looked like for one member
One member came in furious at herself. She’d built and abandoned, by her count, more than a dozen planning systems. Apps, bullet journals, whiteboards, all of it. Each one worked for a week or two, then died, and each death added to a story that she was the problem.
We didn’t build her a better app. We did the opposite. We picked one job: knowing what had to happen each day so she stopped waking up in a panic. We threw out every step that asked her to remember or to start cold. What was left was almost embarrassingly small. A single index card each morning, three lines, filled out during a five-minute body-doubling session with the group. That was the whole system.
It held. Not because it was clever. Because it was small enough to survive her worst days, lived outside her head, and had people in the room when she started.
Then it got tested. A few weeks in, she hit a hard stretch, the kind that used to end every system she’d ever built. She missed the card four days running. The old story started up right on cue: see, you can’t stick to anything, here we go again. But this time the system had a re-entry built in. She didn’t owe four cards. She sat down at the next session, filled out one, and that counted as back on. No clean slate, no starting over, no shame spiral. She just picked the floor back up. That was the part that shocked her, not that she fell off, but that falling off was no longer the end of the system.
Months later she told us the card was still going. The thing that broke a dozen times finally held the moment she stopped building for her best day and built for her hardest one, and stopped treating a missed day as proof she was the problem.
Your next step
You don’t need a better app. You need a system small enough to survive the version of you who has nothing left, and people around you while you run it.
Inside ND Hive, you get both. Body-doubling sessions to borrow the activation you can’t generate alone. A community that has built and rebuilt these systems and will help you find your floor. Nobody keeping score.
Start your 7-day free trial and build one system that actually holds. You’re not broken. You’re not too much. You’re smart and capable. You can do anything with the right tools.