When the Consequence Is the Problem

A participant is pacing, talking over people, refusing to join the group. A staff member issues a warning. It doesn't work, so they get sent home, or suspended, or they lose canteen for the week. Order is restored and the group moves on.

Most of us have seen this play out. Many of us have been the one doing it. The intention is usually sound — maintain expectations, hold a line, signal that behavior has consequences. The problem is that in doing so, we may have applied a consequence to a symptom rather than to a choice. And consequences don't treat symptoms. They simply add something difficult on top of something that was already difficult.

Before responding to challenging behavior, there is a question worth slowing down for: what is actually driving this?

The answer is rarely obvious from the outside. Sometimes people don't know what's expected because no one has clearly taught them. Sometimes they know and aren't following through, and there is something underneath that deserves a real conversation rather than a warning. And sometimes the behavior has nothing to do with choice or motivation — active psychiatric symptoms are interfering with the person's ability to function within program expectations, and no disciplinary response is going to reach that.

Each of those situations calls for a fundamentally different response. The instinct to issue warnings and impose consequences might be appropriate when behavior is willful and repeated. It causes real harm when what is actually happening is a psychiatric symptom expressing itself the only way it can — through disruption, withdrawal, agitation, or refusal.

The research on coercive responses in recovery settings is consistent on this point. People do not develop greater self-regulation under threat. What they develop is a learned performance of compliance when observed, paired with disengagement when they are not. In the more serious cases, they simply stop attending — something programs tend to document as dropout rather than what it frequently is, which is a person who concluded that the program was not a safe place to be honest about where they are.

And consequences don't treat symptoms. They simply add something difficult on top of something that was already difficult.

Recovery is relational and it is built slowly, through accumulated trust between people. Punitive responses erode that trust — not always in dramatic ways, but incrementally, warning by warning, suspension by suspension, until the therapeutic relationship that was supposed to carry the work of recovery has been quietly hollowed out.

When behavior appears to be symptom-driven, the clinical task is to reduce distress rather than enforce the schedule. This means de-escalating, creating space, and resisting the urge to address the incident in the moment when symptoms are still active. That conversation belongs later, when the person is settled and can actually engage with it. When behavior looks more like resistance or ambivalence, the appropriate response is curiosity before correction — understanding what the refusal is protecting before deciding what to do about it.

Documentation matters here as well. Writing down what was actually observed — "paced the room for twenty minutes and did not respond to verbal redirection" — gives the clinical team something to work with. Writing "was acting out" or "was being difficult" records frustration, not behavior, and serves no one.

The staff doing this work are not the source of the problem. Peer support workers and PSR educators are navigating genuinely complex clinical situations, frequently without adequate supervision, clear escalation pathways, or training that equips them to reason through what a situation actually requires. When the guidance runs out, people reach for what feels like structure — and consequences feel like structure. The solution is not to criticize the instinct but to replace it with something better.

That is a training problem, and training problems are solvable.