Programming common stimuli

Common means present across contexts

A common stimulus may be a checklist, payment card, AAC page, staff phrase, uniform, tool, room layout, or sequence of steps. Its value comes from being present and relevant in both teaching and the target setting.

The feature should be detectable and tied to the intended response. A generic picture posted everywhere may be common without controlling anything useful.

Start with the real environment

Observe or document the target setting before building teaching materials. Identify the people, language, objects, sensory conditions, response requirements, and consequences that will actually occur.

If a grocery checkout requires a store loyalty card, teaching with the real card can bridge settings. If store layouts vary, the card alone may be insufficient; multiple exemplars, direct practice, or a portable checklist may also help.

Stokes and Baer described a broader technology

Stokes and Baer’s classic review organized nine generalization tactics, including programming common stimuli, training sufficient exemplars, contacting natural contingencies, and training loosely. The framework argues for active planning rather than waiting for transfer.

This is one tactic within that larger system. A common cue may support performance while people, effort, consequences, or materials still differ enough to limit generalization.

Select features that belong in daily life

Useful common stimuli are acceptable, durable, available, and easy to maintain. They should not depend on one clinician carrying a special item that disappears when services end.

Ask whether the person wants the support. A portable visual checklist or saved phone note may be more useful than memorization. Generalization does not require removing accommodations that remain part of ordinary access.

A fictional common-stimulus probe

Theo practices self-checkout with a laminated card that lists the same four symbols used by a new grocery store. The real card is present during teaching and on the first store visit.

Across six novel checkout opportunities with the card, Theo completes the planned sequence in 5 of 6. Across six later opportunities when the card is unavailable because it was left at home, he completes 2 of 6. These different conditions suggest the card may support performance. They do not prove it caused the difference, and “without card” is not automatically the better outcome.

The team asks Theo whether a phone version would be more reliable and tests it in additional stores.

Probe the target without changing everything

Define which features are common and which are novel. Keep the response, scoring rule, and ordinary support consistent. Record prior exposure, prompts, feedback, partner help, and environmental differences.

A novel-setting success rate equals correct independent responses divided by eligible novel opportunities. Keep it separate from teaching accuracy. After feedback occurs, later trials are no longer first-exposure probes.

Social stimuli can be common too

People’s responses, wording, wait time, and positioning can carry across settings. Training caregivers or staff to use the same accessible prompt and honor the same communication may support transfer.

A telehealth case paper by Wacker and colleagues explains how one program incorporated several Stokes-and-Baer tactics, including common stimuli. A case example illustrates planning and does not establish independent effects for each tactic.

Common stimuli can create narrow dependence

If responding occurs only with one checklist, transfer may remain limited. Decide whether the support is intended to remain, vary across equivalent versions, or fade. Fading is useful only when independence from the feature is a meaningful goal and removal does not reduce accessibility.

Osnes and Lieblein reinterpret generalization programming through stimulus control. Their analysis supports identifying which features should control behavior instead of treating generalization as a vague spread.

The BACB BCBA Test Content Outline, 6th edition includes programming for generalization and maintenance in examination content. It does not prescribe a common stimulus or fading schedule.

Build a common-stimulus register

For each planned bridge, record the stimulus, target response, teaching location, target locations, owner, version, accessibility needs, and replacement plan. Note whether the feature already occurs naturally or must be carried, installed, or displayed.

Then test availability. A checklist stored in a locked staff drawer is not functionally common for the person who needs it. A device prompt that requires unreliable internet may disappear at the exact moment of use. Track present-and-usable opportunities divided by opportunities in which the support was planned.

Retire outdated versions deliberately. If a store changes symbols or a device interface changes, update teaching and target copies together. Preserve the old version in the record so errors are not misread as loss of skill when the environment changed first.