Autism And Audhd

Fit is not a small detail

A system can look reasonable from the outside and still be expensive to run. Noise, ambiguity, interruption, sudden changes, hidden social rules and unclear expectations can all take cognitive energy before the visible work even begins. For autistic and AuDHD people, the question is often not whether they can do the task. It is whether the conditions around the task leave enough capacity to do it without borrowing from recovery.

Masking changes the cost

Many people learn to appear fine while using a lot of energy to monitor tone, facial expression, timing, sensory discomfort, uncertainty and other people's expectations. That can make support needs harder to see. A person may look composed in the meeting and then lose function afterwards. Good support does not wait until collapse proves the cost was real. It makes the load more visible earlier.

AuDHD can pull in two directions

When autistic and ADHD patterns coexist, needs can conflict. A person may need structure and novelty, predictability and flexibility, focus and movement, quiet and enough stimulation. Simple one-size advice often fails here because it solves one side while making the other side harder to run. The better question is what combination of structure, choice, sensory fit, timing and recovery makes action possible this week.

What helps in practice

Current good practice emphasises reasonable adjustments, clear information, sensory awareness, autonomy, predictable communication and support designed with the person. At Poko, that becomes a function-first lens: what needs to be clearer, quieter, smaller, more explicit, more flexible, more recoverable or less socially expensive?

No label required to start

You do not need to know whether the issue is autism, ADHD, AuDHD, burnout, anxiety, sleep, overload or a mix of all of it before you can make the next week more workable. Labels can matter, especially for clinical care and formal adjustments. But the first useful move can still begin with what is hard to run in real life.

How to use this

• Name one condition that makes function more expensive: noise, ambiguity, switching, masking, social load or recovery loss.
• Make one expectation explicit before the work begins: what done means, who decides, when to ask and what can move.
• Protect one recovery point instead of spending the whole week proving you can push through.