Study each topic twice: once as knowledge, once as a decision. For every concept, build a short scenario where a specific person in a specific setting needs something, list the two most tempting options, choose one, and write why the rejected option fails. Then check yourself against a rubric instead of rereading notes.
Core features and diagnosis: keep upstream features separate from downstream effects
Study core features as observable patterns you can match to described behavior, and keep the upstream features separate from downstream effects such as transition difficulty or distress in noisy settings.
Practice describing what differences in social communication and restricted, repetitive patterns of behavior look like across a classroom, a clinic, and a home, because stems may describe behavior and ask you to match it to the right feature rather than name the feature from memory. Build a two-column habit for each feature: definition on the left, and an 'I would think of this when...' trigger on the right. If you can only fill the left column, the item is not finished.
Separate the features themselves from their downstream consequences. Transition difficulty, distress in busy environments, or refusal are effects that can arise from several sources; they are not core features in themselves. When a stem describes one of these effects, the tempting answer names the nearest-sounding feature. The better decision asks which upstream pattern best explains what was observed and in which settings it appears, and your rejection sentence states why the nearest-sounding label does not fit.
- Social communication: consider both the expressive side and the understanding side
- Restricted or repetitive patterns: note the triggers and what the behavior achieves
- Sensory differences: connect them to the environment rather than to 'bad behavior'
- Developmental context: expectations must fit the person's age and individual profile
Evidence-based intervention: tiebreak on goal and setting, not novelty
Choose an intervention by fit: the goal stated in the stem, the mechanism the strategy assumes, and what the setting can sustain. A broader program is not automatically the better answer to a targeted question.
Write one sentence per strategy: 'I would use this when the goal is X and the constraint is Y.' Evidence-based is a claim about the evidence behind a strategy, not about fit; the same strategy can be well supported and still wrong for a stem whose goal is maintenance rather than a new skill, or whose setting cannot sustain the delivery it assumes. When several options are defensible, the tiebreaker is the goal stated in the stem's last sentence.
Scenario: a stem asks how to address one specific behavior and offers both a targeted strategy and a comprehensive program, each defensible on its own. The tempting choice is the program, because it sounds more thorough. The better decision is the targeted strategy, because the stem's last sentence sets the level of the decision: one behavior, one setting. Write the rejection sentence anyway - 'the program answers a different question' - because naming why the rejected option fails is what transfers to new stems.
- State the goal in the learner's terms before comparing options
- Check the mechanism of change each strategy assumes
- Confirm the setting can support the delivery the plan requires
- Prefer the smallest intervention that meets the stated goal
| Stem signals... | Tempting choice | Better choice | Why it matters |
|---|---|---|---|
| Two strategies, both evidence-based | The newer or better-known one | The one that fits the stated goal and setting | Fit, not novelty, breaks the tie |
| The goal is teaching a replacement skill | A strategy that only reduces distress | A strategy with a teaching mechanism | The mechanism must match the goal |
| The stem asks about one behavior | A comprehensive program | The smallest targeted intervention | A program answers a broader question than the stem asks |
| The setting has limited staffing | A plan needing daily specialist delivery | A plan the setting can sustain | Unsustainable plans drift and the data lose meaning |
| Progress stalls | Add intensity immediately | Recheck the goal and the fit first | A stall is information about fit, not only about effort |
Functional behavior assessment: test the function before choosing the strategy
In functional behavior assessment reasoning, what a behavior accomplishes outranks what it looks like; state the function as a sentence about what the person gains before choosing any strategy.
Trace the sequence before naming anything: antecedent, behavior, what followed, and what changed afterward. Then state the likely function as a sentence about what the person gains - attention, escape, access to something, or a sensory experience. Two behaviors that look identical in form can serve different functions for different people, so the appearance of a behavior never selects the intervention on its own.
Scenario: a learner completes a two-step task only when an adult stands nearby. The plausible mistake is calling the proximity attention-maintained and planning more attention. The better decision is to notice that the adult's presence also signals the task is manageable, and to test an escape hypothesis: does task removal or avoidance reliably follow the behavior? Why it matters: an intervention matched to the wrong function can fade a support the learner still needs, and the resulting data will look confusing rather than informative.
- Describe the antecedent in the person's terms, not the adult's
- Note what reliably followed the behavior across observations
- State the function as a sentence about what the person gains
- Test the hypothesis against the next observation before committing
Ethics scenarios: map scope, consent, and documentation before reading the options
Map every ethics scenario onto three checks: whether the action stays within your scope and competence, whether consent and assent are handled, and whether the reasoning is documented and shareable.
Treat those three checks as your default map for any ethics scenario: is this within my scope and competence, is consent - and where relevant the learner's own assent - handled, and is the decision documented well enough that a colleague could reconstruct the reasoning? Practice the mapping before looking at the options, because a defensible answer touches all three checks, while a tempting answer may satisfy only one of them convincingly.
Scenario: a colleague asks for guidance on a presentation that resembles one you have never worked with directly. The plausible mistake is answering from general knowledge, because the question feels adjacent to your expertise. The better decision names the limit and the next step - training, supervision, or referral to someone with relevant experience. Why it matters: a defensible scope answer protects the learner first, and it also models for the colleague that adjacency is not the same as competence.
- Scope: name the limit and the next step (training, supervision, referral)
- Consent: identify the decision-maker and how the learner's assent will be sought
- Documentation: the record should let a colleague reconstruct your reasoning
- Team communication: share the decision early enough for others to respond
Family collaboration: separate a constraint the plan must respect from a preference you can negotiate
Collaboration means keeping one coherent plan while adjusting its delivery to the family's routines; separate what the family cannot change from what they prefer not to change.
A constraint is something the family cannot change: work schedules, another child's needs, access to transport. A preference is something they could change but may not want to. Strategies must survive constraints and can only negotiate preferences. Confusing the two produces plans that sound collaborative but ask for the impossible, and a family living with an impossible plan gradually stops reporting what happens at home.
Scenario: a caregiver says the home routine 'isn't working' and they 'can't keep it up.' The plausible mistake is hearing low motivation and adding reminders or a chart. The better decision is to ask what a typical evening looks like, then separate constraints from preferences: if the caregiver works evenings, the routine moves to a different slot; if a sibling's bedtime is fixed, the routine shortens. Why it matters: a deliverable plan keeps the data meaningful and builds the trust that makes future adjustments possible.
- Ask what a typical day looks like before proposing anything
- Name one constraint the plan must respect out loud
- Offer two delivery options where you can
- Define success at home, not only in your own setting
Systems and advocacy: from one case pattern to a setting-level mechanism, plus your weekly drill
Systems questions reverse the usual direction: start from a setting-level pattern and propose a specific mechanism, including who owns the change and what evidence would show it worked.
Convert a case observation into a setting-level proposal: state the pattern, the smallest change with the widest effect, who owns it, who must agree, and what evidence would show it worked. Answers that name a mechanism - a consistent visual schedule, a staff training, a referral pathway - are usable, because someone can implement and check them. Answers that name only a value or an attitude leave nothing to implement.
Scenario: several learners in the same program show the same difficulty with transitions. The plausible mistake is writing an individual plan for each learner, because each plan feels precise. The better decision is to check for a setting-level cause first - for example, whether transition expectations differ from room to room - and propose one program-wide mechanism. Why it matters: if the environment produces the pattern, five individual plans spend effort where a single change would serve everyone, including learners who have not yet been flagged.
- Name the setting-level pattern instead of assigning individual blame
- Weekly drill: pick one topic, write a four-line scenario, list the two most tempting options, choose one, and write a one-sentence rejection of the other
- Expected observations by week four: rejection sentences name the specific trigger rather than just 'it's wrong'; scenarios take under five minutes to write; you reach the top rubric score on at least three consecutive topics
- Self-check rubric: 1 = you named a concept only; 3 = you chose correctly but could not say why the other option fails; 5 = you named the trigger, the choice, and the rejection reason. Reaching rubric 5 on roughly two thirds of your topics is a learning milestone, not a passing prediction
- Adaptable sequence: cover two topics per week with a scenario and rejection for each; schedule one review day that reuses your oldest topics; keep the final week to rubric-5 checks only, with no new content
- Readiness checks: you can state the trigger for every concept without notes; every missed practice item produced a written rejection sentence; you can retell the FBA and family scenarios from memory and explain why each mistake fails
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.