Your brain has jobs.
Sometimes it does those jobs too hard, too fast, or without giving you much warning. If you understand what it is doing, you get more say over what happens next. This is not a program about fixing your thinking. It is a manual for the system you already run.
Six modules, usually one a week. Each one starts with a question you have probably asked yourself, gives you the science in plain words, shows what it looks like in real life, and then hands you something to try. Every module ends the same way: what did your brain learn?
Nothing here needs you to feel calm or confident first. The order is deliberate. You learn how your system runs before anyone asks you to run it differently, and you get your body settled before you are asked to make decisions. Your responses make sense. Then we work out what you want to do with them.
We are not going to convince your brain with positive quotes. We are going to collect evidence.
Make it yours
Your answers stay in this browser on this device. They are not sent anywhere. You can print your manual at the end or clear everything from the practitioner panel.
Rate where you are right now, 0 to 10. There are no right answers and nobody is grading you. You will rate the same six statements at the end so you can see what shifted.
Right now
0 means not at all. 10 means completely.
Why can you spend three hours on something you care about, but ten minutes starting something pointless feels impossible?
Because your brain is not a single machine that is either working or broken. It is a system with hardware, processing load, notifications, a battery, and background apps. Once you know how yours runs, a lot of things stop looking like personal failure and start looking like settings.
Every waking second your brain is doing four jobs at once: prioritising what deserves attention, predicting what is about to happen, allocating processing power, and deciding whether something is worth acting on. None of that is optional and most of it happens before you are aware of it.
Brains differ in how much each of those jobs costs. For some people, attention, planning, understanding spoken instructions, switching between tasks, coping with uncertainty, and noticing what is going on inside their own body all use more processing power than they seem to from the outside. A situation can look easy to everyone else while costing you a lot more to run. That is not a character flaw. It is a spec sheet.
The gaming version is accurate: hardware (what you were built with), processing load (how much is running), lag (when demand outruns capacity), notifications (interruptions you did not choose), battery (energy that runs down and needs charging), background apps (worries and tasks quietly eating power), and performance mode (the conditions where you run at your best).
Needing structure does not mean being incapable. It means knowing your own system requirements.
- Starting is harder than doingStarting means planning, choosing, and switching all at once, which is the most expensive part of any task. Once you are in, most of that cost has already been paid.
- Vague instructions are infuriating"Just sort it out" hands your brain a search with no keywords. It has to build the whole plan before it can take one step.
- Being rushed makes thinking worsePressure pulls processing power toward the threat of the deadline and away from the actual problem. You are not slow. You are being throttled.
- Knowing the point changes everythingYour brain allocates energy to things it believes matter. "Why am I doing this?" is a legitimate system question, not an attitude.
- Some environments cost moreNoise, bright light, new places, and people watching all run in the background. The task did not get harder. The load did.
Build your system map
Tap a chip, then tap the zone it belongs in. Add your own. There are no wrong answers, only accurate ones.
Fast at
Uses more processing power
Drains the battery
Helps it run better
What does 90%, 50%, and 10% look like?
Slide to see the state. Then describe what each one actually looks like for you, so the people around you can recognise it too.
This is module one of six.
The full program goes on to the alarm system, resets, checking the story, testing it, and building proof, and it is tailored to the cohort it runs with. Programs also exist for adolescent boys and for parents and carers, and we build programs for schools and organisations on request.
Why does your body react before you have even decided anything is wrong?
Because the part of your brain that predicts danger does not wait for permission. Anxiety is information, not an instruction. The alarm can be real even when the prediction behind it turns out to be wrong.
Your brain runs a protection system whose whole job is to guess what might go wrong and get your body ready before you have had time to think. Uncertainty, sensory overload, a situation that matters to you, or anything that once went badly can trip it. It fires fast because a slow alarm is useless. The cost of that speed is accuracy.
The sequence is always the same. Tap each step to see it play out in a situation you might actually face.
Something can actually hurt you. The alarm is doing its job. Act on it.
Something feels bad but cannot hurt you. The alarm is a prediction. You get to check it.
The feeling is real. The danger is a guess. Those are two different things, and telling them apart is a skill.
Most people are told to "name the emotion". For a lot of brains that is the hardest possible starting point, because the body signal arrives long before the word does, and bodily cues do not feel the same for everyone. So we start with signals you can actually observe: heart, stomach, muscles, temperature, thoughts speeding up, going quiet, getting snappy, wanting to leave, avoiding, or arguing. You do not have to name a feeling before you are ready. You just have to notice the dashboard.
Build your alarm dashboard
For each signal you get, tap when it usually shows up: early (first warning), mid (it's building), or late (already loud). Leave the ones you don't get.
Why does "just calm down and think about it" never work when you actually need it to?
Because thinking is the first thing to go offline when your system is overloaded. Body first. Decisions second. You change the conditions your brain is running in, and then you solve the problem.
When you are highly activated, exhausted, or overloaded, the parts of your brain that handle reasoning, language, holding back an impulse, and flexible problem solving get more expensive to run, right when everyone around you is asking you to use them. Long explanations, reassurance, and "be logical" are least useful exactly when adults are most likely to reach for them. That is not a coincidence. It is why the order of this manual matters.
A reset is not about feeling great. It is about moving from not available for thinking to available enough to choose. That is a much smaller distance, and it is measurable.
Sleep belongs here too, not as a rule about bedtime, but as maintenance. Sleep is when your brain clears the day, files memories, and recharges the battery you mapped in Module 1. Poor sleep and anxiety feed each other, and improving sleep tends to improve how the alarm behaves. Nobody is going to lecture you. You just get to know what the maintenance window does.
- Fewer wordsWhen you are at 10%, language costs the most. The people who help best say less, not more.
- Pause the demandStopping the ask for five minutes is not giving in. It is loading the conditions the task actually needs.
- Familiar over newA task you can do on autopilot brings the system back faster than a new one that needs planning.
- Body before brainMovement, temperature, water, food, and predictable input change the state. Arguing with the state does not.
Build your reset menu
Nobody gets told what works. You experiment. Tap what you are willing to try, then come back after you have used it and rate it honestly.
Maintenance window
Three levers that actually move sleep. Pick one to try, not all three.
If a thought feels one hundred percent true, does that make it a fact?
No. Your brain is a prediction machine, and the predictions it makes when the alarm is on are extremely convincing. A thought can feel true without being a fact. You do not have to defeat it, delete it, or believe it before you act.
Anxiety and past experience produce very confident forecasts: "I'll stuff it up." "People will think I'm stupid." "There's no point." "I can't do it." "Something bad will happen." They arrive fully formed, in your own voice, with feelings attached. That is what makes them feel like facts.
The problem is not that your brain predicts. Everyone's does. The problem is when a prediction gets treated as an instruction, and the instruction is usually "avoid". Avoiding feels like relief, but it means your brain never receives the evidence that would let it update the forecast. So the same prediction fires next time, just as loud.
You will not find worksheets here about "challenging irrational thoughts". Your thoughts are not irrational. They are predictions made from old data. Instead you get a lab: a thought goes in, it gets separated into what is known and what is guessed, and it comes out as something you can test. You can carry a thought with you and still do the thing. That is the skill.
We aren't going to convince your brain with positive quotes. We are going to collect evidence.
- The prediction arrives firstBy the time you notice "I can't", your brain has already decided. Noticing that it is a prediction is the first move, not arguing with it.
- Feeling sure is not the same as being rightConfidence is a feeling your brain adds to a forecast. It is not a measure of accuracy.
- Avoidance deletes the evidenceEvery time you skip the thing, the forecast stays undisputed. The lab exists to get it disputed.
- You can act with the thought still thereYou do not need it gone. You need it moved from the driver's seat to the passenger seat.
The Prediction Lab
Every difficult thought goes through four boxes. Then it goes in your lab log, and if you want, straight into Module 5 as an experiment.
What if confidence is what you get after you do the thing, not before?
Most people wait to feel ready. The evidence says it works the other way around. Confidence usually comes after you do the thing. So this module is where the manual stops being about understanding and starts being about proof.
When something feels uncertain, unfamiliar, or likely to end in failure, avoiding it is a completely reasonable move. The catch is that your brain never gets the new information it needs to update its prediction, so the next time is exactly as hard. Doing the thing, even badly, is how the forecast gets corrected.
Actually testing predictions is one of the strongest supported parts of any anxiety approach, and it works for lots of different brains when it is adapted properly. The modern version is not "stay in the scary thing until you stop feeling scared". It is "make a prediction, run the test, and see what your brain learns". The goal is competence, not compliance. You are not doing this for anyone else.
Mastery experiences, times you did the thing and survived it, appear to be the single biggest contributor to believing you can handle things. Bigger than encouragement. Bigger than being told you are capable. That is why this module carries the most weight.
I can feel unsure and still find out what happens.
- It has to be yoursAn experiment tied to something you actually want beats a therapy task every time. Driving, work, cooking, a call, a question, a new place.
- Smallest safe version first"I don't think I can" becomes "what is the smallest version that would give us real evidence?" Small experiments still count as data.
- Predict before, record afterThe comparison between what you predicted and what happened is the whole point. That gap is where your brain updates.
- Unsure is allowedYou do not need to feel ready. You need a reset menu and a small enough step.
Brave experiments
Set one up before you do it. Come back after and record what actually happened. Your proof bank grows every time.
What do you do when nobody is prompting you?
Understanding a strategy in a session does not automatically make it available at 11pm, in a car park, or on a first shift. This module turns everything you have built into one page you actually own. Not a list of therapy strategies. An operating manual.
Skills do not travel on their own. Getting started, remembering to use something later, planning, and communicating what you need are all separate jobs, and they are often the expensive ones. So the manual has to be short, visible, and built around what matters enough for you to bother.
That last part is not a motivational line. People stick with things far more when the reason is their own, the structure is clear, and the link between the skill and their actual life is spelled out. Nobody sustains a strategy because an adult wants them to. They sustain it because it gets them closer to the licence, the job, the mates, the sleep, or the front door.
Understand → Notice → Reset → Check the story → Test it → Build proof. One model. Every situation.
Most of this is already filled in from what you did in Modules 1 to 5. Edit anything. It is your manual, not ours. The "Use what I built" links pull your own answers back in if you change your mind.
My Brain User Manual
Daniel’s Diaries™Same six statements as the start. Rate where you are now and see what moved.
Now
0 means not at all. 10 means completely.
What shifted
Grey is where you started. Gold is now.
For practitioners
Delivery notes, evidence, and outcome data
This resource is a SETT informed, six module psychoeducation program for young people whose neurodevelopmental profile makes attention, language processing, executive functioning, emotional regulation, initiation, and flexible responding more effortful. It is built to link directly to diagnosed impairment, functional impact, skill acquisition, and community participation, and to be individualised and measured rather than assumed effective on completion. Every module finishes with a real life application tied to independence, relationships, driving, employment, sleep, getting out of the house, or doing something difficult.
Sequencing principle
Physiological and relational safety before behaviour change. Modules 1 to 3 establish a non pathologising system map, the alarm as a prediction system, and body first regulation. Modules 4 and 5 then do the cognitive and behavioural work, with Module 5 (behavioural experiments) carrying the greatest weight. Module 6 converts everything into an owned operating manual and a self chosen mission, because initiation, prospective memory, and generalisation across settings are frequently the impairments that stop a strategy travelling out of the room.
Module rationale
| Module | Functional impact addressed | Evidence base as stated in the program brief |
|---|---|---|
| 1 Know your system | Attention, planning, language processing, switching, uncertainty, and internal state recognition are more effortful; situations that look manageable to others cost substantially more. | Metacognitive understanding rather than diagnostic education, giving the young person language to recognise and communicate needs before dysregulation. |
| 2 The alarm system | Protective responding activates before conscious evaluation under uncertainty, threat, sensory load, or emotional significance. | Emotional awareness and regulation are relevant to youth anxiety; interoception in autistic people is heterogeneous, so bodily cues are never assumed to be standard. |
| 3 Back online | Reasoning, language, inhibition, and flexible problem solving cost more when activated, exhausted, or overloaded. | Safety first premise of SETT; meta analytic evidence that sleep quality relates to adolescent anxiety and that sleep targeted intervention can improve anxiety outcomes. |
| 4 Stories | Convincing negative predictions are treated as instructions and avoidance prevents contradictory learning. | ACT informed language; psychological flexibility associated with anxiety improvement in adolescent trials, with methodological limits and no demonstrated superiority over CBT. Growth mindset deliberately not oversold given small, variable effects. |
| 5 Build proof | Avoidance of unfamiliar, uncertain, or failure sensitive tasks blocks prediction updating. | Exposure based approaches are among the most strongly supported anxiety components, including adapted CBT for autistic young people; inhibitory learning framing; mastery experiences explain more variance in adolescent self efficacy than social support variables. |
| 6 Run your own system | Initiation, prospective memory, planning, communication, and generalisation across settings. | Autonomy support, structure, and meaningful involvement predict adolescent engagement; utility value work shows linking learning to the person's own life increases persistence. |
[INFO NEEDED: full citations for the studies summarised above, from Aimee, before this resource is distributed outside the practice.]
Delivery
One module per week over six weeks is the default, delivered alongside sessions rather than as homework. Keep language short, literal, and low abstract. Let the young person drive the interactive elements; the practitioner's job is to make the real life translation land, not to complete the fields. Effects of adapted CBT for anxiety in autistic young people vary substantially between individuals and informants, so treat the check in data below as one signal among several, and never assume completion equals improvement.
Outcome data on this device
| Statement | Start | End | Change |
|---|
Privacy and reset
All entries are stored only in this browser on this device (local storage). Nothing is transmitted. Use a separate browser profile or device per young person, or clear the manual between people. Clearing cannot be undone, so print or copy the summary first.