Poko Resources
Adhd And Executive Function
ADHD can make ordinary work harder to run because attention, working memory, inhibition, timing, switching and follow-through all carry load. Executive function support works best when it reduces that load in the actual conditions where the person has to act.
Executive function is not one thing
People often talk about executive function as if it is a single skill. In real life it is a set of connected operations: holding a goal in mind, choosing where attention goes, inhibiting the wrong move, starting, switching, remembering the next step, tracking time, regulating effort and finishing. A person can be strong in one part and still get stuck in another. The problem may not be motivation. It may be that the task is asking for too many cognitive operations at once.
Why capable people still stall
A capable person can understand the task, care about the outcome and still be unable to move cleanly. ADHD is associated with differences in attention regulation, impulsivity and activity level, but the real-world impact often shows up as inconsistent performance: one day the system runs, another day the same task feels unreachable. The useful question is what the task is asking the brain to hold, decide, resist, start, sequence and recover from.
What support looks like now
Current good practice is moving away from moral language and toward design: clearer next actions, reduced switching cost, visible priorities, external memory, realistic pacing, fewer open loops and less dependence on perfect internal state. This does not mean lowering expectations. It means building conditions that make the intended action easier to find and easier to repeat.
Where Poko starts
Poko starts with function. Instead of asking people to prove they are struggling enough, it asks what is hard to run right now. Is the problem choosing, starting, shifting, finishing, planning, remembering, regulating pressure or returning after interruption? That keeps the support practical, whether the person has a diagnosis, is exploring one, or simply knows the week is not working.
What to watch this week
Notice where the break actually happens. A task that looks like procrastination may be a decision-load problem. A finishing problem may be a standards or transition problem. A planning problem may be too many hidden dependencies. The more precise the break point becomes, the less support has to rely on force.
How to use this
- Choose one task that keeps sticking and name the exact break point: choose, start, switch, finish or return.
- Reduce one cognitive operation before you begin: decide the first move, remove one option or write the handoff point.
- Treat inconsistency as information about load and conditions, not as proof that you do not care.