Why Direct Support Staff Aren't Using the Tech That Could Help Them

Walk into most human services agencies right now, and you'll find at least one software platform that was supposed to make life easier for front-line staff. It was bought by leadership, trained once, and largely ignored by the people it was designed for. This is not a technology problem. It's a trust problem, a training problem, and occasionally a timing problem. But mostly, it's a communication problem.

I hear a version of this story constantly. One Direct Service Professional (DSP) I spoke with recently put it plainly: "They handed me a new system halfway through a shift and told me it would streamline my workflow. I smiled, nodded, and found a workaround by the end of the week." Not because she was resistant to change. Most DSPs are remarkably adaptable. But because the tool was built without her.

The adoption gap in human services tech is wide and it's getting wider. Vendors are building AI-powered tools for I/DD organizations at a growing pace: documentation assistants, scheduling platforms, behavior support tracking, communication tools for people with complex needs. Some of them are genuinely useful. But they're landing in organizations where front-line workers are stretched thin, where training time is scarce, where the historical relationship between "new technology" and "more work for staff" has been painfully consistent.

Here is the thing I hear most often when I talk to DSPs: they don't ask for better technology. They ask for better paychecks. We agree. Building new tools and skillsets to scale service is exactly how we get those bigger paychecks for our front-line staff. But that argument only works if the technology actually gets used.

When I ask DSPs why they don't use the tools available to them, I hear a few things over and over. First: nobody showed me how, not really. A one-hour orientation doesn't build confidence. It builds anxiety. Second: it doesn't fit how I actually work. Tools designed for desktop use get handed to people who work on their feet, in homes, in community settings. Third, and this one matters most: I wasn't involved in picking it. There's something that happens when a person has no voice in a decision that shapes their daily work. They don't own it. They tolerate it, at best.

This is fixable. But it requires a different starting point. Instead of asking "what technology should we deploy," organizations that are getting this right are asking: where do our staff spend the most time, where do they lose the most energy, and what would they actually use? That question, asked directly to DSPs and not on their behalf, changes what you build and how you roll it out.

At PathAble, we believe that inclusion as a design principle applies not just to the people we serve, but to the people doing the serving. If a DSP wasn't in the room when a tool was designed or selected, you're going to spend twice as much on training and get half the adoption. The math doesn't work.

The technology that helps DSPs isn't necessarily the most sophisticated. It's the technology they trust, understand, and had a hand in shaping. That bar is achievable. We just have to stop designing for an imaginary worker and start listening to the actual ones.