Beyond The Binder. The Program That Remembers

Every 90 seconds was a new day. Every 90 seconds, we were strangers again.

I stepped into the kitchen. The digital clock on the microwave blinked 8 pm. DJ abruptly popped out of his chair, his tone startled but friendly,  “Hi, I’m DJ. What’s your name?” I told him. It was the same one I gave him at 10 am when I showed up for the shift. And the same one I gave him again and again during every hour in between. “Hey, nice to meet you,” he said -- as if it were the very first time.

And for DJ, it truly was the first time. He was 35 then, but a motorcycle accident at 17 froze his world in adolescence and melted away any new footprints that should have come with time. No new memories. Every morning he stressed about making weight for his high school wrestling match, and every night he doused himself with Drakkar cologne in anticipation of picking up some “chicks” at the party. And every shift, I met him again. We had the same getting-to-know-you conversation, played the same card game, and walked the same route through his neighborhood.

Supporting DJ was hard. It wasn’t because he was an unlikeable guy; it was because nothing stuck. Learning didn’t build the way it usually does. Shared experience didn’t accumulate. Even the simple comfort of familiarity -- the ease of “we know each other”-- kept evaporating and demanding to be rebuilt.

One day, after we played our hundredth game of War in the park, we sat back to people watch. The silence was just long enough to wash away our card game banter and competitive one ups, and he turned to me and said, “Hi, I’m DJ.” And even though we lived this moment a million moments before, a basic truth was so clear to me then: So much of relationship depends on memory. It’s the inside jokes that land without explanation. The look that doesn’t need a caption. The way you learn, over time, what makes someone light and dim. And it’s what, ultimately, can make the world feel manageable.

That’s the part that often gets overlooked when we talk about “behavior support.” We tend to focus on the mechanics of the plan -- strategies, data, protocols, skill targets. But in real life, support doesn’t even leave the ground without a relational foundation strong enough to carry it. 

You can have the most elegant programming, and it will still fail on an ordinary Tuesday if the person doesn’t feel safe with the staff delivering it. 

Relationship is the intervention. Which is why continuity matters.

Too often in disability services, we recreate DJ’s 90-second reset every time a program’s memory lives only inside one person’s head. When staff leave, it isn’t only a relationship that ends. It is a whole body of “knowing” that walks out with them; and the person we support is the one forced to start over. 

There are, of course, beautiful exceptions where direct staff stay for many years, supporting the same person. But the larger truth is that people leave. They leave for better pay, for family, for health, for burnout, for reasons that have nothing to do with the person they supported. And while the current turnover crisis in disability services may feel especially acute, turnover itself is not new. In my 26 years in this field, I have seen both harsh and forgiving seasons, but none without it.

Just because turnover is real, a person’s life shouldn’t become fragile. What holds support together, even when relationships are disrupted, is continuity built into the system. This means making sure the relational wisdom your best staff have built is not lost when they leave, but shared, learned, and carried forward by the whole team. Programs can build this type of continuity by treating it as a three-part system: what we know, how we pass it on, and what we do when things get hard. Specifically:

1) Externalize program memory: what we know

This is the person-specific “source of truth.” The goal is simple: the team can retrieve the right information quickly, without guessing. A useful way to organize it is by what you’d want any staff member to recognize in real time:

• Green flags (DJ is okay): “When DJ is steady, you’ll see…”
• Yellow flags (early signs): “When things are starting to wobble for DJ, it usually looks like…”
• Red flags (it’s tipping): “When it’s going off track, you’ll see…”
• What helps (fastest way back): “The quickest way to help DJ re-set is…”
• What makes it worse (even if intentions are good): “Avoid… even if it seems helpful.”
• Orientation anchors: “DJ does best when he knows…”
• What a good day means here: “A good day for DJ includes…”

This is the information staff should be able to retrieve in under a minute, mid-shift. If it can’t be found quickly, it won’t be used. And then the program is back to tribal knowledge and guesswork.

2) Design onboarding as relationship transfer: how we teach

This is how a program brings a new staff member into the relationship safely, so they can apply the program memory with dignity instead of accidentally creating distress. Start with a short onboarding sequence that gets practiced, not just read:

The first 10 minutes protocol (taught + coached):

• Arrival stance: “Come in slower than you think you need to”
• Greeting ritual: what it sounds like here (and what to avoid)
• Preview habit: “Now / next / how long / who with”
• First choice offered: one real control point early
• One repair script: a rehearsed reset if you misstep (“That was too fast. Let’s try again.”)

Then make it stick with a simple coaching structure:

• Shadowing: new staff watch a skilled staff run the first 10 minutes once
• Guided practice: new staff do it while someone coaches quietly
• Feedback loop: one specific “do more of this” note after the shift
• Reinforcement: supervisors notice and praise these skills the way they praise technical competence

In this way, new staff learn how to be safe and predictable quickly since continuity is built in lived moments, not in written policies.

3) Build anti-drift defaults: what we do under pressure

Hard days are a given part of services; they should be expected and planned for. Call-outs, new hires, double shifts, fatigue -- this is when programs drift into speed and control. So, teams need a universal “pressure protocol” that outlines a simple routine staff return to when the shift starts tightening:

When you feel the shift tightening:

• Orient first (now / next / how long)
• Offer one real choice
• Reduce language (say less, slower)
• Slow pacing (hands, feet, voice)
• Repair quickly (name it, soften, restart)

This is what trained teams can fall back on when they’re tired, new, or stretched thin. And it protects the relationship on the days when the system is most likely to accidentally threaten it.

As DJ taught me so well, relationship runs on memory. Great services build programs that can hold it -- so no one has to start over every 90 seconds.