Specify target behaviors precisely before designing any reward system

Contingency management fails when the target behavior is fuzzy — define exactly what earns the reward, in observable terms.

Why it works

Token economies work through consistent, contingent reinforcement: the reward is delivered if and only if the specified behavior occurs. Vague targets (behave better, be more productive) make consistent contingency application impossible. Without precise specification, the system delivers reward inconsistently, which either fails to shape behavior or produces variable-ratio conditioning of unintended behaviors. Observable behavioral definitions remove ambiguity from both delivery and assessment.

How to do it

1. Write the target behavior as a description a stranger could reliably observe and measure: not "exercise more" but "complete a 30-minute workout at a heart rate above 120 bpm."
2. Specify frequency and timing: how many times per week, within what time window.
3. Define what counts as a pass and what does not — be more specific than you think necessary.
4. Review the definition with a neutral observer to check for ambiguity before running the system.

Evidence

Behavioral specification is foundational to applied behavior analysis. Precise operational definitions are associated with better treatment fidelity in CM studies. (clinical)

The practice of behavioral specification is a standard procedure rather than a separately studied intervention; its importance is established by the high failure rate of systems with vague targets.

Sources

• Cooper, Heron & Heward, "Applied Behavior Analysis" — behavioral measurement and specification

Common mistake

Starting with a reward system before the target behavior is operationally defined — the ambiguity then becomes a source of conflict and inconsistency that undermines the whole system.