These answers draw in part from “Why We Do What We Do” (The Daily BA), and extend it with peer-reviewed research from our library of 27,900+ ABA research articles. Clinical framing, BACB ethics code references, and cross-links below are synthesized by Behaviorist Book Club.
View the original presentation →In Why We Do What We Do, clarify the decision point before the team jumps to a solution. In Why We Do What We Do, begin by naming what the team is trying to protect or improve, who currently controls the decision, and what evidence is trustworthy enough to guide the next move. In Why We Do What We Do, it prevents the common mistake of treating the title of the problem as though it already contains the solution. The source material highlights today I launch a new series: "Follow This!" With 130+ of behavioral and #mentalhealth topics explained to date and no sign of slowing down, I kick this off with a highlight of the Why We Do What We Do podcast with co-founder and host on their psychology focused podcast! In Why We Do What We Do, once that decision point is explicit, the BCBA can assign ownership and document why the plan fits the actual context instead of an imagined best-case scenario.
For Why We Do What We Do, review the best evidence by looking for data that separate competing explanations. In Why We Do What We Do, useful assessment usually combines direct observation or record review with targeted input from the people living closest to the problem. For Why We Do What We Do, the analyst should ask which data would actually disconfirm the first impression and whether the measures being gathered speak directly to the analytic principle, decision point, and applied example the team is trying to connect. For Why We Do What We Do, that may mean implementation data, workflow data, caregiver feasibility information, or evidence that another variable such as medical needs, policy constraints, or training history is influencing the outcome. When Why We Do What We Do is at issue, assessment is chosen this way, the result is a smaller but more defensible decision set that other stakeholders can understand.
Treat Why We Do What We Do as an ethics issue once poor handling can change risk, consent, privacy, or scope. In Why We Do What We Do, the issue stops being merely procedural when poor handling could compromise client welfare, distort consent, create avoidable burden, or place the analyst outside a defined role. In Why We Do What We Do, in that sense, Code 1.01, Code 1.04, Code 2.01 are often relevant because they anchor decisions to effective treatment, clear communication, documentation, and appropriate competence. For Why We Do What We Do, a BCBA should therefore ask whether the current response protects the client and whether the reasoning around the analytic principle, decision point, and applied example the team is trying to connect could be reviewed without embarrassment by another qualified professional. In Why We Do What We Do, if the answer is no, the team is already in ethical territory and needs to slow down.
Within Why We Do What We Do, involve the relevant people before the plan hardens. In Why We Do What We Do, bring stakeholders in early enough to shape the plan rather than merely approve it after the fact. In Why We Do What We Do, that means clarifying what behavior analysts, trainees, researchers, and the clients affected by analytic rigor each know, what they are expected to do, and what limits apply to confidentiality or decision-making authority. In Why We Do What We Do, strong involvement does not mean everyone gets an equal vote on every clinical detail. In Why We Do What We Do, it means the people affected by the analytic principle, decision point, and applied example the team is trying to connect understand the rationale, the burden, and the criteria for success. That level of involvement matters most when Why We Do What We Do crosses home, school, clinic, regulatory, or interdisciplinary boundaries.
Avoidable mistakes in Why We Do What We Do usually start when the team answers the wrong problem too quickly. In Why We Do What We Do, one common error is relying on the most familiar explanation instead of the most functional one. In Why We Do What We Do, another is building a response that only works in training conditions and then blaming the setting when it fails in the wild. With Why We Do What We Do, teams also get into trouble when they skip translation for direct staff or families and assume that conceptual accuracy in the supervisor's head is enough. In Why We Do What We Do, most avoidable problems shrink once the analyst defines the analytic principle, decision point, and applied example the team is trying to connect more tightly, checks feasibility sooner, and names the review point before implementation begins.
Real progress in Why We Do What We Do shows up when the routine becomes more stable under ordinary conditions. In Why We Do What We Do, the cleanest sign of progress is that the relevant routine becomes more stable, understandable, and easier to defend over time. In Why We Do What We Do, depending on the case, that could mean better graph interpretation, fewer denials, more accurate prompting, reduced mealtime conflict, clearer school collaboration, or stronger staff performance. Isolated success is less informative than repeated success under ordinary conditions. In Why We Do What We Do, a BCBA should therefore look for data that show maintenance, stakeholder usability, and whether the changes around the analytic principle, decision point, and applied example the team is trying to connect still hold when the setting becomes busy again.
Rehearsal for Why We Do What We Do works only when it resembles the setting where performance must occur. Training should concentrate on observable performance rather than on verbal agreement. For Why We Do What We Do, that usually means modeling the key response, arranging rehearsal in a realistic context, observing implementation directly, and giving feedback tied to what the person actually did with the analytic principle, decision point, and applied example the team is trying to connect. In Why We Do What We Do, it is also wise to train staff on what not to do, because omission errors and overcorrections can both create drift. When supervision is set up this way, the analyst can tell whether Why We Do What We Do content has been transferred into field performance instead of staying trapped in meeting language.
Carryover in Why We Do What We Do usually breaks down when training conditions do not match the natural contingencies. In Why We Do What We Do, generalization problems usually reflect a mismatch between the training arrangement and the natural contingencies that control the response outside training. If the team learned Why We Do What We Do through ideal examples, one setting, or one highly supportive supervisor, it may not survive in case conceptualization, intervention design, staff training, and literature-informed problem solving. In Why We Do What We Do, a BCBA can reduce that risk by programming multiple exemplars, clarifying how the analytic principle, decision point, and applied example the team is trying to connect changes across contexts, and checking performance where distractions, competing demands, or stakeholder variation are actually present. In Why We Do What We Do, generalization improves when those differences are planned for rather than treated as annoying surprises.
Outside consultation for Why We Do What We Do is warranted when the next decision depends on expertise beyond the BCBA role. In Why We Do What We Do, consultation or referral is indicated when the case depends on medical evaluation, legal authority, discipline-specific expertise, or organizational decision power the BCBA does not possess. For Why We Do What We Do, that threshold appears often in topics tied to health, billing, privacy, school law, trauma, or interdisciplinary treatment planning. Referral is not a sign that the analyst has failed. In Why We Do What We Do, it is a sign that the analyst is keeping the case aligned with Code 1.04, Code 2.10, and other role-protecting standards while staying honest about what the analytic principle, decision point, and applied example the team is trying to connect requires from the full team.
A practical takeaway in Why We Do What We Do is the next observable adjustment the team can actually try. The most useful takeaway is to convert Why We Do What We Do into one immediate change in observation, documentation, communication, or supervision. For Why We Do What We Do, that might be a checklist revision, a tighter operational definition, a different meeting question, a consent clarification, or a more realistic generalization plan centered on the analytic principle, decision point, and applied example the team is trying to connect. In Why We Do What We Do, the key is that the next step should be small enough to implement and meaningful enough to test. When the analyst does that, Why We Do What We Do stops being a source of agreeable ideas and becomes part of the setting's actual contingency structure.
The ABA Clubhouse has 60+ on-demand CEUs including ethics, supervision, and clinical topics like this one. Plus a new live CEU every Wednesday.
Ready to go deeper? This course covers this topic with structured learning objectives and CEU credit.
Why We Do What We Do — The Daily BA · 1 BACB General CEUs · $24.99
Take This Course →We extended these answers with research from our library — dig into the peer-reviewed studies behind the topic, in plain-English summaries written for BCBAs.
224 research articles with practitioner takeaways
150 research articles with practitioner takeaways
106 research articles with practitioner takeaways
1 BACB General CEUs · $24.99 · The Daily BA
Research-backed educational guide with practice recommendations
Side-by-side comparison with clinical decision framework
You earn CEUs from a dozen different places. Upload any certificate — from here, your employer, conferences, wherever — and always know exactly where you stand. Learning, Ethics, Supervision, all handled.
No credit card required. Cancel anytime.
All behavior-analytic intervention is individualized. The information on this page is for educational purposes and does not constitute clinical advice. Treatment decisions should be informed by the best available published research, individualized assessment, and obtained with the informed consent of the client or their legal guardian. Behavior analysts are responsible for practicing within the boundaries of their competence and adhering to the BACB Ethics Code for Behavior Analysts.