Practice 3 of 6

Executive Function Notes

Where do I get stuck? Transitions, initiation, decision making, and processing lag.

Where do I get stuck, and why?

In short: Executive dysfunction is not laziness. It is a failure of the ignition system. The signal from intention to action does not reliably transmit.

Why This Matters

Executive function is the set of cognitive processes that allow me to plan, initiate, sustain, and switch between tasks. For the Level 1 ASD mind, these processes do not operate smoothly or reliably. I can know exactly what needs to be done, want to do it, and still remain motionless. This is not laziness. It is not a character defect. It is autistic inertia, a well documented difficulty with task initiation and state transitions.

Standard advice assumes an intact executive engine: "Just start." "Break it down." "Use a timer." These strategies assume that the barrier is cognitive (not knowing how) or motivational (not wanting to). For me, the barrier is often purely executive: the signal from intention to action does not reliably transmit. Understanding where my executive function breaks down, and under what conditions, is essential. Without this map, I will continue to blame myself for failures that are neurological, not moral.

The Friction Points

Task Initiation

The hardest part of any task is starting it. I can sit for hours knowing I need to begin something, watching the time disappear, and still not move. External momentum (a person expecting me), reducing the first step to a pure physical action, and body‑first protocols help.

Transitions

Moving from one activity or state to another is disproportionately costly. Leaving the house requires a full mental gear shift. Rituals that mark transitions, buffer time between activities, and accepting that transitions will always cost something are necessary.

Decision Making

Decisions, especially open-ended ones, drain executive function rapidly. Reducing decisions by creating defaults, making decisions in advance, and using structured decision frameworks helps.

Processing Lag

There is a 48 to 72 hour delay between input and full integration for complex information. Explicitly request time to process: "I need to think about this; I'll get back to you in a few days."

The Protocol

1

Map my friction points

For one week, keep a simple log. When I get stuck, note: what I was trying to do, which friction point was active, and what finally got me unstuck. Look for patterns.

2

Build an external momentum system

Identify at least one reliable external ignition source: a scheduled call, a commitment to another person, a public deadline. Use these intentionally to break inertia on important tasks.

3

Create transition rituals

Design a short, repeatable sequence that signals a mode shift. Example: before deep work – make tea, put on headphones, clear desk. The ritual tells the brain: "We are changing states now."

4

Implement the 72‑hour rule

When faced with a complex decision or an emotionally charged communication, the default response is: "I need to process this. I will get back to you in a few days." This respects my actual processing timeline.

The Deeper Layer

Executive dysfunction is often invisible to others. They see someone who is smart, capable, and seemingly unmotivated. I have internalized this judgment for years, believing I was lazy or undisciplined. Releasing that narrative is part of this practice.

The goal is not to "fix" my executive function. That is not realistic. The goal is to design a life that works with my executive profile: fewer transitions, more external structure, more pre‑made decisions, and explicit permission to take the time I need to process. This is accommodation, not weakness. It is building the ramp for a mind that does not do stairs.

Reflection

Which friction point (initiation, transitions, decisions, processing lag) costs me the most energy on a typical day?

What external momentum sources have reliably worked for me in the past? How can I schedule them more intentionally?

What transition ritual can I implement this week for the state shift I find hardest (e.g., starting work, stopping work, leaving home)?

What is one decision I can eliminate entirely by creating a default?