Tag: AI workflow

ADHD attention is interest-based, not importance-based. This is the sentence that explains more about ADHD than almost any other, and it’s the one most frequently misunderstood by people designing productivity systems — including people with ADHD designing their own.

The neurotypical productivity assumption: prioritize by importance, apply effort accordingly, use willpower to bridge the gap when motivation doesn’t match priority. The implicit claim is that attention is a fungible resource that can be directed by conscious choice.

ADHD attention doesn’t work this way. It activates based on interest, novelty, urgency, or challenge — regardless of importance. A highly important but low-interest task gets no attention. A low-importance but high-interest problem gets hyperfocus. The activation is not a choice; it’s a system property. Willpower can coerce attention onto low-interest work for short periods at significant cost, but the cost is real and the duration is limited.

Most productivity systems for ADHD try to solve this by manufacturing interest in important work: gamification, accountability structures, artificial deadlines, visual progress tracking. These help at the margin. They don’t change the underlying system property. The alternative — designing the operation so that the distribution of work matches the distribution of attention — is more structurally sound.

The Two-Lane Task Architecture

The practical implementation: everything that needs to happen gets sorted into two lanes before it’s scheduled or assigned.

The interest lane. Work that activates the ADHD interest system: novel problems, strategic questions, creative content, complex client situations, architecture decisions, anything with genuine uncertainty about the right answer. This work goes to the operator during periods of activated attention. It gets done at high quality when the interest system is engaged and at low quality or not at all when it isn’t — so the design goal is matching this work to the right operator state, not forcing it through on a schedule.

The automation lane. Work that is deterministic, repetitive, and low-interest: routine meta description updates, taxonomy normalization, scheduled content distribution, schema injection across a batch of posts, image processing pipelines. This work goes to automated systems that don’t require activated operator attention. Haiku runs taxonomy fixes at scale. Cloud Run handles scheduled publishing. The work happens regardless of operator interest state because the operator is not in the execution path.

The sorting question for any task: “Is there a real decision being made here, or is this applying a known rule to a known situation?” Real decisions belong in the interest lane — they need judgment. Known rules applied to known situations belong in the automation lane — they need execution, not judgment, and execution is more reliable in automated systems than in a bored human.

What Gets Routed Where

In a multi-site content and AI operation, the routing looks roughly like this:

Interest lane (operator-driven): Content strategy for a new vertical. Client situation requiring judgment about what to prioritize. Novel technical architecture decisions. Long-form article writing that requires genuine creative engagement. Any situation where the right answer isn’t obvious and domain knowledge is the differentiating factor.

Automation lane (system-driven): Batch SEO meta rewrites across a hundred posts. Taxonomy normalization on a site. Scheduled social distribution from a content calendar. Image optimization and upload pipelines. Schema injection on published posts. Monthly performance reports pulled from analytics APIs. Anything that follows a defined process with known inputs and outputs.

The key constraint: don’t put judgment-requiring work in the automation lane. Automation doesn’t have judgment. Automated taxonomy decisions applied to content that needed a human decision about categorization produce wrong categories at scale, which is worse than wrong categories on individual posts because scale multiplies the error. The routing decision requires honest assessment of whether the work needs judgment or just execution.

The Compounding Effect

The interest-based routing architecture compounds in two directions simultaneously. High-interest work done in activated states is done at higher quality — which produces better outputs and more interesting problems to work on, which sustains the activation. Low-interest work handled by automation is done reliably at consistent quality — which reduces the backlog pressure that creates the urgency triggers that pull ADHD attention to the wrong problems at the wrong time.

The system becomes self-reinforcing: high-quality outputs create interesting follow-on problems, which keep the interest lane well-stocked with work that activates attention. Reliable automation reduces the anxiety of unfinished low-interest work, which reduces the cognitive overhead that competes with high-interest work. The operation runs more on genuine interest and less on urgency management — which is a much more sustainable energy source for an ADHD brain over the long term.