Daniel sent us this one — a long one, and honestly it's the kind of prompt that could be its own manual. He's been on this kick lately, tackling life systems from a non-pharmacological angle. The core idea is something you hear a lot with SSRI meds: use the window where the medication is doing its job to build the therapy skills that outlast the prescription. He's applying that same logic to ADHD — if you're on something that gives you reliable focus, that's the moment to build the organizational scaffolding that felt impossible before.
The scaffolding he needs right now is intense. Ten months ago he and Hannah had Ezra, their son, and they're parenting completely solo — both sets of grandparents are outside Israel, the war's made visits impossible so far, and they just started shared daycare last week. So they're in that raw, no-backup phase of new parenthood.
He gave us a snapshot of where things are cracking. Yesterday he ate two slices of cheese on dubiously fresh bread because he forgot to shop. His read on it isn't "I was lazy" — it's that when life gets harder and obligations stack up, the stuff that was barely held together by improvisation starts to fall apart. For him lately, that's been self-care.
He's asking us for something really specific. Not general productivity advice. He wants a user manual for his life right now — a source of truth that covers everything: chores, business tasks, taxes, invoices, Ezra's schedule, dinner, wake-up times. Something he and Hannah can literally put in their back pocket, paper or app, that works for brains that find complicated things easy but struggle with the daily stuff it takes to be a functional human.
He mentioned those two A-four checklists they had taped to the door during the Iran-Israel war — one for staying prepared when they were running back and forth to bomb shelters. Go-bag by the door, phone charged, phone off silent. When they were exhausted and sleep-deprived, those two pages were anchors. He wants that same thing, but for everything.
By the way, today's script is coming from DeepSeek V four Pro. Feels appropriate for a topic about precision and discipline.
I'll take it. Alright, let's dive in.
The first thing I want to name — and I think this is the frame Daniel's already operating in — is that what he's describing isn't a motivation problem. It's an executive function load problem. He's got a newborn, he's running a business, they're preparing for a move, they're handling apartment crises. That's not a situation where you just need to try harder. That's a situation where your working memory is completely saturated.
And the cheese-on-bread dinner — he's not saying he didn't know he needed groceries. He's saying the system for making sure groceries happened wasn't resilient enough to survive a day where both parents were maxed out. The question is what kind of system survives that.
Let's talk about what actually works and what doesn't, especially for ADHD brains. Daniel mentioned Getting Things Done, GTD, the David Allen method. He said he's tried it, and the result is a swarm of to-dos and calendars that becomes its own source of overwhelm.
Which is the classic GTD failure mode for ADHD. The system is designed to get everything out of your head, which is good — but then it presents you with a list of two hundred next actions, and for someone with executive function challenges, that list is paralyzing. You haven't reduced the cognitive load, you've just moved it to a different medium.
Russell Barkley, one of the leading ADHD researchers, argues that the core deficit in ADHD isn't attention, it's performance — the gap between knowing what to do and actually doing it. A to-do list helps with the knowing part but does nothing for the doing part. For someone with ADHD, seeing forty-seven items on a list doesn't create motivation, it creates shutdown.
If GTD and standard to-do apps aren't the answer, what does a system look like that actually bridges that knowing-doing gap?
I think we need to start with a principle that's counterintuitive for productivity nerds but essential for ADHD brains: you don't want a system that shows you everything. You want a system that shows you only what's relevant right now, in this context, at this moment. The overwhelm Daniel's describing — "I find it hard to keep everything in view at once" — the solution isn't to get better at keeping everything in view. It's to stop trying to keep everything in view.
Instead of one master list, you want something more like a series of lenses. When you're in the kitchen at six PM, you see the kitchen-at-six-PM lens. When you're at your desk on a Tuesday morning, you see the desk-Tuesday-morning lens.
And this connects to something Daniel already knows works: those bomb-shelter checklists. Those worked because they were context-specific, short, and physically present where he needed them. He didn't have to remember to check an app. The checklist was on the door he was walking past. The trigger was environmental.
Let's build from that. If the bomb-shelter checklist model worked, what's the equivalent for daily life? You don't create one checklist, you create maybe five or six, each tied to a specific context, each short enough that it doesn't trigger overwhelm.
The magic number for an ADHD-friendly checklist is between three and seven items. Working memory capacity for most adults is about four chunks of information. For someone with ADHD, that working memory is even more constrained under stress. If your morning routine checklist has twenty-three items, you've already lost.
Alright, let's get concrete. Daniel asked us to draft a user manual — area by area, block by block. What are the domains we need to cover?
I'd break it into six domains. One: morning routine and Ezra launch. Two: work operations — invoices, taxes, client work. Three: household maintenance — groceries, laundry, cleaning. Four: evening routine — dinner, Ezra wind-down, bedtime. Five: personal self-care — the thing Daniel said is currently suffering. And six: the weekly reset — a dedicated time to review and restock all the other systems.
That's a good breakdown. And the key insight for each domain is that the checklist shouldn't be a list of tasks, it should be a list of triggers. A task says "do laundry." A trigger says "when you walk past the laundry basket and it's full, start a load." One requires you to remember to check. The other is activated by the environment.
That's backed up by what we know about prospective memory — the ability to remember to do something in the future — which is one of the most impaired cognitive functions in ADHD. Time-based prospective memory — "remember to do X at three PM" — is especially bad. But event-based prospective memory — "when Y happens, do X" — is much more reliable. So designing triggers around events rather than times is a real adaptation.
For the morning routine, instead of "seven thirty: wake Ezra," you'd have "when your alarm goes off, go to Ezra's room." The alarm is the event trigger, not the clock.
And then you chain them. Alarm goes off, you're in Ezra's room. You pick him up, you're in the kitchen. You're in the kitchen, the breakfast checklist is on the fridge. Each step triggers the next. This is called a routine chain, and it's one of the most effective strategies for ADHD because it reduces the number of decisions you have to make.
Decision fatigue is the other piece here. When you're exhausted, every decision costs more. A checklist that removes decisions — not just reminds you of them — is worth ten times more than a to-do list.
Let's talk format. Daniel said paper or app, doesn't matter. For years, the productivity world has been pushing digital — Todoist, Notion, Obsidian. And for certain things, digital is great. But for context-specific, environment-triggered checklists, paper has real advantages.
I lean digital for most things. Make your case.
First, paper is spatially stable. Your brain encodes information partly by where it is in physical space. A checklist on the fridge is in the same place every time — that spatial consistency aids recall. An app requires you to navigate to it, and the screen looks different depending on what else is open. Second, paper doesn't have notifications, but it also doesn't have distractions. You open your phone to check a checklist, and there's a WhatsApp message, an email, a news alert. For an ADHD brain, that's a trap. Third, paper is always on. It doesn't need charging, it doesn't crash, it doesn't require an update. It's just there.
Those are solid points. But paper isn't searchable, isn't editable without a pen, and you can't set reminders on it.
So the right answer is a hybrid. Paper for the daily context-specific checklists — the things you need to see in the moment, in the physical space where the action happens. Digital for things that need to be captured, stored, and retrieved on a longer time horizon — tax documents, client contracts, medical records.
Paper checklists in the kitchen, by the door, in the bathroom, maybe one on the desk. And a digital system for the archive and the calendar.
And for the digital side, I want to recommend something specific: a plain text file. Not an app, not a platform, just a single markdown file — or a small set of them — that serves as the canonical source of truth.
Why plain text over something like Notion or Todoist?
Plain text is future-proof — you can open it on any device, any operating system, forever. It's fast — no loading screens, no sync delays. It's distraction-free. And critically for ADHD, it's infinitely flexible. You're not fighting the app's opinion about how you should organize things. You can structure it exactly the way your brain works.
That last point is underrated. Most productivity apps have an opinion — GTD apps want you to do GTD, kanban apps want you to do kanban. If your brain doesn't work that way, you spend more energy adapting to the tool than the tool saves you. And for someone like Daniel, an open source developer, a plain text file is probably the most natural thing in the world. He can version-control it with Git. Zero learning curve.
Alright, so we've got a format recommendation: paper checklists for daily context-specific stuff, a plain text file for the master reference. Now let's actually build the content.
Let's go domain by domain. And I want to structure each domain the same way: first, the non-negotiable minimum — the three to five things that absolutely must happen. Second, the triggers — what in the environment prompts each action. Third, the failure modes — what typically goes wrong and how to recover.
Non-negotiable minimum: Ezra is fed, dressed, and delivered to daycare. Everything else is bonus. The triggers: alarm one is the wake-up trigger. Walking into Ezra's room triggers the diaper-and-clothes sequence. Walking into the kitchen triggers the breakfast sequence — and the breakfast checklist is literally taped to the cabinet above where the breakfast food lives. The checklist says: bottle or solids depending on age, bib, wipes within reach, check the daycare bag is packed.
The daycare bag itself should have a checklist taped to it. Spare clothes, diapers, wipes, whatever the daycare requires. You check it the night before as part of the evening routine, not in the morning when you're rushed.
Anything that can be done the night before, do it the night before. The morning checklist should be as short as humanly possible. If it has more than five items, you've got things on there that belong in the evening.
The evening routine needs to include prep for the next morning. What's that look like?
Evening is two sub-domains. There's the Ezra wind-down — dinner, bath, bedtime routine, story, lights out. And then there's the adult reset — where the prep for tomorrow happens. Non-negotiable for Ezra: dinner happens, some form of hygiene happens, he's in bed at roughly the same time every night. Non-negotiable for the adult reset: daycare bag is packed, tomorrow's breakfast is staged, a quick scan of the kitchen, and — this is the one Daniel specifically needs — a two-minute check on tomorrow's meals. Do we have something for dinner? Do I need to defrost something? Is a grocery run needed?
The meal check is what would have prevented the cheese-on-bread situation. It takes two minutes the night before. If you try to figure it out at six PM when everyone's hungry and tired, it takes thirty minutes and you end up eating cheese on questionable bread.
Now, household maintenance — this is the one that tends to sprawl, because it includes groceries, laundry, cleaning, apartment repairs, bills. It's the domain most likely to generate the "swarm" Daniel talked about.
We need to be ruthless about what goes in the daily and weekly checklists versus what goes in the master reference. The daily household checklist is maybe three items: dishes done or at least contained, trash taken out if full, and a quick floor scan for hazards now that Ezra's crawling — Daniel mentioned he's been doing that with a headlamp, which is honestly a great image.
The weekly household checklist is where groceries and laundry live. I'd recommend a fixed day and time for each. Saturday morning, groceries. Sunday afternoon, laundry. The specific day doesn't matter, but the fixity matters enormously. If it's "I'll do groceries when we run out of things," you're always reacting. If it's "Saturday morning is grocery time, period," it becomes a rhythm, not a decision.
For ADHD brains, removing the decision is the whole game. Every decision you remove is cognitive bandwidth you get back.
Now, the meal planning that feeds into that grocery run — that's where a simple reference document helps. A list of five to seven meals that you know how to make, that everyone will eat, that use mostly pantry staples. When you're planning the week's meals, you pick from that list. You're not inventing new dinners every week. You're rotating through a known set.
That sounds boring until you're a sleep-deprived parent, at which point it sounds like salvation. What about the business domain? Daniel's self-employed, he's got invoices, taxes, client work.
Business is tricky because it's the domain where GTD-style capture actually is useful — you do need to track commitments, deadlines, and ideas. But the overwhelm problem is the same. The solution is to separate the business domain into two layers: the operational layer and the strategic layer. The operational layer is the stuff that must happen on a schedule — invoices go out, taxes get filed, client deliverables get shipped. That layer should be handled by a small set of recurring checklists, same as household. The strategic layer — project planning, business development, creative work — that's where you use a more flexible system.
The operational layer is where most ADHD freelancers get into trouble. Invoices don't go out because there's no trigger. Taxes don't get filed because the deadline feels abstract until it's urgent. The fix is to make the operational stuff as automatic and trigger-based as the household stuff.
I'd recommend a weekly business admin block — maybe two hours on a Monday morning or Friday afternoon. During that block, you run through a checklist: send outstanding invoices, log expenses, check bank balances, review the coming week's deadlines, file anything that needs filing. The checklist is five to seven items. You do it every week at the same time. It becomes a rhythm, not a panic response.
For taxes specifically, I'd add a monthly check — just a five-minute scan to make sure you're setting aside enough, that your records are in order, that you're not going to get a nasty surprise. Small, frequent doses make tax stuff boring and routine instead of terrifying and annual.
Alright, we've covered morning, evening, household, and business. What about personal self-care? That's the domain Daniel said is currently suffering.
This is the hardest to systematize because it's the easiest to de-prioritize. When Ezra needs something and a client needs something and the apartment needs something, your own needs slide to the bottom. And for someone with ADHD, self-care tasks often don't generate enough urgency to break through the executive function barrier until there's a crisis.
Part of the answer is to stop treating self-care as a separate domain and instead bake it into the existing checklists. The evening adult reset includes "brush teeth, wash face, go to bed by X time." The morning checklist includes "eat something before you leave the house." It's not a separate regimen, it's just part of being a functional human, and it's on the list.
I'd add one thing to the weekly reset: a quick self-check. Am I sleeping enough? Am I eating actual meals? Am I getting any time that isn't work or parenting? If the answer to any of those is no for more than a week, that's a red flag.
We've got our six domains. Now the question Daniel actually asked: how do you use this thing? What's the workflow? Because having the checklists is only half the battle. Actually consulting them is the other half.
A checklist you don't look at is just decoration. And for ADHD brains, the "out of sight, out of mind" problem is real. If the checklist is in a drawer or buried in an app, it might as well not exist.
Placement matters enormously. Each checklist lives in the physical location where the actions happen. The morning checklist is on the bedroom door or the bathroom mirror. The kitchen checklist is on the fridge or the cabinet. The evening checklist is wherever you wind down. The business admin checklist is on your desk, literally taped to the monitor.
The weekly reset checklist — where does that live?
I'd put that one in a prominent place too, maybe the fridge or a family command center. But the weekly reset is also a good candidate for a digital reminder, because it's a once-a-week thing that's easy to forget. A recurring calendar event with a notification: "Saturday morning, weekly reset, check the fridge list.
The paper checklists are the execution layer, the digital calendar is the trigger layer for things that don't have a natural environmental trigger, and the plain text master file is the reference layer. It's where you store the list of go-to meals, the tax calendar, daycare contact info, pediatrician's number, the moving checklist. You don't look at it every day. You consult it when you need to update something or when a situation arises that isn't covered by the daily checklists.
Let's talk about what happens when the system breaks. Because it will break. Daniel and Hannah are going to have days where the morning checklist doesn't get looked at, the groceries don't get done, and dinner is cheese on bread again. What's the recovery protocol?
This is crucial, and it's something most productivity systems get wrong. They assume compliance. They don't have a failure mode. For ADHD, the failure mode is the most important part of the design. Because shame spirals are real — you miss a day, you feel bad, you avoid the system, you miss more days, the system collapses. The recovery protocol has to be: no shame, just reset.
At the top of each checklist, I'd put a one-line note: "If you're seeing this for the first time in a while, that's fine. " It sounds cheesy, but it's a deliberate design choice. It lowers the barrier to re-entry. The system doesn't judge you for falling off. It just invites you back.
The emotional experience of using a productivity system matters. If the system makes you feel like a failure every time you look at it, you'll stop looking at it. And that's another argument for paper over apps. An app can show you a red badge with fifty-three overdue tasks. That's designed to create urgency, but for ADHD it often creates avoidance. A piece of paper doesn't shame you. It just sits there, patient, waiting for you to come back.
Now, Daniel mentioned the "medication as a window" concept — using the period of reliable focus to build the skills and systems. How does that connect?
This is where timing matters. If Daniel is on a medication that gives him a window of reliable executive function — say, a few hours in the morning — that's the time to do the system-building work. Not the daily execution, but the initial setup. Designing the checklists, printing them, taping them up, creating the plain text file, setting up the calendar reminders. That's cognitively demanding work that benefits from sustained focus. Do it during the window.
Then the daily execution — running through the checklists — ideally becomes automatic enough that it doesn't require that same level of executive function. You front-load the cognitive work so that the daily stuff runs on habit and environmental triggers. There's a concept from behavioral economics called "choice architecture." You structure the environment so that the default option is the one you want. If the checklist is on the fridge, the default is checking the list. If the go-to meals are posted in the kitchen, the default is picking from that list instead of staring into the fridge at six PM.
For someone with ADHD, that's especially powerful because it reduces the number of decision points. Every decision point is a potential failure point. Fewer decisions, fewer failures.
There's a trap here, though. The organization work can become a form of procrastination. You can spend the whole medication window tweaking the system instead of doing the actual work the system is supposed to support.
That's a real risk. The perfect checklist that never gets used is worse than a mediocre checklist that actually guides behavior.
My advice: give yourself a time box for system-building. Say, two hours total. Design the checklists, print them, tape them up, done. Don't iterate. Don't optimize. The first version will be wrong in ways you can't predict until you use it. Use it for two weeks, then tweak — but the tweaking happens during a dedicated review session, not as an ongoing distraction.
That's the agile development approach applied to life systems. Ship a minimum viable product, get feedback from reality, iterate. Daniel's a developer, so that framing will probably resonate.
Let's pull this together. If we were going to hand Daniel a user manual, what would it contain? Page one: the system overview — a one-paragraph explanation of how the whole thing works, so that when it breaks and you need to rebuild, you know the principles. Pages two through seven: the six domain checklists, each with three to seven items, each with a note at the top about recovery. Page eight: the weekly reset checklist — the one that ties all the other domains together. Page nine: the master reference — go-to meals, important contacts, tax deadlines, moving checklist.
The format: pages two through eight are printed on separate sheets, each posted in its relevant location. Page nine is a plain text file, synced to both parents' phones and computers.
I'd add one more thing: a daily anchor. One thing that happens at the same time every day, no matter what, that serves as the heartbeat of the whole system. For Daniel and Hannah, it might be the evening adult reset — that fifteen-minute window after Ezra goes down where they run through the evening checklist together.
The anchor keeps the rhythm going even when individual pieces fail. If the morning was chaos and the afternoon was a disaster, the evening reset still happens. It's the reset button.
Doing it together matters. If one person is carrying the mental load of the checklists, it's not sustainable. The system has to be shared. Both parents know where the checklists are, both parents can run through them, both parents can update the master reference. The "source of truth" only works if it's actually the truth for everyone.
Alright, I want to address something deeper Daniel said. He finds complicated things easy but struggles with the daily things it takes to be a functional human. That's a really common ADHD experience, and it's not a character flaw. It's a neurological reality.
ADHD brains are interest-based, not importance-based. If something is novel, challenging, urgent, or personally interesting, it engages the dopamine system and executive function kicks in. Complicated problems are often novel and challenging, so the ADHD brain locks in. But daily maintenance tasks — groceries, laundry, brushing teeth — are none of those things. They're not novel, not challenging, not urgent until they become a crisis. So the brain doesn't engage. It's not that Daniel doesn't care about eating dinner, it's that the task of ensuring dinner happens doesn't generate the neurochemical conditions for action.
The system has to compensate. It has to make the uninteresting tasks automatic — or at least remove the need for interest by reducing the cognitive load so much that the task doesn't require engagement. You don't need to be interested in checking the fridge checklist, you just need to walk past the fridge and see it.
Reducing friction also helps. If the groceries are delivered instead of requiring a trip to the store, that's less friction. If the go-to meals use ingredients you always have, that's less friction. If the laundry basket is right where you take off your clothes, that's less friction. Every bit of friction you remove is one less thing your brain has to overcome. Daniel mentioned home delivery specifically — if it's in the budget, grocery delivery is one of the highest-return investments a new parent with ADHD can make.
In Israel, the grocery delivery infrastructure is actually pretty good. Shufersal, Rami Levy, they all do it. It's not expensive.
There's another dimension here: the emotional side. Daniel described the cheese-on-bread moment and his read was "this was preventable." That's an analytical read, which is useful for system design. But there's also an emotional read: "I failed at a basic adult task, and that feels bad." For someone with ADHD, those moments accumulate into a narrative of "I can't do simple things, what's wrong with me.
That narrative is self-reinforcing. The worse you feel about your ability to handle daily life, the more you avoid thinking about daily life, the more things fall apart, the worse you feel.
The system also has to function as a kind of emotional prosthetic. It has to externalize the competence so that you don't have to feel competent to get things done. On a bad day, when you feel like you can't do anything right, the checklist still works. You don't have to believe in yourself, you just have to follow the list.
That's almost a philosophical stance. The system doesn't depend on your emotional state. It's there whether you're feeling great or feeling terrible. And that reliability, over time, actually changes the emotional narrative. When you have a stretch of weeks where dinner happens and the apartment is basically functional and Ezra gets to daycare on time, you start to build evidence that you can do this. The system creates the conditions for competence, and the experience of competence changes how you see yourself.
Let me address one more thing. Daniel mentioned he's tried Google Calendar and Todoist and isn't convinced they make things easier. I want to give a more nuanced take on where digital tools do and don't help.
The problem with Google Calendar and Todoist isn't that they're digital, it's that they're unstructured. They give you a blank canvas and say "organize your life." For someone with ADHD, that's paralyzing. But a shared family calendar with recurring events for the fixed rhythms — daycare drop-off, weekly grocery run, business admin block — that's genuinely useful. It provides the external trigger for things that don't have a natural environmental trigger. And shared is the key word. Both parents can see it, both parents get notifications.
For task management, the sweet spot is something much simpler than Todoist. A shared reminders app with a very small number of lists. Not "projects" and "contexts" and "next actions." Just "this week," "this month," and "someday." The "this week" list gets reviewed during the weekly reset and should never have more than about seven items. If you can't fit the week's priorities into seven items, you're not prioritizing, you're cataloging.
The point is, digital tools have a role, but they need to be as simple and structured as the paper checklists. The tool should do the organizing for you, not ask you to do the organizing inside the tool.
Alright, let's do the temperature check: if Daniel implements something like this, what's the likely failure mode?
I think the most likely failure mode is that it works for two weeks and then the weekly reset gets skipped one week, and then the checklists get stale, and then the whole thing quietly dies. The weekly reset is the linchpin. If that goes, everything else slowly drifts out of alignment.
How do you protect the weekly reset? It needs to be sacred. Same time every week, no exceptions unless someone's bleeding. And it needs to be short — twenty minutes max. If it's an hour-long ordeal, it won't survive.
I'd also say pair it with something pleasant. Do it with coffee on a Saturday morning. Make it a ritual, not a chore. The checklists get reviewed, the meal plan gets sketched out, the grocery order goes in, and then you've earned your weekend.
The other failure mode is checklist creep. Over time, you add items. The three-to-seven-item checklist becomes a twenty-item checklist, and suddenly it's overwhelming again. You need a hard rule: if you add something, you remove something. The checklist has a fixed capacity.
That forces prioritization. If you want to add "clean the bathroom," what are you willing to remove? If the answer is "nothing," then maybe "clean the bathroom" lives in the master reference under "occasional tasks.
One more failure mode: the system works for one parent but not the other. The checklists become a source of friction instead of a shared tool. The fix is to design the system together, review it together, and be willing to adapt it to both people's needs. If Hannah hates paper checklists and wants digital, maybe the kitchen checklist is a shared note on her phone. The principle matters more than the format.
The system has to serve both of them, not just the person who's more into systems.
Let's summarize the user manual. One: six domains, each with a short checklist of non-negotiable minimums. Two: checklists are posted in the physical location where the actions happen. Three: a weekly reset that reviews everything and restocks the system. Four: a plain text master reference for long-term information. Five: a shared digital calendar for time-based triggers. Six: a recovery protocol that says "start here, no shame." Seven: protect the weekly reset like it's a medical appointment. Eight: fixed capacity — no adding without subtracting.
That's a solid manual. And I think it answers the question Daniel was really asking, which isn't "how do I get more organized" but "how do I stop the daily stuff from consuming all my mental bandwidth so I can be present for my family and my work.
The goal isn't to have a perfect system. The goal is to have a system that's good enough that you don't have to think about it. The mental bandwidth you free up is the real prize.
Now: Hilbert's daily fun fact.
Hilbert: In the Byzantine court, the emperor's silentiaries were officials whose sole job was to enforce absolute silence during imperial ceremonies. Any breach of the prescribed silence was considered not just a breach of etiquette but a potential political threat, because noise could mask the approach of an assassin. By the 1970s, a team of archaeologists excavating a Byzantine site in Patagonia — yes, Patagonia — found what appeared to be a ceremonial chamber with acoustic properties so precise that a whisper at one end could be heard clearly at the other, while footsteps in the center were completely deadened. The working theory is that the room was designed to make any unauthorized movement acoustically invisible to the emperor while amplifying the slightest conspiratorial whisper, turning silence itself into a surveillance system.
I have so many questions about Byzantines in Patagonia, and I suspect I'll never get answers to any of them.
That was deeply unsettling.
For anyone listening who's in a similar situation — new parent, ADHD brain, life getting more complex than your old systems can handle — the core question is: what's the smallest thing you can put in place this week that would prevent one of your recurring failures? A checklist on the fridge. A recurring grocery delivery. A shared calendar. The system doesn't need to be perfect. It just needs to be slightly better than what you're doing now.
If you build it during the window when you have focus, the daily stuff gets easier even when the focus isn't there. That's the whole game.
This has been My Weird Prompts. Thanks to our producer, Hilbert Flumingtop. You can find us at myweirdprompts.
If you got something useful out of this, leave us a review wherever you listen. It helps other people find the show.
We'll be back soon.
