Escape behavior during academic tasks: a preliminary analysis of idiosyncratic establishing operations.

Three boys with autism or developmental delay kept hitting, biting, or screaming when teachers gave classwork. The team ran a four-step check: first a classic functional analysis, then a descriptive look at the room, next a deep dive into what exact part of the task set the kids off, and last a quick follow-up test.

They changed tiny bits of the work—how many problems, the kind of paper, the voice tone—while keeping escape as an option. They wanted to see which micro-tweaks turned off the problem behavior.

Each boy had his own 'trigger recipe.' For one, just lowering the problem count from ten to three cut aggression to zero. For another, switching from a worksheet to picture cards did the trick. The fixes were small, but the destructive acts almost vanished.

Best part: the kids could still ask for a break. The team only changed the task, not the escape door.

Allison et al. (1980) first showed that escape itself fuels aggression; Rose et al. (2000) zooms in further, mapping the exact task features that light the fuse. It's the same engine, but now we know which bolts to turn.

Traub et al. (2019) also sharpened escape assessment by timing how fast kids run from demands. Both papers prove that finer metrics—latency or tiny EO shifts—speed up and sharpen functional work.

Taylor et al. (1993) split different forms of self-injury by separate functions; J et al. does the same for task escape, showing each topography may need its own micro-fix.

Before you write a full behavior plan, run a micro-EO check. Ask: is it the length, the modality, or the wording that sparks the fire? Adjust just that piece while keeping the break option open. You may solve the problem without heavy extinction or new rewards.