How to Run a BCBA Journal Club That Actually Helps Clients

A 60-minute journal club works when the hour ends with a written plan for one real client, not a summary of the paper, and when the article was chosen because a case on someone's caseload is stuck right now. That single shift, picking the article from a live case instead of a reading list, is the difference between a club that stays on the calendar and one that quietly dies after three meetings.

This guide is the group version of the routine Matt Harrington walks through in his CEU, "Research to practice - extending past the pages." He built the framework after watching a fieldwork student type "ABA research paper on reducing XX behavior" into Google and get nowhere. Journal club is where a team learns that skill together, in public, with stakes.

Why most journal clubs end after three meetings#

The first meeting feels great. Someone picks a recent JABA article, everyone reads it, the discussion is lively, people leave with a few notes. The second meeting is fine. By the third, two people did not read the paper, one person is on a session, and the host is wondering why they keep doing this.

The reason is simple. Nothing on anyone's caseload changed. The club produced summaries, not decisions. When a meeting does not move a real client forward, attendance becomes optional. When attendance becomes optional, the club dies.

The fix is to tie every meeting to a stuck case. If the article does not connect to a learner someone is working with this month, the club is reading group, not journal club.

Pick the article from a current case, not from a reading list#

Start the month with a case, not a paper. Ask the team a single question. Who has a learner where you do not know what to do next?

That question almost always gets a hand. Maybe a kid is plateaued in FCT. Maybe an 18-year-old is not progressing in vocational skills. Maybe transitions are still a wall. Take that case and walk it through Matt's research finding framework.

"I was helping a fieldwork student. They were struggling with a specific client."

Get specific before you get vague. Write the actual scene on a whiteboard. Client enters classroom, work presented, client leaves seat, path blocked, aggression. Then identify the hinge point. The hinge is the one behavior that, if it changed, would solve the case. Maybe it is the para's prompting. Maybe it is task tolerance. Maybe it is delay to motor imitation.

Now go vague, but only on the hinge. Type that into Google Scholar with quotes and Boolean operators. "Functional analysis" AND school. Prompt fading AND functional communication training. Pull two or three candidate articles. The case presenter picks the one that fits best and sends it to the club a week before the meeting.

This single change does more for engagement than any other tweak. The article is no longer a random pick. It is the paper that might unblock someone's actual client.

A 60-minute meeting structure that ends with a plan, not a summary#

Sixty minutes is enough if the agenda is tight. Here is the structure that works.

Minutes 0 to 10. Case presenter walks through the learner. Skills, deficits, what has been tried, where it stalled. No article yet. Just the case.

Minutes 10 to 20. Article presenter walks through the paper. Population, procedure, results, limitations. Two slides max, or no slides.

Minutes 20 to 45. Application. This is the only section that matters. The team works on one question. What from this paper would you actually do with this client on Monday? Write the procedure on a shared doc. Name the prerequisite skills. Name what you would change because the paper used three hospital nurses and this learner has one RBT.

Minutes 45 to 55. Devil's advocate. One person, assigned at the start, argues against using the paper. Resources do not match. Phenotype is different. Implementer competence will tank fidelity. The team has to answer those objections in writing.

Minutes 55 to 60. The plan. The case presenter writes one paragraph. What will change on the BIP this week, who will run it, what data we will collect, when we will check back. That paragraph is the deliverable. No paragraph, no journal club.

Roles: case presenter, article presenter, devil's advocate#

Three roles, rotated monthly. Every team member should hold each role at least twice a year.

Case presenter owns the client. They bring the scene, the data, and the question. They leave with the plan and they are accountable for running it.

Article presenter owns the paper. They do the heavy reading and translate it into something the team can use in 10 minutes. They are also responsible for finding the article's reference section gems for next time.

Devil's advocate owns the objections. Their job is to stress-test the plan against boundaries of intervention. Phenotype, prerequisite skills, resources, implementer competence. They are not being mean. They are protecting the client from a clean Monday morning copy of a hospital study run by a PhD author.

The roles keep the meeting from becoming a one-person show. They also build the exact skills Matt's CEU is teaching, just distributed across the team.

The application section is the only section that matters#

Most journal clubs spend 45 minutes on the paper and 5 minutes on application. Flip it. Spend 10 minutes on the paper and 25 minutes on what changes for this learner.

"I would write pros, cons, summaries of research articles, but all of those were summaries about the particular research article and not the application."

The application section is where the team practices the skill that graduate programs do not teach. Pulling the behavioral principle out of the paper, separating it from the demographics and setting, and rewriting it for the learner in front of you. That is the skill. Everything else is reading comprehension.

A useful prompt for the application section: "If you stripped this paper of its setting and population, what is the behavioral principle that did the work, and where else does that principle live in this client's day?"

That question is what turned a 2014 Hanley SBT paper, originally run in an outpatient clinic, into a working intervention in a public school for a learner whose placement got changed mid-treatment.

Tracking what changed on the case the week after#

The five-minute plan at the end of the meeting is the contract. The week after, the case presenter brings a one-slide update. What got tried, what the data looked like, what is next.

Three outcomes are common. The plan worked, and the team moves on. The plan partially worked, and the team revisits one variable. The plan did not work, and the team asks whether the article was wrong or the application was wrong. That last question is the most useful one a journal club ever asks.

Keep a running log. One row per month. Client initials, hinge point, article cited, what changed on the BIP, what the data did over four weeks. After six months you have a small library of your team's own applied research. After a year, new hires read that log on day one.

How to keep RBTs and supervisees engaged#

RBTs should be in the room. Not for every meeting, but for the case they are running. They are the implementers. The plan that gets written at minute 55 is their plan to run.

Two rules keep them engaged. First, the article presenter has to translate the paper for a non-BCBA audience. If an RBT cannot follow the procedure section, the BCBAs do not understand it either, they just have the vocabulary. Second, the RBT on the case writes the data plan. They know what they can actually collect during a session.

"I'm obsessed with finding a better way to do something, finding a more efficient and proficient way to teach the learner."

Supervisees should rotate through all three roles. Start them as devil's advocate. The role forces them to read the boundaries section of every paper, which is the section their graduate program probably skipped. Then move them to article presenter, then case presenter. By the time they sit for the exam, they have run six to eight live translations from paper to plan.

If the club counts toward CEUs or supervision hours, write that into the structure from the start, not as an afterthought.

FAQ#

How often should a journal club meet?

Once a month. More often and you run out of stuck cases. Less often and the team loses the rhythm. Sixty minutes, same day every month, on the calendar a year out.

Who should pick the article each month?

The case presenter picks, with help from the article presenter. The case comes first, the article serves the case. A reading-list approach where a senior BCBA assigns papers in advance is how clubs die.

Should RBTs be in the journal club?

Yes, for the months their client is the case. They write the data plan and they leave with the procedure they will run. Optional for other months. Mandatory presence with no role kills morale.

Can journal club count toward CEUs?

Yes, if it is structured and documented. Most BACB-approved providers will support a recurring journal club series with learning objectives, an instructor of record, and attendance tracking. Build that scaffolding before you launch.

What do we do if the article does not match anyone's caseload?

Pick a different article. The whole point is to tie reading to a live case. If nobody has a stuck case this month, take the meeting off and run a procedural refresher instead. Do not force a paper.

What to do next#

The shortest path from this guide to a working club is to pick a date, name three people for the three roles, and ask the team for one stuck case. Watch Matt's CEU before the first meeting so the framework for picking and translating the article is shared language.