Table of Contents >> Show >> Hide
- What you’ll learn in Part 1
- The big picture: what “behavior reduction” actually means
- D-1: Identify essential components of a written behavior reduction plan
- 1) The target behavior (defined like a scientist, not a poet)
- 2) The hypothesized function (the “why”)
- 3) Replacement behavior(s) to teach and reinforce
- 4) Prevention / antecedent strategies (what to do before behavior happens)
- 5) Consequence strategies (what staff do after behavior happens)
- 6) Data collection + decision rules
- 7) Generalization, maintenance, and caregiver/staff alignment
- D-2: Describe common functions of behavior (and how to spot them)
- D-3: Implement antecedent interventions (MOs, SDs, and other “before” fixes)
- A practical MO vs. SD example (with food, because we’re human)
- Common antecedent strategies you should recognize
- 1) Adjust the environment (less chaos, more success)
- 2) Clarify instructions (your words matter)
- 3) Increase choice and control
- 4) Make reinforcement easier to earn (at first)
- 5) Noncontingent reinforcement (NCR) as a preventative tool
- D-4: Implement differential reinforcement procedures (DRA, DRO, DRI, DRL)
- DRA: Differential Reinforcement of Alternative Behavior
- DRI: Differential Reinforcement of Incompatible Behavior
- DRO: Differential Reinforcement of Other Behavior
- DRL: Differential Reinforcement of Low Rates (for “too much,” not “never”)
- How to implement differential reinforcement without stepping on a rake
- A mini scenario (the kind the exam loves)
- Common mistakes (and how to avoid them)
- A fast study plan + mini practice prompts
- Wrap-up (and what’s coming in Part 2)
- Experiences related to behavior reduction
- SEO tags (JSON)
Behavior reduction is where ABA stops being “interesting theory” and becomes “real life with real stakes.” It’s also a big chunk of what new Registered Behavior Technicians (RBTs) are expected to understand and implement accuratelyunder supervision and according to a written plan.
This is Part 1 of 2, focused on the “foundation layer” of behavior reduction: how behavior plans are built, how functions work, how antecedents set the stage, and how differential reinforcement does most of the heavy lifting. Part 2 will dig deeper into extinction details, predictable side effects (hello, extinction bursts), and crisis/emergency procedures.
Important reality check: RBTs don’t invent behavior reduction plans from scratch. Your job is to implement what your supervisor designs, collect data, and communicate what you observe. If you’re ever unsure, you don’t guessyou ask.
What you’ll learn in Part 1
- The big picture: what “behavior reduction” actually means
- D-1: Components of a written behavior reduction plan
- D-2: Common functions of behavior (and how to spot them)
- D-3: Antecedent interventions (MOs, SDs, and other “before” fixes)
- D-4: Differential reinforcement (your best friend on the exam and in sessions)
- Common mistakes (and how to avoid them)
- A fast study plan + mini practice prompts
- : Study & field experiences (composite, realistic examples)
The big picture: what “behavior reduction” actually means
Behavior reduction is the process of decreasing interfering behaviors (behaviors that are unsafe, limit learning, or reduce quality of life) while increasing replacement behaviors that serve the same function in a safer, more effective way.
If you remember nothing else, remember this:
- We reduce behavior ethically (least restrictive, client dignity intact).
- We reduce behavior functionally (we target the “why,” not just the “what”).
- We reduce behavior by teaching (replacement skills + reinforcement), not by “winning” a standoff.
On the RBT exam, behavior reduction is usually tested through short scenarios: you’ll be asked to identify functions, pick an antecedent strategy, select the right differential reinforcement procedure, or recognize what belongs in a plan.
D-1: Identify essential components of a written behavior reduction plan
A written behavior reduction plan (often embedded within a Behavior Intervention Plan/Support Plan) is basically a “how we handle this” playbook. A good plan is clear enough that two different staff members could follow it and get similar resultswithout freelancing.
1) The target behavior (defined like a scientist, not a poet)
Plans include an operational definitiona description of the behavior that’s observable and measurable. “Noncompliance” is vague. “Within 10 seconds of an instruction, the client does not begin the requested task and/or says ‘no’ while turning away” is measurable.
2) The hypothesized function (the “why”)
Most behavior reduction plans specify the likely function(s): attention, access to tangibles/activities, escape/avoidance, or automatic/sensory reinforcement. When the plan is function-based, the intervention has a much higher chance of working long-term.
3) Replacement behavior(s) to teach and reinforce
Reduction without replacement is like removing a phone’s battery and being shocked when it “doesn’t work.” Plans typically specify what to teach instead, such as functional communication (“Break please,” “Help,” “All done”), tolerance skills (waiting), or coping strategies.
4) Prevention / antecedent strategies (what to do before behavior happens)
Look for strategies that change the setup: visual schedules, choices, demand fading, transition warnings, enriched environment, clearer instructions, and so on. These are often the most humane and efficient interventionsbecause the best tantrum is the one that never starts.
5) Consequence strategies (what staff do after behavior happens)
This section tells you exactly how to respond to both:
- Replacement behavior (reinforce ithow, when, and with what).
- Problem behavior (how to avoid accidentally reinforcing it; what steps to follow; when to prompt alternatives).
6) Data collection + decision rules
Plans include what data to collect (frequency, duration, latency, ABC notes) and what counts as improvement. Many plans also specify treatment integrity checksbecause an intervention can’t be “ineffective” if it wasn’t actually implemented as written.
7) Generalization, maintenance, and caregiver/staff alignment
Strong plans consider: Where should the new skill show up? Who needs training? How will reinforcement be thinned responsibly? (Translation: how do we make this work in real life, not just in Session Room #3?)
D-2: Describe common functions of behavior (and how to spot them)
Behavior doesn’t happen “for no reason.” It happens because it worksit reliably produces something or removes something. In exam questions, function is usually inferred from an ABC-style mini story: what happened right before and right after.
Function #1: Attention
Pattern: Behavior results in social attention (talking, scolding, eye contact, comforting, negotiation).
Example: A client yells; staff rush in and delivers a long lecture about “using words.” (Congratsyou may have reinforced yelling with a TED Talk.)
Function #2: Access to tangibles/activities
Pattern: Behavior results in getting an item or activity.
Example: Client throws iPad; caregiver hands iPad back to calm them down.
Function #3: Escape/avoidance
Pattern: Behavior delays, reduces, or removes demands, tasks, transitions, or unpleasant situations.
Example: When math worksheets come out, problem behavior starts; the worksheet disappears “until later.”
Function #4: Automatic/sensory reinforcement
Pattern: The behavior itself produces reinforcement (sensory feedback), and it can occur even when no one is around.
Example: Repetitive behaviors that persist across settings regardless of social consequences (function assessment is still requireddon’t assume).
Quick test-prep tip: don’t confuse “topography” with “function”
Two clients can have the same topography (e.g., screaming) with different functions. The exam loves this trick. If the consequence differs, the function can differ.
D-3: Implement antecedent interventions (MOs, SDs, and other “before” fixes)
Antecedent interventions are changes made before the target behavior occurs to reduce its likelihood and increase the chance of appropriate behavior. In the RBT task list language, you’ll often see:
- Motivating operations (MOs): variables that change how valuable a reinforcer is and how likely behavior is to occur to get it.
- Discriminative stimuli (SDs): cues that signal reinforcement is available for a specific behavior.
A practical MO vs. SD example (with food, because we’re human)
If you’re hungry, pizza becomes more reinforcing (that’s an MO effect). If you see the neon “OPEN” sign, it signals pizza is available if you walk in and order (that’s SD territory). Hunger changes value; the sign changes the “availability signal.”
Common antecedent strategies you should recognize
1) Adjust the environment (less chaos, more success)
Reduce triggers: remove distracting items during work, provide a quiet workspace, use a visual schedule, or offer a predictable routine. This is “behavior reduction” that doesn’t feel like a power strugglebecause it isn’t.
2) Clarify instructions (your words matter)
Short, specific, and doable instructions reduce escape-motivated behavior. “Be good” is not an instruction. “Hands down, feet on floor” is.
3) Increase choice and control
Choices can reduce problem behavior by decreasing the aversiveness of demands and increasing cooperation (“Do you want to start with reading or math?”). You’re not giving away the whole storeyou’re giving a door handle.
4) Make reinforcement easier to earn (at first)
When new replacement skills are introduced, reinforcement often needs to be immediate and frequent. Then it can be thinned gradually. If you start with “earn a sticker after 45 minutes of perfect behavior,” you are basically training frustration tolerance… for yourself.
5) Noncontingent reinforcement (NCR) as a preventative tool
NCR means providing access to reinforcement on a time-based schedule, independent of behavior, to reduce motivation for problem behavior. It’s often used carefully and paired with teaching appropriate requests so the client still learns functional skills.
D-4: Implement differential reinforcement procedures (DRA, DRO, DRI, DRL)
Differential reinforcement is the “workhorse” of ethical behavior reduction. Instead of trying to “stop” behavior with sheer willpower, you increase better behavior so it can compete and win.
The core idea: reinforce one response class more than anothertypically reinforcing replacement/appropriate behavior while not reinforcing the problem behavior (according to the plan).
DRA: Differential Reinforcement of Alternative Behavior
Reinforce: a specific alternative behavior that serves the same function.
Common use: Functional Communication Training (FCT) is a classic DRAteach a communicative response that produces the same reinforcer the problem behavior used to obtain.
Example: If behavior is escape-maintained, teach “Break please” (or hand a break card), then reinforce that request with a brief break.
DRI: Differential Reinforcement of Incompatible Behavior
Reinforce: a behavior that physically cannot occur at the same time as the problem behavior.
Example: Reinforce “hands in pockets” or “hands on table” to reduce hitting (incompatible topographies).
DRO: Differential Reinforcement of Other Behavior
Reinforce: the absence of the target behavior for a specified interval.
Example: If no screaming occurs for 2 minutes, deliver reinforcement. If screaming occurs, reset or adjust per plan.
Exam tip: DRO reinforces “anything but the target behavior,” so it can accidentally reinforce weird replacement behaviors unless paired with teaching what you do want.
DRL: Differential Reinforcement of Low Rates (for “too much,” not “never”)
Reinforce: lower rates of behavior when eliminating it completely isn’t realistic or necessary.
Example: Reducing excessive calling out in class from 20 times to 5 times per period while teaching hand-raising.
How to implement differential reinforcement without stepping on a rake
- Know the function. Your replacement behavior has to “pay” in the same currency the problem behavior was earning.
- Define behaviors clearly. If staff can’t agree what counts, data becomes interpretive art.
- Reinforce fast at the start. New skills need a strong reinforcement history.
- Prompt the replacement behavior. Don’t wait for magic; teach it.
- Thin reinforcement gradually. Move from continuous to intermittent schedules as appropriate and as directed.
- Track data and integrity. If it’s not improving, you need accurate data to troubleshoot.
A mini scenario (the kind the exam loves)
Scenario: When asked to clean up, a client drops to the floor and screams. Staff remove the demand to calm them.
Likely function: escape/avoidance.
Plan-friendly approach: Antecedent supports (warning + visual “cleanup, then snack”), teach a functional request (“Help” or “One more minute”), reinforce compliance and the request (DRA), and implement demand procedures exactly as written.
Notice what’s missing: arguing, negotiating, and saying “Use your words” seventeen times while continuing the demand with no teaching plan. That’s not behavior analysis. That’s improv.
Common mistakes (and how to avoid them)
1) Reinforcing the problem behavior by accident
If behavior is attention-maintained, even “Stop it” can be a reinforcer. If behavior is escape-maintained, removing the task can reinforce it. Your supervisor’s plan will specify how to avoid this while still maintaining safety and dignity.
2) Picking a replacement behavior that doesn’t match the function
Teaching “Say hi” won’t reduce escape-maintained behavior. Teaching “Break please” might. Match function first, then select the replacement.
3) Using DRO when you really need a taught skill
DRO can be useful, but if the client doesn’t know what to do instead, you may get a creative substitute behavior. Teach the alternative (DRA/DRI) and reinforce it.
4) Reinforcement that’s too delayed, too weak, or too random
“Maybe you’ll get something later” is a fantastic way to teach that replacement behavior is optional. Early on, reinforcement should be strong and timely (then faded responsibly).
5) Treating the plan like “suggestions”
Consistency matters. If four staff members implement four different versions of the plan, the learner gets four different contingenciesand you get four different outcomes. None of them are reliable.
A fast study plan + mini practice prompts
Study plan (30–45 minutes a day for one week)
- Day 1: Memorize plan components (operational definition, function, replacement, antecedent, consequence, data).
- Day 2: Drill functions using ABC mini stories (identify likely reinforcer).
- Day 3: Antecedent strategies: choices, visual schedules, NCR, instruction clarity.
- Day 4: Differential reinforcement types (DRA/DRI/DRO/DRL) + examples.
- Day 5: Mixed practice: choose intervention type given function.
- Day 6: Spot the error: “What is being reinforced here?”
- Day 7: Teach-back: explain DRA vs. DRO to a friend (or a wallwalls are patient).
Quick prompts (answer out loud)
- List 6 components you’d expect in a behavior reduction plan.
- Given this ABC: “Demand placed → screaming → demand removed.” What’s the likely function?
- Pick DRA vs. DRO: You want to increase “ask for help” while decreasing tantrums. Which is best?
- Name two antecedent strategies for transitions.
- Why might reinforcement need to be thinned gradually?
Wrap-up (and what’s coming in Part 2)
In Part 1, you built the foundation for behavior reduction:
- You learned what belongs in a written plan (and why clarity protects everyone).
- You practiced identifying common functions using ABC logic.
- You reviewed antecedent strategies that prevent behavior before it starts.
- You studied differential reinforcement procedures that ethically shift behavior over time.
Next: Part 2 will cover extinction procedures (and predictable side effects), how to troubleshoot when behavior spikes, and what it means to implement crisis/emergency procedures according to protocol.
Experiences related to behavior reduction
Note: The following are realistic, composite “what it often feels like” experiences RBT trainees report while studying and practicing behavior reduction concepts. They’re not about any specific client and are written to highlight learning points.
Experience #1: The “I swear it got worse” week.
A brand-new RBT starts implementing a plan focused on escape-maintained problem behavior during work time. The replacement behavior is a break card, and the plan uses DRA: break card earns a short break; problem behavior does not. The first couple of sessions? Rough. The client tries the old strategy hardermore intense protests, more frequent dropping, bigger emotions. The RBT’s internal monologue is basically: “Did I break ABA?” What helps is supervision that reframes the moment: behavior change often looks messy before it looks better. The key is implementing the plan consistently, prompting the break card early, and reinforcing the request quickly so the client learns, “Oh. This new method works.” A week later, the break card becomes the defaultand the RBT learns a life lesson: when a new skill starts winning, the old one sometimes throws a goodbye party.
Experience #2: The accidental reinforcement trap.
Another trainee is working on attention-maintained calling out. The plan targets a replacement behavior: raising a hand (DRA/DRI combohand-raising is incompatible with blurting if hands are occupied, and it’s also the appropriate alternative). On paper it’s simple. In real life, the trainee catches themselves responding to blurting with full sentences: “Remember, you need to raise your hand, okay buddy, we talked about this…” That response is warm, human, and potentially very reinforcing. Once they notice it, they switch to the plan: minimal attention to blurting, immediate enthusiastic attention to hand-raising, and short prompts (“Hand”) when needed. Within a few days, blurting decreases and hand-raising increases. The funniest part? The trainee realizes they had been giving the best attention to the behavior they wanted least. Classic.
Experience #3: Antecedents are the unsung heroes.
A trainee studies motivating operations and discriminative stimuli and expects it to be abstract, exam-only content. Then they see it in the wild: the client hasn’t eaten much, the session is late, and demands are piling up. Problem behavior increases. The supervisor helps them “zoom out”: if the value of escape is higher because the client is tired or hungry, the MO has shifted. The intervention isn’t to push harderit’s to adjust the setup: schedule a quick snack (if appropriate and approved), start with easy tasks, increase reinforcement frequency briefly, and use clear transition cues. Behavior reduces without a showdown. The trainee’s takeaway becomes a sticky-note mantra: “Before you change consequences, check the setup.”
Experience #4: Learning to love data (even if you don’t want to).
One RBT admits they’d rather alphabetize the clinic’s crayons than take ABC data in real time. But after a month, something clicks: data isn’t paperwork punishmentit’s protection against guessing. When behavior spikes, the RBT can show patterns: “It’s occurring most during transitions,” or “It follows removal of the iPad,” or “It happens after long instructions.” The team can adjust antecedent supports and reinforcement schedules based on evidence, not vibes. And honestly? “Not vibes” is a pretty strong clinical standard.
Experience #5: The confidence shift.
Studying behavior reduction can feel intimidating because it intersects with safety, ethics, and real distress. Over time, most trainees report a confidence shift: they stop thinking, “How do I stop this behavior?” and start thinking, “What skill does this person need, and how do we make that skill pay off?” That mindset is more humane, more effective, andbonusmore likely to show up as the correct answer on the exam.
