By Amy Blaschke, Founder of Multiplist
You know the feeling.
You spent a Sunday afternoon building a beautiful Notion workspace. Nested pages, custom databases, color-coded tags. It felt like finally — this is the system that's going to stick.
Six weeks later you haven't opened it. The last entry was a half-finished note you don't remember writing. There are 23 tasks in Trello, all in the "To Do" column, none with due dates, most of them from a project that's already done or dead.
You call it a graveyard. You've called a lot of workspaces graveyards.
And the worst part isn't the wasted Sunday. It's the voice in the back of your head that says maybe I'm just not someone who can stay organized. Maybe other people can maintain these systems. Maybe the problem is me.
It isn't you. And I'm going to explain exactly why — because understanding the real reason these tools fail is the first step to finding one that doesn't.
# Why Notion Fails ND Brains (It's Architectural, Not Personal)
Notion is genuinely powerful. I'm not here to trash it. But it was designed around a specific set of cognitive assumptions — and if your brain doesn't match those assumptions, you're not failing at Notion. You're failing at being a different kind of person.
Here's what Notion requires to work:
Sustained executive function to set it up. Every Notion workspace begins with a blank page and infinite possibility. For a neurotypical brain with strong executive function, that's exciting. For an ADHD or autistic brain, it's paralyzing. Setup requires deciding what categories matter, how to structure them, what templates to use, what to name things. All before you've done a single unit of actual work. Executive function is exactly the resource most ND brains have the least of — and Notion spends it before you've started.
Consistency to maintain it. Even a perfectly designed Notion setup requires regular maintenance. Pages need to be updated. Tags need to be applied. Things need to be filed in the right places. This requires doing the same administrative actions repeatedly, on the same schedule, with the same level of care — regardless of whether today is a high-capacity day or a low-capacity day. ND capacity is famously variable. The system that works on a Tuesday doesn't get touched on a Friday.
A "highly organized champion." This is the phrase that appears in research on productivity tools again and again. Every tool needs someone to be its steward — to enforce the structure, tidy the loose ends, and coax other users into compliance. That person is exhausting to be. For solo workers, it means being your own steward, which is just more executive function tax.
Tolerance for notifications becoming guilt. When you stop maintaining the system, it doesn't just sit quietly. There are overdue reminders. Abandoned pages. Empty databases. Every time you open it, the visual evidence of your inconsistency is right there. Overdue notifications trigger shame. Shame makes you avoid the tool. Avoiding the tool creates more overdue items. This is the "disability multiplier effect" — the system designed to help becomes the source of additional burden.
None of this is a character flaw. It's a mismatch between tool design and brain design.
# Why Trello Fails Too
Trello is simpler than Notion, which makes it more approachable. The Kanban board is intuitive. Cards move from left to right. It feels like progress.
Until it doesn't.
The Trello graveyard is different from the Notion graveyard, but just as familiar. Cards pile up in "To Do." Nothing ever reaches "Done." The board becomes a source of low-grade dread rather than clarity.
The core problem: tasks without context are meaningless after 48 hours.
A card that says "write proposal" made perfect sense when you created it. Three weeks later, it's a mystery. What proposal? For who? What were the constraints? What was I thinking when I wrote this? The task is disconnected from the reasoning behind it — and without that reasoning, the card is just noise.
Trello also has no memory. No intelligence. No connection between cards and the actual thinking you've done. It's a list with columns. It doesn't know your priorities have shifted, that the client changed their mind, or that the "write proposal" card is actually blocked by a conversation you had on Tuesday that you never captured anywhere.
The tool and your actual work are two separate universes. You have to manually keep them synchronized. For ND brains, manual synchronization is the first thing to fail.
# What You Actually Need: Both, Wired Together
Here's the thing nobody says out loud: you don't need a better note-taking app. You don't need a better task manager.
You need something that is both — and that does the wiring between them automatically.
I've started describing Multiplist as what you'd get if ChatGPT and Trello had a baby. People immediately get it, which tells me the gap is obvious once you name it. You want a workspace that thinks and moves. That captures meaning and organizes action. That holds your knowledge and holds your work — without requiring you to manually keep both in sync.
But there's a third ingredient that's equally important: it has to tend itself.
The reason every productivity system eventually becomes a graveyard is that they all require the user to be the gardener. You have to water them. You have to weed them. On the days when you have zero executive function to spare, the garden gets neglected — and it doesn't recover on its own.
A system designed for ND brains has to do its own tending. It has to catch what you create without requiring you to file it. It has to extract meaning from your conversations without requiring you to summarize them. It has to organize your work without requiring you to maintain the organization.
# What This Looks Like in Practice
Let me walk through what this actually means, concretely — because I think the abstract promise of "a tool that works differently" is easy to dismiss without seeing the specifics.
Meaning flows from conversation automatically. When you have a productive session with your AI — making decisions, articulating frameworks, generating ideas — those insights don't live only in the chat window. Multiplist extracts the structured meaning from that conversation: the decisions you made, the frameworks you named, the questions you need to revisit, the passages that sounded exactly like you. This extraction happens without you doing anything. No filing. No tagging. No copy-pasting.
Your workspace is spatially organized, not linearly listed. Instead of an infinite list of tasks or an infinite tree of nested pages, Multiplist organizes work into Containers (life domains — a client, a project, a business lane) and Studios (workspaces within those domains). ND brains remember where things are more reliably than what things are called. Spatial organization isn't a design preference — it's neurologically correct for how spatial memory dominates in many ND cognitive profiles.
Aero already knows your thinking. The AI assistant inside Multiplist — Aero — doesn't greet you like a stranger every time you open it. It has access to your Vault: the accumulated seeds from all your previous sessions. When you start a new conversation, Aero already knows what you've been working on, what decisions you've made, what frameworks you've developed. No re-explaining. No re-contextualizing. Just continuing from where you were.
The workspace is "no shame" architecture. Dormant doesn't mean failed. There are no overdue notifications generating guilt. There's no productivity metric telling you you're behind. The system doesn't punish you for having a low-capacity day — it just holds everything exactly as you left it and waits without judgment. When you come back, it's exactly where you were.
Your own IP is searchable like the web. The Archivist — Multiplist's long-term memory layer — indexes everything across all your sources over time. When you want to find something, you don't scroll. You search. In natural language. Across six months of sessions. Like Perplexity, but for your own intellectual history. Every result traces back to exactly where it came from — which conversation, which date, which context.
# The Thing That Actually Changes
The tools in your graveyard have something in common: they required you to do work about your work. Setup work. Maintenance work. Filing work. Tagging work. Synchronization work.
The hidden cost of that meta-work is enormous, especially for ND brains where executive function is the scarcest resource. Every minute spent organizing is a minute not spent creating. Every cognitive load unit spent on maintenance is a unit unavailable for the actual thinking.
The shift Multiplist is designed to create is simple to state and profound in practice: the system catches what you produce, instead of you serving the system.
You have a conversation. The meaning is extracted. You do the work. The work lands somewhere searchable and organized. You come back the next day. The context is still there. You don't start from zero.
Your brain is not broken. The tools were designed for a different brain. And now there are tools designed for yours.
# A Note on Transition
If you're reading this surrounded by your own graveyard — the Notion workspace you haven't opened, the Trello board of forgotten cards, the ChatGPT export you meant to review — I want to say something clearly:
None of that is wasted.
Every conversation in those chat logs contains real thinking. Real decisions. Real frameworks. The work happened. It just didn't get preserved in a form you can use.
One of the things Multiplist does is let you import your existing AI conversation history and extract the meaning from it retroactively. The graveyard becomes a mine. The forgotten conversations become a Vault. The work you thought was lost turns out to have been there all along, waiting for a system that could see it.
The conversation was always that good. The extraction just proves it.
Amy Blaschke is the founder of Multiplist, a meaning operating system that extracts structured knowledge from AI conversations and makes it searchable, composable, and persistent. She's also autistic, which is why she built it.
Related reading: