The reason your Notion workspace dies in six weeks isn't a discipline problem. It's a data-model problem.
Your productivity system is fighting your brain — and no amount of trying harder will fix a system designed for a different neurotype.
The Pattern
You know the pattern. You discover a new tool — Notion, Obsidian, Logseq, Tana, Capacities. You spend a weekend building the perfect workspace. It works for two weeks. Then you stop opening it. Six weeks later, it's a graveyard. You feel ashamed. You conclude the problem is you.
It's not you. The problem is structural.
The Data-Model Mismatch
Most productivity tools assume a neurotypical executive function system. They assume:
- You can reliably initiate tasks without external trigger
- You can maintain priority hierarchies without active maintenance
- You can retrieve information by navigating a hierarchical structure
- You can sustain attention on a single task until completion
- You can switch contexts without losing the previous context entirely
If your brain does these things reliably, any of these tools will work. If your brain doesn't — and ADHD, autistic, and many other neurodivergent brains don't — the tool is fighting your cognitive architecture. No amount of discipline overcomes a data-model mismatch.
What Actually Works
The principle is simple: design the conditions, not the effort.
A system that works for a neurodivergent brain has different properties:
1. Low-friction capture. The system must accept input with near-zero activation energy. If you have to navigate to a page, click a button, and choose a database, you won't capture — and what isn't captured doesn't exist.
2. Surface, don't search. Neurodivergent brains struggle with hierarchical retrieval (where did I put that?). They excel at associative recognition (oh, THAT'S what I was thinking about). The system should surface related items, not require you to remember where you filed them.
3. Tolerate entropy. The system must work when it's messy. If the system breaks when you don't maintain it, you'll stop using it when life gets hard — which is exactly when you need it most.
4. Match your retrieval, not your filing. How does your brain actually retrieve information? Not "by category" — by association, by context, by feeling-state. The system's organization should mirror your brain's retrieval, not some idealized taxonomy.
5. Reduce masking load. If using the system requires you to perform neurotypical cognition, it's adding to the masking burden. The system should feel like relief, not performance.
The Attractor-State Frame
Here's the reframing that changes everything: you don't achieve consistency by trying harder. You redesign the conditions so consistency becomes the path of least resistance.
This is the attractor-state frame from dynamical systems theory. An attractor is a state the system tends toward. Your current system has an attractor toward abandonment — the conditions make "stop using it" the easiest move. You can't fight the attractor with willpower. You have to change the conditions so the attractor shifts toward continued use.
This means: if your system requires you to open it, you won't. If your system comes to you — via notifications, widgets, ambient displays — you will. If your system requires maintenance, it will decay. If your system self-maintains — via auto-categorization, smart surfacing, frictionless capture — it won't.
The Diagnostic Question
Before you adopt any productivity system, ask one question: does this system match how my brain actually retrieves information, or does it require my brain to retrieve information like a neurotypical brain?
If the answer is the latter, the system will die. Not because you're broken. Because the system is fighting your brain.
The goal isn't to fix your brain. The goal is to build systems that work with your brain's actual architecture — not the architecture productivity gurus assumed you had.
The LifeOS framework is designed around these principles. Take the LifeOS Audit assessment to diagnose which layer of your current system is leaking — and what to redesign first.
Share
Comments
Sign in to join the conversation.