Notion vs Things for ADHD: Choose by Friction

The decision is about daily friction

At 4:40 p.m., after a scattered day and a few unexpected messages, a task manager earns its place if it makes the next action obvious without requiring a tour through six views. That is the test. Notion and Things can both hold commitments, yet they help at different points in the work cycle.

Notion is built for designing a system around work, while Things is built for moving through a day with fewer negotiations. For many adults with ADHD, capture is manageable; returning to a crowded system and deciding what still fits the available energy is where the gears jam.

The better tool is the one that removes friction at the point where the process usually breaks down. Sometimes that means connecting a task to a project brief, a meeting decision, and a client record. Sometimes it means seeing one believable Today list.

Notion works when tasks need their context

Notion earns its complexity when a task makes more sense beside the information that explains it, such as project requirements, research, household records, content plans, or shared operating notes. A plain task list can feel flimsy when the work has many moving parts.

Its databases can support filtered views, templates, connected project pages, relations, formulas, status properties, and dashboards that show different slices of the same work. That flexibility is useful. It also creates many choices before the system feels finished.

A blank database is helpful when the needed structure is already clear, but it can turn into a tiny interior-design project when starting the actual task feels harder than rearranging properties. That trap is common. The tool gives plenty of room to build around avoidance.

Where Notion is a good fit

• Projects with supporting material: Keep a task beside requirements, decisions, notes, and deliverables.
• Shared workflows: Give a team one source of truth with visible owners and statuses.
• Custom processes: Create views for a launch, a client pipeline, a semester, or recurring home administration.
• Repeatable work: Use templates when each instance needs the same supporting information and steps.

Notion can create recurring database entries with repeating templates, which suits weekly reviews, recurring meeting notes, and other processes with a consistent page structure. Notion’s guide to repeating database templates explains how scheduled templates create new entries.

That automation handles creation. It cannot judge urgency. A template may add “weekly planning” every Monday, yet the task still needs a view and a routine that put it in sight at a useful moment.

The best Notion setup is usually smaller than the one imagined on a highly focused Sunday. One task database, one project relation, and a few filtered views can carry a surprising amount of work without becoming a second job.

Things works when the day needs less negotiation

Things uses a more opinionated personal workflow with an Inbox, Areas, projects, headings, tags, and a clear daily view. The structure is deep enough for substantial projects. It does not ask for a database schema before “send invoice” can be captured.

Today is the center of gravity in Things, and it can show calendar events alongside planned tasks while separating later items into This Evening. That boundary helps when the problem is not finding work but recognizing that today has limits.

Things also supports repeating to-dos and projects on a fixed schedule or after completion, which matters for routines that depend on the last completion rather than an arbitrary date. Things’ repeating-task guide covers both methods.

After-completion repeats fit work like replacing a water filter, submitting expenses, doing laundry, or watering plants. The schedule follows the work. You still decide whether the newly created item deserves space in Today.

The platform limit is decisive for some people: Things is available on Mac, iPhone, iPad, Apple Watch, and Vision Pro, but not on Android, Windows, or the web. It is also not designed as a team task-management tool.

Notion vs. Things at a glance

Feature count is the wrong contest because Notion will almost always win it. The practical comparison is which kind of friction is easier to live with.

Test the tool on a depleted day

A productivity system should be judged after a fragmented workday, a missed meal, and three new messages, not during a motivated planning session. Good-day systems are cheap. The useful system still works when attention is thin.

Research on cognitive offloading supports part of this instinct. In a laboratory tracking task, participants who could hand some targets to a computer partner offloaded part of the work and improved their own accuracy, as reported in this PLOS One study. It is not a direct test of task apps. Still, reducing one decision can free attention for the work itself.

Notion asks for trust in views and rules created earlier, which can be excellent when those rules fit the work. Things narrows the choice. It asks for a review of a constrained plan and a decision about what belongs today.

Choose Notion if structure itself settles the mind, dashboards get reopened, and projects become easier when their details are connected. Choose Things if extra options cause hesitation, most work is personal, and a clean daily plan makes starting less sticky.

Choose Notion for complex, connected work

Pick Notion when tasks need to interact with documents, databases, people, or repeatable processes, and when maintaining a few conventions feels worthwhile. Keep those conventions few. A system with one task database and two or three useful views usually lasts longer than a sprawling productivity headquarters.

Set a maintenance limit before building. Spend no more than 1 hour on the first setup, then use it for 14 days before changing anything substantial. That rule keeps a rough Tuesday from triggering a full rebuild.

Choose Things for personal daily execution

Pick Things when the main need is getting commitments out of working memory, sorting them into life Areas and projects, then seeing a credible plan for the day. Its design is a strong fit for someone who wants order without becoming the administrator of a personal database.

Keep Today intentionally small. A 17-item Today list is a backlog wearing a different outfit. Move the rest into projects, Upcoming, or Someday so the daily view can remain a decision tool.

Consider recommendation-first planning when choosing is the bottleneck

A backlog can contain work tasks, errands, appointments, flexible routines, and personal goals, while the recurring problem is repeatedly deciding what fits the current time and energy. In that case, a recommendation-first tool such as OwnTime can surface next-task suggestions based on timing, importance, effort, and context.

Recommendation at the moment of choice is better automation than another weekly dashboard. It addresses the handoff between intention and action. That is often where executive function needs support most.

Using Notion and Things together

Using both can work well when each app has one clear job. Keep project documents, shared work, and reference material in Notion, then use Things for personal next actions and daily commitments.

Avoid copying every task into both places. Two sources of truth double the maintenance. That is where otherwise sensible systems often quietly fall apart.

Recurring tasks with flexible timing

Things has a practical advantage when a task should repeat after completion, which suits routines that do not belong on an exact calendar date. Notion is the better choice when every recurring item needs a full page template, supporting notes, or a standardized workflow.

Do not mistake recurrence for urgency. A task can return every week without deserving an interruption at 2:15 p.m. on a packed day.

Stop rebuilding the system

Make one rule firm: a setup change must solve a problem that appeared at least twice in normal use. One unusually chaotic Tuesday is data. It is not enough evidence to redesign everything.

Boring defaults win here. A system that survives an ordinary messy week is preferable to an elegant setup that depends on unusually focused conditions. Run one tool for 14 days, review what failed, and change only the part that failed twice.